n o ren
Systems & Organizations

The Holacracy Mirage

If you dissolve titles, the same senior voices still decide who gets the next product slot.

Giving every employee a self‑managed circle sounds like a shortcut to endless agility, but it also hides the real gatekeepers behind a veil of collective language. In a holacratic firm, each circle drafts its own purpose, yet the people who have spent years navigating the old hierarchy naturally become the unofficial arbitrators of budget and roadmap. When a new feature proposal lands on the front‑page of the governance meeting, the circles vote, but the few who have earned the reputation of “knowing the budget” quietly steer the discussion, approving only what aligns with their legacy priorities. This dynamic creates a paradox: the formal structure looks flat, yet decision velocity slows because the informal network still requires a handful of nods before anything moves forward.

The hidden gate shows up most sharply when a junior engineer drafts a bold experiment and circulates it through the circles. The proposal is praised for its language, but it stalls at the budget review circle, where the long‑standing members ask for additional data that never arrives, and the idea quietly fades. The organization has spent weeks on a paper‑trail while the underlying power structure remains untouched, turning the promise of rapid iteration into a silent bottleneck.

If you keep the circles but ignore the informal influence map, you’ll keep hearing “we’re flat” while the product pipeline thins and talent drifts.

Formal flattening does not automatically disperse decision power.
Identify recurring contributors in governance records to reveal the real de‑facto leaders.

Ignoring the hidden influence network lets decisions languish, eroding speed and morale.

The illusion of equality masks who truly controls resources, making it impossible to hold anyone accountable for delays.

1
Open the last three governance minutes, list every name that appears more than once, and note who authored the budget approvals.
2
In your next sprint planning, ask each team to name the person whose input they consider “essential” for any scope change; tally how many unique names arise.

The concept mirrors “informal organization” studies from sociology, which show that even in flat designs, long‑standing relationships dictate who gets heard. By mapping these ties, you can redesign meeting cadences to surface hidden dependencies rather than let them fester under the guise of self‑management.

The drawback is that exposing the informal map can trigger resistance; senior members may feel threatened and double‑down on secrecy, so any intervention should be framed as improving transparency for the whole group, not a power grab.