🗃️
Contributor Access Bundle DBs
/
Use a Role Documentation process based on Purpose, Accountabilities, and Domains of the role, with Sobol as an interface

Use a Role Documentation process based on Purpose, Accountabilities, and Domains of the role, with Sobol as an interface

Proposed By
Essential Intent
Outcome
PASSED
Proposal Date
Dec 14, 2021
Meeting Notes
Type
Tooling
Last edited time
Jul 28, 2022
Meeting Notes:
Outcome: Passed ✅
Outcome Summary
This proposal passed, and sobol will be used to document roles based on purpose, accountabilities, and domain.
Proposal
Proposal 1 - Loie
  • Tension: It's hard to know who to ask for certain help, or know how to give meaningful feedback on each other's work because roles are unclear, we don't have agreements of what work we're doing.
  • Proposal: Use a Role Documentation process based on Purpose, Accountabilities, and Domains of the role, with Sobol as an interface
    • We'd start with documenting our own roles in January (by inputting them into Sobol), and try to reach agreement with our close teams on what our individual purpose & way of achieving it is. It's a bit like going thru a DAO hiring process, just a little later than one usually would :) This will likely be folded into our first round of DAO Peer Review process
    • The 5 fields for defining a role are: Purpose, Accountabilities, Responsibilities (this is who is executing), Projects/Tasks, and Domains of Authority
    • Sobol has quoted us a membership of $150/month for 50 users. We can pay in GTC for 6 months in advance if we wish.
    • Sobol serves as much more than a database of roles - it has beautiful community-mapping capabilities and would serve as our org chart too. The Sobol team is excited to work with us & would likely build custom features for us.
    • Daniel lined up to Project Manage this implementation
    • Example of org at bankless here
  • Clarifying Questions
    • Sean: How to use this for people who are not contributing full-time? 'Allocation' helps with this. Maybe less than 10hrs
    • Kris: 282 active contributors, who should fill this out? We could work with email invitations only
    • Kyle: one decision is to use sobol, second is to work on role definition. Are we relying on people to fill this out? This first round can be us submitting what we think is true and then we can make suggestions to change
    • Sean: Getting into performance mgmt. Is this a tool where we would do this most holistically? Loie: peer review itself is a separate proposal
    • Kris: How do we push/enforce people to actually fill this out? Loie: meta Q - if WS leads support this, they can stimulate their team members to fill this out. Daniel will help to catherd.
    • Kris: How can we make sure that there is no extra overhead for notion - ideally we try to integrate as much as possible via APIs, sobol could be more internal facing
  • Reactions
    • Kyle: supportive, as scoped
    • Joe: supportive, pls consult with people from the dao tooling notion team
    • Sean: supportive
    • Annika: highly supportive, echo many Qs, scale & making sure it's not dropped
    • Huxwell: fully supportive, define the source of truth for what is in the workstreams
    • Kevin: supportive, visualizing the dao
    • Kris: supportive, long term solution, make sure it works well with notion, set up call with vgk/qz/kris to make all things sync
  • Amendment notes:
    • Needs to be useful without too much overhead
    • set up call with notion team
  • Objections?
  • Proposal passed!
🗃️
Contributor Access Bundle DBs
/
Use a Role Documentation process based on Purpose, Accountabilities, and Domains of the role, with Sobol as an interface

Use a Role Documentation process based on Purpose, Accountabilities, and Domains of the role, with Sobol as an interface

Proposed By
Essential Intent
Outcome
PASSED
Proposal Date
Dec 14, 2021
Meeting Notes
Type
Tooling
Last edited time
Jul 28, 2022
Meeting Notes:
Outcome: Passed ✅
Outcome Summary
This proposal passed, and sobol will be used to document roles based on purpose, accountabilities, and domain.
Proposal
Proposal 1 - Loie
  • Tension: It's hard to know who to ask for certain help, or know how to give meaningful feedback on each other's work because roles are unclear, we don't have agreements of what work we're doing.
  • Proposal: Use a Role Documentation process based on Purpose, Accountabilities, and Domains of the role, with Sobol as an interface
    • We'd start with documenting our own roles in January (by inputting them into Sobol), and try to reach agreement with our close teams on what our individual purpose & way of achieving it is. It's a bit like going thru a DAO hiring process, just a little later than one usually would :) This will likely be folded into our first round of DAO Peer Review process
    • The 5 fields for defining a role are: Purpose, Accountabilities, Responsibilities (this is who is executing), Projects/Tasks, and Domains of Authority
    • Sobol has quoted us a membership of $150/month for 50 users. We can pay in GTC for 6 months in advance if we wish.
    • Sobol serves as much more than a database of roles - it has beautiful community-mapping capabilities and would serve as our org chart too. The Sobol team is excited to work with us & would likely build custom features for us.
    • Daniel lined up to Project Manage this implementation
    • Example of org at bankless here
  • Clarifying Questions
    • Sean: How to use this for people who are not contributing full-time? 'Allocation' helps with this. Maybe less than 10hrs
    • Kris: 282 active contributors, who should fill this out? We could work with email invitations only
    • Kyle: one decision is to use sobol, second is to work on role definition. Are we relying on people to fill this out? This first round can be us submitting what we think is true and then we can make suggestions to change
    • Sean: Getting into performance mgmt. Is this a tool where we would do this most holistically? Loie: peer review itself is a separate proposal
    • Kris: How do we push/enforce people to actually fill this out? Loie: meta Q - if WS leads support this, they can stimulate their team members to fill this out. Daniel will help to catherd.
    • Kris: How can we make sure that there is no extra overhead for notion - ideally we try to integrate as much as possible via APIs, sobol could be more internal facing
  • Reactions
    • Kyle: supportive, as scoped
    • Joe: supportive, pls consult with people from the dao tooling notion team
    • Sean: supportive
    • Annika: highly supportive, echo many Qs, scale & making sure it's not dropped
    • Huxwell: fully supportive, define the source of truth for what is in the workstreams
    • Kevin: supportive, visualizing the dao
    • Kris: supportive, long term solution, make sure it works well with notion, set up call with vgk/qz/kris to make all things sync
  • Amendment notes:
    • Needs to be useful without too much overhead
    • set up call with notion team
  • Objections?
  • Proposal passed!