Authority without permission
The cost of a permission culture is not the delay. It’s what people stop proposing once they’ve learned that everything routes through one person.
Holacracy’s answer is to make authority explicit: roles with defined accountabilities, decisions that belong to a role rather than a rank, and a process for changing the roles. Do that properly and people act without asking, because asking is no longer the mechanism.
What has to be real
Three things, and skipping any one produces theatre.
The role has to actually hold the decision. If someone with a defined accountability makes a call and it gets quietly reversed, the whole structure is now decorative and everyone learns that in one incident.
The process for changing roles has to be light. Structure that can’t be amended in a meeting hardens into the bureaucracy it was meant to replace.
Ambiguity has to have an owner. Most real problems fall between roles, and distributed authority is silent about those unless you name who decides when nobody’s remit covers it.
The recognisable version is a decision sitting between two teams and belonging to neither — pricing page copy, error message wording, who owns a migration. Nobody is blocked, exactly. It gets raised, discussed and left, three times, across five weeks. The tell is that nobody can say what would have to happen for it to be settled. That isn’t a hard problem, it’s an unowned one, and the fix is one sentence naming who decides.
Where it breaks
Distributed authority is a coordination technology with a real cost, and the literature is quiet about it.
It is heavy. Explicit roles, governance meetings, and a process for changing the process is a lot of overhead for eight people who could just talk. Below a certain size it slows you down while feeling sophisticated — and above a certain speed, in a crisis, you want one person deciding fast and being wrong sometimes, not a process.
It also doesn’t remove power; it relocates it. Informal influence, tenure and who founded the company all still operate, now without an org chart making them visible. A flat structure with unacknowledged hierarchy is harder to challenge than an explicit one, because there’s no name on the thing you’d be challenging.
And it assumes uniformly high judgement. Autonomy given to someone without the context to use it isn’t empowerment; it’s abandonment with extra steps. New people especially need more direction than the model wants to admit, and “process-backed autonomy” is a poor substitute for someone senior saying: do it this way for now, here’s why.
The version I’d defend is narrow — push decisions to whoever has the context, say out loud who that is, keep the reversal rule explicit, and accept that some calls stay central.
Takeaway: structure + autonomy = agility.