Even though it seems premature to moving onto another iteration so soon after the last, there are obviously - as mentioned by Kieran in the Town Hall - teething problems with the current version. Early sketch, but I think it's good to get the conversation started.
Problem:
- Confusion over power dynamics, roles and responsibilities between Councils and Contributors
Proposed Solution:
Make the following clear:
- Governance can say "no", but cannot say "yes"
- Specialist Councils are community suggestion filters
- Main Council has veto authority over major changes
Essentially flow is as follows: community suggestion chaos -> idea gets traction -> Specialist Council vote -> Contributors decide if they want to pursue
-> if minor action pursued, resources committed to doing action
-> if major action pursued, Main Council can vote to veto -> resources committed
Advantages:
- Allows great community ideas to surface
- Leverages talented specialists within the community to filter popular but shortsighted ideas
- Gives Contributors complete decision-making authority over their realm of expertise, i.e. avoids the 'a camel is a horse made by committee' problem and gets out of the team's way
- Gives the DAO/players final say before major changes are made
- Isn't a complete reshuffling of governance in the way 1->2 was
Questions unanswered:
-
What constitutes a "major" action? My personal preference is for this to be relatively limited so as to not bog the team down, but the threshold should be clearly defined
-
In this structure, do current Specialist Councils (e.g. Strategy, Game, Marketing etc) make sense? If the role is simply to filter community suggestions, should these be determined by the quantity of community inputs in each subject area?
-
Likely many others that this early sketch is missing - interested in any and all feedback