Responsibility without authority is a familiar trap: someone is told to organize an event but must seek approval for every booking, expense, and change. Delegation removes that bottleneck by transferring actual decision rights alongside the work.
The boundary matters. An events team might choose speakers and spend an agreed budget while remaining unable to sign a long-term property lease. Within that space, it can act; outside it, another decision process applies.
A domain you can actually use
A useful delegation says what outcome the role serves, which decisions it controls, what resources it can use, and what constraints remain. The domain approach in sociocratic governance makes those relationships explicit. It also distinguishes the delegate's room to act from the delegator's continuing responsibility for the arrangement.
Delegation can fail in opposite directions. A manager may reserve so many exceptions that nothing meaningful has moved. Or they may announce “You're in charge” while withholding information, funds, or support when another department objects.
There is also a trust problem when authority can be withdrawn without explanation as soon as the delegate makes a different choice. A real handover allows judgment, including decisions the original authority would not have made. Review then concerns whether the domain is being handled well, rather than whether the delegate has learned to anticipate someone else's every preference.
Real cases
- The Manhattan Project: coordination at enormous human cost — Can mission achievement be separated from the legitimacy and costs of the mission?
- Apollo: a clear goal still needed a coalition — What makes a large mission survive beyond the person who announced it?
- Buurtzorg: small nursing teams with a shared backbone — What replaces middle management when a professional service scales?
- East London: importing self-management into an NHS organization — What happens when an autonomous-team model meets an existing institution?
- Haier: markets and microenterprises inside a giant company — How much autonomy can small enterprises have within a large corporate platform?
- Zappos: changing the rules and offering an exit — What can a forced governance transition reveal about consent and implementation?
- FAVI: autonomy under customers and peers — Where does control go when a factory removes supervisory layers?
- Semco: participation backed by business information — What makes employee discretion more than permission to give suggestions?
- GitLab: written context with one accountable decision-maker — How can a distributed team combine wide input with clear decisions?
- Loomio: different rooms have different decision rights — What must an online discussion space specify before its decisions mean anything?