GM everyone!
Following the encouraging response to the initial org-chart comment, I’d like to open this thread to go deeper into the design conversation as a practical exploration to improve information flows and clarify domains within Scroll DAO.
cc. @coffee-crusher, @bitblondy, @Tino, @Jamilya
Why this matters
As Scroll grows, having clarity on who is responsible for what, and where decisions are made, becomes vital.
A visual, role-based org map can offer many advantages:
-
Improved accountability: visible responsibilities tied to specific roles
-
Clearer onboarding: newcomers can identify where they fit and who to contact
-
Less duplication of work: clearer domains prevent teams from unknowingly working on similar problems
-
Reduces influence trafficking: having two people linking circles makes information flow more resilient
-
Increased learning capacity: contributors who share the same role (e.g. Accountability) can form “squads” across circles to document and refine shared practices
Unlike Sociocracy, where the basic unit is the person, a role-based map (inspired by Holacracy) reflects how multiple roles can be held by one person, and how one role can be held by multiple people. This makes communication more flexible, allowing for both direct messaging and role-based coordination.
Modular elements from Sociocracy 3.0 (adaptable to Scroll)
This is not about applying one governance model wholesale. It’s about selectively integrating elements that improve coherence. Here are some of the key building blocks:
1.- General Circle
A small coordination group composed of links from 6–7 primary circles.
benefits:
-
Keeps high-level conversations focused and aligned
-
Allows domain-specific circles to retain autonomy
-
Prevents over-centralization while improving shared understanding
The proposed size (~6 circles) helps avoid overload while keeping it participatory.
2.- Double-Linking
Each circle connects to its parent circle via:
- A Coordinator (appointed by the parent-circle or Foundation)
- A Representative (elected from within the circle)
benefits:
- Creates bidirectional communication
- Ensures no single gatekeeper filters context
- Adds resilience in case someone is absent or overloaded
3.- Operational Roles & Governance Roles
Each circle can define:
- Operational roles for execution (e.g. DevRel lead, Funding steward, etc.)
- Governance roles for internal coordination, like Facilitator, Secretary and Coordinator (distributing invisible coordination labor more fairly).
benefits:
- Facilitators help structure conversations (achieving a balance between efficiency and inclusiveness)
- Secretaries track agreements and documentation (enabling accountability and driving learning)
- Coordinators support alignment without centralizing power (Taking the DAO perspective, bringing the focus back to what matters)
4.- Consent-Based Decision-Making (for operational matters)
Consent can be used within circles for program-level decisions, while proposals affecting the whole DAO remain subject to representative voting via delegates. That is, governance decisions at the council/team level (where the members’ perspectives are sought to be integrated instead of voting for the most popular one).
benefits:
- Increases contextual understanding and builds on prior learning.
- Encourages constructive objections.
- Maintains alignment between members.
5.- Rounds as Structured Dialogue
Circles can adopt decision rounds to ensure all voices are heard before acting. That is, when you don’t know what to do, invite the group to do a structured round of reactions.
benefits:
- Builds collective intelligence
- Surfaces blind spots
- Reduces dominance by the loudest or most confident
Let’s co-create what fits Scroll
All of this is offered as a menu of options we can adapt. This process offers the perfect moment to:
- Make responsibilities and domains visible
- Clarify accountability and reporting flows
- Improve onboarding and delegation
- Explore the formation of role-based squads or shared learning spaces
If you’re interested in any of these, I invite you to continue this conversation with me.
Happy to organize or join a co-design call to shape this further.
Here a poll to explore possible dates and ways forward
- Wednesday the 13th at 18:00 hrs UTC (post the Weekly DAO & Governance Call in the afternoon)
- Thursday the 21st at 17:00 hrs UTC
- I don’t have any of those options, but I still want to participate. Let’s find more options!
- I want to participate asynchronously, checking out the progress and leaving comments in the thread.
I look forward to your comments, questions, and reactions. 
Excited to be able to contribute through this topic that I love.
