2021-11-18 Community Experience Call

Created
Nov 18, 2021
Tags
Attendees
ย 
ย 
Community Experience
ย 
Strategy
  • Design vs Implementation under DAOops
  • Org
  • Budget - as soon as tally passes
    • Hiring
  • Q1 Budget
    • + Support
Onboarding
  • Discord
    • Delayed
  • Proposal for onboarding pause
    • Move to cohort where we try to really engage with everyone in the database
      • Currently not 'processing' people (300+)
      • Kernel's process creates a good sense of community - so we get a good sense of values, eg in discussion groups
      • Repeated people who keep showing up are the people we need
      • We can have them read up on some material before and have them engage
      • Having a journey as a group helps a lot (//kernel)
      • Priority is having people go to the right way of the dao
      • A lot of our most engaged users dropped off bcs they got lost, BUT 121 onboarding calls were some of the best calls
    • In the meantime
      • we will not stop hiring
      • we will optimize the process, eg community managers, one typeform etc
      • continue to do bi-weekly onboarding calls and help people find their place
      • continue having a bi-weekly hosts call, where we come up with good ways to interact with people in the biweekly onboarding calls
    • Notes loie
      • would NOT stop hiring for specific needed roles
      • til Jan 1st at least
      • move twds cohort model
      • could repurpose the biweekly call for those who are currently in
      • we haven't had the time to give current contributors the attn they need
      • we are accepting people that shouldn't have been accepted, we can't accurately vibecheck with the way we are reviewing ppl now
      • Kris and Loie will take the "are we lightly reviewing ppl still" convo offline
      • Every workstream should have a community manager
      • moonshot collective is an 'edge case', bit MMM as well
  • Hiring
  • Processes
  • Participation
  • Remuneration
  • Open jobs
ย 
Tools
ย 
Calendar
  • Google calendar x addevent?
  • Next step:
    • Cali find a developer to fix the recurring event issue
    • Kris: find person for training & maintenance
Knowledge base
  • Knowledge base being set up by Cali & Alp, under Dgitcoin
  • New contributors information can live here
  • Support has been integrated here
  • Translations - a number of translations happening
Notion
  • Update status + next steps
Discord
  • Next steps
    • Channel mapping & recommendations - DONE
    • Roles proposal - DONE
    • Check-in with stakeholders - DONE
    • Roles linked to the access levels - work in progress
ย 
Action Steps:
  • Post request for peer review experts in Onboarding chat
ย 
People ops
  • Org charts & roles
    • Simona lots of experience here, kyle working on sobol, daniel created a proposal here
    • Tip ryan: tooling option for mapping
    • Next step:
      • loie do catherding for now - taskforce
      • loie/daniel: who are the people who need their roles defined - this'll start by Daniel dm'ing WS leads & asking for list of all ppl who have been paid by the WS
      • QZ is the notion master to have a seat at this table
  • Vision/Mission
    • Simona working on a unified document
    • next steps coming next week
  • Peer review process
    • Call coming up next week
  • Conflict resolution
    • Alp doing some research here & syncing with loie
    • 'ombudsperson' - would be good to have one
    • Loie is also trained in conflict resolution - you can always call on loie
      • Adam golding could be a good person
  • Coaching
    • Most effective calls were the 121 coaching onboarding calls (ryan, is also his background)
    • Candidates
      • Gerrit could be a good person (from MC)
      • Ryan has a great coach as well - level7.is
  • Weekly contributor call
    • Ryan's goal - to make it an open call & share some of the things we're doing
    • Would be great to have a clear agenda for this call
    • Tue meeting - if he could attend that one (kris)
ย 
ย 
ย 
ย 
ย 

2021-11-18 Community Experience Call

Created
Nov 18, 2021
Tags
Attendees
ย 
ย 
Community Experience
ย 
Strategy
  • Design vs Implementation under DAOops
  • Org
  • Budget - as soon as tally passes
    • Hiring
  • Q1 Budget
    • + Support
Onboarding
  • Discord
    • Delayed
  • Proposal for onboarding pause
    • Move to cohort where we try to really engage with everyone in the database
      • Currently not 'processing' people (300+)
      • Kernel's process creates a good sense of community - so we get a good sense of values, eg in discussion groups
      • Repeated people who keep showing up are the people we need
      • We can have them read up on some material before and have them engage
      • Having a journey as a group helps a lot (//kernel)
      • Priority is having people go to the right way of the dao
      • A lot of our most engaged users dropped off bcs they got lost, BUT 121 onboarding calls were some of the best calls
    • In the meantime
      • we will not stop hiring
      • we will optimize the process, eg community managers, one typeform etc
      • continue to do bi-weekly onboarding calls and help people find their place
      • continue having a bi-weekly hosts call, where we come up with good ways to interact with people in the biweekly onboarding calls
    • Notes loie
      • would NOT stop hiring for specific needed roles
      • til Jan 1st at least
      • move twds cohort model
      • could repurpose the biweekly call for those who are currently in
      • we haven't had the time to give current contributors the attn they need
      • we are accepting people that shouldn't have been accepted, we can't accurately vibecheck with the way we are reviewing ppl now
      • Kris and Loie will take the "are we lightly reviewing ppl still" convo offline
      • Every workstream should have a community manager
      • moonshot collective is an 'edge case', bit MMM as well
  • Hiring
  • Processes
  • Participation
  • Remuneration
  • Open jobs
ย 
Tools
ย 
Calendar
  • Google calendar x addevent?
  • Next step:
    • Cali find a developer to fix the recurring event issue
    • Kris: find person for training & maintenance
Knowledge base
  • Knowledge base being set up by Cali & Alp, under Dgitcoin
  • New contributors information can live here
  • Support has been integrated here
  • Translations - a number of translations happening
Notion
  • Update status + next steps
Discord
  • Next steps
    • Channel mapping & recommendations - DONE
    • Roles proposal - DONE
    • Check-in with stakeholders - DONE
    • Roles linked to the access levels - work in progress
ย 
Action Steps:
  • Post request for peer review experts in Onboarding chat
ย 
People ops
  • Org charts & roles
    • Simona lots of experience here, kyle working on sobol, daniel created a proposal here
    • Tip ryan: tooling option for mapping
    • Next step:
      • loie do catherding for now - taskforce
      • loie/daniel: who are the people who need their roles defined - this'll start by Daniel dm'ing WS leads & asking for list of all ppl who have been paid by the WS
      • QZ is the notion master to have a seat at this table
  • Vision/Mission
    • Simona working on a unified document
    • next steps coming next week
  • Peer review process
    • Call coming up next week
  • Conflict resolution
    • Alp doing some research here & syncing with loie
    • 'ombudsperson' - would be good to have one
    • Loie is also trained in conflict resolution - you can always call on loie
      • Adam golding could be a good person
  • Coaching
    • Most effective calls were the 121 coaching onboarding calls (ryan, is also his background)
    • Candidates
      • Gerrit could be a good person (from MC)
      • Ryan has a great coach as well - level7.is
  • Weekly contributor call
    • Ryan's goal - to make it an open call & share some of the things we're doing
    • Would be great to have a clear agenda for this call
    • Tue meeting - if he could attend that one (kris)
ย 
ย 
ย 
ย 
ย