A familiar scene plays out in organisations that are trying to modernise how they work—whether they call it Agile, product operating model, "platform thinking," or just "becoming faster."
A customer-impacting incident is mentioned to the CEO when they ventured into the break room looking for a snack. Next thing a regulator is asking pointed questions. A critical delivery milestone is missed—the board issues a please explain which echoes down the org chart. And suddenly a transformation that had been preaching empowerment starts sounding like an all too common sermon when senior managers are embarrassed: "we need more control". Decision rights move upward. Committees proliferate. Everything get escalated—the noise to signal ratio increases. The organisation's nervous system tightens.
Then, as the dust settles, another problem emerges—usually less dramatic, but more corrosive. Teams wait weeks for approvals. Good people start to say, "I'll just do what I'm told"—a death knell of innovation. The organisation becomes safe(er)—at least for senior managers—and the pendulum swings back: "we need empowerment". The committees are disbanded. Layers are removed. Teams are told to "act like owners." The nervous system loosens.
If you've worked in organisations long enough, you've already seen this movie and its several remakes. Time to rewrite the script.
Mapping Control and Empowerment
Not every disagreement deserves the dignity of a polarity. Some are strategic trade-offs and require choice rather than synthesis. Others are category errors: two unlike things are thrown into the same quarrel and then treated as if they were rivals. But control ↔ empowerment belongs to a different class. It is one of the recurring structural tensions of organising, and it persists because both poles are necessary over time.
A brief map makes the point.
Pole A: Central control
- Upsides (when held well): coherence of direction, risk containment, enterprise-wide efficiency, architectural integrity, consistent customer experience, clear accountability.
- Downsides (when overdone): bureaucracy, slow decisions, compliance theatre, learned helplessness, talent flight, and the quiet spread of managerialism—where technique replaces judgement and process becomes a substitute for authority.
Pole B: Team empowerment
- Upsides (when held well): speed, local responsiveness, ownership, innovation at the edge, engagement, learning, and better use of frontline information.
- Downsides (when overdone): fragmentation, duplication, inconsistent standards, uncontrolled risk, everyone does their own thing, burnout from unprioritised demand, and what looks like autonomy but is really abandonment.
That is the polarity logic. Over-control buys order at the price of responsiveness. Over-empowerment buys initiative at the price of coherence. Each pole solves the mess created by the other—until it creates a mess of its own.
Why the Pendulum Always Finds a Reason to Swing
The more revealing question is not whether organisations need both control and empowerment. Of course they do. It is why senior teams keep behaving as though they must choose between them afresh every year.
Part of the answer is brutally practical: the two poles are not judged by the same standard. Control has one enormous political advantage over empowerment. It helps people who have little capability but a lot of positional authority to stay in power.
A new approval gate looks like action. A new committee looks like seriousness. A new dashboard looks like grip. When a regulator is asking questions, a major delivery has slipped, or the board wants a "please explain", these things are immediately legible as evidence that management is doing something. By contrast, the opportunities killed by delay, the initiative suffocated by escalation, and the talent quietly leaving because every decision now needs three signatures rarely arrive in the same crisp form. They are slower, more diffuse, and therefore easier to ignore—particularly when voiced by people at the bottom of the org chart.
Empowerment has its own advantage. It flatters the organisation's self-image. It sounds modern. It sounds developmental. It allows senior leaders to position themselves as enlightened opponents of bureaucracy. "Trust the teams" is a far more attractive slogan than "we failed to define decision rights properly." That is why empowerment programs are so often launched in tones of moral renewal and implemented with the rigour of a pep talk.
So the pendulum swings. After a visible failure, control regains prestige. After a period of stagnation, empowerment does. The organisation tells itself a moral story each time. Control becomes prudence; empowerment becomes courage. The trouble is that both stories are only half true.
Friedrich Hayek's (1899–1992) point about distributed knowledge still bites: people closest to the work usually see reality sooner than those higher up the hierarchy. If you want speed, adaptation, and better use of information, you cannot centralise every meaningful decision. But another point bites too: organisations are not loose collections of teams. They are systems that must coordinate across dependencies, risks, channels, and time. If you want reliability, trust, and scale, you cannot allow every team to operate as a sovereign state. Coordination is not a managerial affectation; it is a condition of collective performance.
Once one sees this, a less flattering picture comes into view. Many organisations are not really practising control or empowerment. They are performing them.
