Org Design: Changes in Governance Needs?

Questions:

General Governance

What decisions will we continue to use our existing token governance process?
- Or rather what decisions will need to remain on-chain regardless of what level they are made at (DAO, Org, Team, etc.?
  - Funding/budget approval for Orgs/Teams
  - subDAO creation/defunding
  - Community emergency kill-switch (if all orgs turn malicious)
  - Emergency funding requests (e.g. if grants breaks down)
If decisions involving ALL token-holders decreases dramatically, how does this affect incentive to buy/use token? What implications does that have?
Should on-chain votes happen in cycles or as needed?
- DAO level: annually, quarterly, every 6 months?
- Org level: annually, quarterly, every 6 months, as needed?
- Team level: as needed?
- If different votes will have different (or no specific cycle), define when they all will happen.
What will governance structures at Org or Team levels look like? (to be decided by each org & team)
- Multi-sigs
- Purely non-tokenized voting (soulbound tokens, NTTs, one person-one vote?)
- Part on-chain, part off-chain? (part tokenized gov, part non-tokenized?)
- Different for different levels?
How will labeling of proposals need to change to make it clear who gets to/has to vote on what?
- DAO-wide decisions vs Org decisions vs team decisions
- Want to remain transparent - but need to clearly communicate voting to avoid confusion/overload of info for contributors
What happens to delegates/active delegates in this new system if any change?

Power relationships:

What checks and balances need to exist between layers?
- e.g. - How do teams keep orgs in check if they start making decisions they don’t agree with/believe are bad for the teams
How to uphold Collective responsibility — “We are responsible for holding each other accountable rather than relying on a hierarchy.”

Cross-team coordination:

How will the different decision-making models within the various teams work with each other/interact with each other? To what extent will they need to (cross-team coordination)?
Should there be some degree of similarity in these decision-making models for the sake of easy transferability (of contributors) between orgs/teams?
- i.e. - every time someone transfers to a different team or interacts with a various teams they don’t have to onboard to an entirely new system

Product

Liability/Risk