A reference for clarifying Holacracy. Each principle is shown as Holacracy practices it, contrasted with a traditional hierarchy and a consensus org (each at its best, not as a strawman), with a plain-language note on what it means in practice.
| # | 🟢 Principle (Holacracy) | 🏢 Traditional hierarchy | 🤝 Consensus | 📝 In practice |
|---|---|---|---|---|
| A · Roles & authority | ||||
| 1 | Role ≠ soul — identity stays separate from the roles you fill | Title & person blur | Whole person, but conflict feels personal | When a role's work is criticized — “Marketing dropped the ball” — it lands on the role, not on you as a person, so you can fix it without feeling attacked. You fill several roles and none of them is you; you can drop a role tomorrow and still be the same colleague. This is what makes it safe to give honest feedback in the room: everyone knows we're talking about the work, not the worth of the human doing it. |
| 2 | Know which hat you wear — name which of your roles is acting | One title, rarely comes up | You speak as yourself | Before you speak, name the role you're speaking from — “As Scheduler, I need the dates by Friday” vs. “As a teammate, I'd hate to rush you.” The same person can hold conflicting interests across their roles, and saying which one is talking stops the muddle. It also exposes when you're speaking from no role at all — sometimes a useful signal that the work isn't anyone's yet. |
| 3 | Address the right hat in others — aim at the role, not the person | Go to the person / their manager | Raise it to the group or individual | Aim requests and objections at the role that owns the work, not at whoever happens to be in the chair — “I need this from Finance” rather than “I need this from you, Sandra.” If two roles both sit on one person, be explicit about which you're addressing. This keeps disagreement from feeling personal and makes it obvious when a needed accountability has no role assigned to it yet. |
| 4 | Roles explicitly defined — written purpose + accountabilities | Job descriptions + reporting lines | Roles stay flexible to need | A role is a written purpose plus a short list of accountabilities — ongoing activities people can expect from it — not a vague job title carried in someone's head. If it isn't written, it isn't a real expectation: you can't be held to, or rely on, an accountability nobody can point to. The test: a new person could read the role and know what they've signed up for without asking around. |
| 5 | Energize role w/ full authority — act on your own judgment in role | Authority delegated within a mandate | Authority flows from the group | Within your role's defined domain you act on your own judgment — you don't need sign-off for decisions that fall inside it. “Energize” means you supply the initiative; the role is a container, and it does nothing until a person decides and acts. The trade is real autonomy in exchange for clear boundaries: full authority inside the lines, none outside them. |
| 6 | Don't wait for permission — act, adapt later | Escalate for oversight | Check in to stay aligned | If a reasonable action serves your role's purpose, take it now and adjust if it turns out wrong — don't sit on it waiting for someone to bless it. The default flips from “ask first” to “act, then correct,” which is what actually makes the org move at speed. The guardrail is your role's domain: act freely inside it, and surface a tension if you keep needing to reach outside it. |
| 7 | Roles filled voluntarily — a marketplace, opt in/out | Assigned by fit & competence | Volunteered, shared ownership | Roles are offered and accepted, not assigned by decree — it's closer to a marketplace than a chain of command, and you can hand a role back when it no longer fits you or you it. This means the people in roles generally want them, which beats grudging compliance. The flip side: if a needed role goes unfilled, that's visible data — real demand with no taker — not something to paper over by quietly drafting someone. |
| B · Tensions | ||||
| 8 | Process only your own tensions — bring what you sense | Managers triage & prioritize | Open floor — anyone surfaces anything | You bring only the gaps you personally sense — not what you imagine bothers someone else, and not a grievance you're relaying on another's behalf. If Bob has a problem, Bob brings it; you speaking for him produces a watered-down, un-ownable version no one can act on cleanly. This keeps the meeting grounded in real, felt signals from the people actually in the room. |
| 9 | No future/hypothetical tensions — only present & concrete | Plan / forecast ahead | Deliberate the what-ifs together | Process what's concretely present now, not “what if, six months out, this breaks.” Hypotheticals are endless and unfalsifiable — you can argue a maybe forever — whereas a present tension has a real current that points to a real next step. If the future risk is genuine, it usually shows up as a present tension (“we have no plan for X”), and then it's fair game. |
| 10 | Tension = felt gap, not complaint — gap → named better state | Structured feedback / review | Space to voice concerns | A tension is the gap between how things are and how they could be — name the better state you sense is possible, not just what annoys you. “This is broken” is a complaint; “we could resolve handoffs in a day instead of a week” is a tension with a direction to move in. Reframing a gripe into a proposed-better-state is the single move that turns venting into governance. |
| 11 | Don't solve in room — capture output — projects + next-actions | Decisive leadership closes items | Discuss to shared understanding | The meeting's job is to produce outputs — projects and clear next-actions with an owner — not to design the full solution live while everyone watches. Whiteboarding the whole fix in the room burns the group's time and usually belongs to one role doing focused work afterward. Capture “who will do what next,” then let that person actually solve it on their own time. |
| C · Decision-making (Integrative Decision-Making) | ||||
| 12 | Consent, not consensus — passes unless a valid objection | Clear decision rights, fast | Full agreement → deep commitment | A proposal passes the moment no one raises a valid objection — you don't need everyone to agree or like it, only for no one to show it causes harm. Consensus asks “does everyone say yes?”; consent asks “does anyone have a reasoned no?” — a much lower, faster bar. “I'd have done it differently” or “I don't love it” is not an objection; only a concrete harm is. |
| 13 | Objection must show harm — reasoned, role-based | Accountable owner decides | Every voice can shape or halt | To block a proposal you have to articulate why it harms or moves the org backward — preference, taste, and “I'd rather…” don't count. The burden is on the objector to make the case, not on the proposer to win everyone over; an unreasoned no carries no weight. This is what stops one anxious or contrarian voice from quietly holding the whole group hostage. |
| 14 | Safe enough to try — reversible → go | Due diligence before committing | Proceed when all are comfortable | The bar is not “is this the best, perfect, safe option” but “is it safe enough to try and reversible enough to undo” — if so, run it and learn. Most decisions are doors you can walk back through, and treating them as one-way traps you in analysis. You'll get real data from trying that no amount of pre-meeting debate would produce. |
| 15 | Object as a role — for a role's purpose | Raise it via your remit | Speak as an equal member | A valid objection is raised on behalf of a role's purpose — “this harms what Scheduling is accountable for” — not your personal comfort or your read of office politics. It must tie to the org's work, not to you. This keeps decision-making anchored to what the organization is actually trying to do, rather than to whoever feels strongest in the moment. |
| 16 | IDM steps are ordered — a fixed sequence | Agendas & decision protocols | Organic, inclusive discussion | The sequence is fixed — proposal → clarifying questions → reaction round → amend/clarify → objection round → integration — and the order is the point, not bureaucracy. Clarifying questions before reactions stops people attacking a proposal they've misread; one-at-a-time reactions stop debate-pile-ons. Following the steps is what lets a group move through a charged decision without it dissolving into a free-for-all. |
| 17 | Reactions/questions in their lane — no cross-talk | Chaired, with a speaking order | Everyone heard fully | A clarifying question only seeks to understand the proposal (“what does X mean?”), never to critique it in disguise (“don't you think X is risky?”); reactions are each person's own response, not a back-and-forth debate. No cross-talk: everyone reacts in turn, no one rebuts. Keeping the lanes separate is what makes the round fast and keeps the loudest voice from setting the tone. |
| D · Process & meetings | ||||
| 18 | Facilitator owns process, not content — a neutral steward | Leader sets direction & runs it | Shared / rotating facilitation | The facilitator steers how the meeting runs — whose turn, which step, staying in process — and stays deliberately neutral on what gets decided. They can hold the line on the rules hard precisely because they have no stake in the outcome. If the facilitator starts pushing their own preferred decision, they've quietly become a participant and the safety of the process collapses. |
| 19 | Open with a check-in round — each voices presence before work | Optional small talk | Open sharing to start | Each person says, briefly and uninterrupted, where they are right now — distracted, energized, worried about the deadline — before any work starts. It's not small talk: naming “I'm half here, kid's sick” lets the group read the room accurately and clears mental static so people can be present. One round, no responses, then into the work. |
| 20 | Close with a closing round — each reflects on how it went | Ends / quick action recap | Group reflection | Each person reflects, in turn, on how the meeting went — not redoing the decisions, but “that felt rushed,” “good to finally name the handoff problem.” This surfaces process tensions while they're fresh and is how the meeting itself gets better over time. It also gives a clean, deliberate ending instead of everyone trailing off the call. |
🧊 Icebox — Govern roles, not people (overlaps 1 + 4). Folded in rather than given its own seat: its one sharp corollary is the answer to “so can this thing tell me what to do?” — no; governance can only define the roles you choose to energize, never how you live.
Traditional and consensus columns are steelmanned — each model shown at its best. The contrast is to clarify Holacracy, not to dunk on the alternatives.