Bureaucracy Is Usually the Fossil Record of Something That Once Went Wrong

Nobody sets out to create bureaucracy.

There is rarely a meeting where an intelligent group of people says, “What this organisation really needs is a twelve-page form, four approvals and a mandatory e-learning module that everybody completes while answering emails.”

Bureaucracy arrives more respectably than that.

Something goes wrong. A control is added. Someone forgets an important field, so the field becomes mandatory. A manager makes a poor decision, so future managers lose some discretion. An audit identifies a gap, so another sign-off appears. A customer complains, a regulator asks a difficult question, or a board member experiences an unpleasant twenty minutes, and somewhere in the organisation a new process is born.

Every addition makes sense. That is precisely the problem.

Most bureaucracy is not created by stupidity. It is created by perfectly reasonable decisions made one at a time. The absurdity appears later, when nobody stands far enough back to see what all those reasonable decisions have become together.

This is why bureaucracy is so difficult to challenge. Every individual rule has a parent, a justification and usually a story involving risk. Removing it feels reckless. Adding another one feels prudent.

And so, bureaucracy has a natural direction: It grows.

The Problem: Bureaucracy Is Organisational Scar Tissue

Earlier in this series, we described organisations as cognitive systems: systems that sense, remember, learn, protect themselves and adapt. Through that lens, bureaucracy becomes much more interesting than “too much paperwork.”

It is organisational scar tissue.

Scar tissue is not bad. It is evidence that the body protected itself after injury. An organisation behaves similarly. A financial loss becomes an approval. A safety incident becomes a procedure. A regulatory breach becomes mandatory training. A failed project becomes a governance committee. The organisation remembers pain by changing its behaviour.

This is often sensible. But scar tissue has an awkward property. Too much of it restricts movement. The protection becomes the constraint.

Imagine a public agency where a procurement failure leads to an additional approval. A later audit introduces a second check. A ministerial question creates extra documentation. Finance wants evidence. Risk wants sign-off. Procurement wants consistency. Legal wants assurance. Five years later, buying an ordinary office chair requires documentation appropriate to acquiring a minor defence system.

Nobody designed this outcome. Everyone designed their own sensible piece of it.

This is the bureaucracy paradox: locally rational decisions can create globally irrational systems.

The same happens in corporations. Following a regulatory incident, a bank may sensibly tighten product approval. Then Compliance adds a review, Legal adds another, Risk introduces a committee, Technology adds a security gate, Finance requires a business case, and Brand wants final approval. Eventually, the safest way to avoid product failure is not to launch a product at all.

The system has become extremely good at preventing one kind of risk by quietly creating another.

At CoEcosystem, we help organisations distinguish necessary control from accumulated organisational scar tissue, simplifying work without casually removing the protections that genuinely matter. Learn more at CoEcosystem’s website.

A Better Framework: The Bureaucracy Fitness Test

The solution is not a bonfire of policies. That is merely bureaucracy’s equally foolish cousin: simplification theatre.

Rules exist for reasons. Some protect lives, customers, assets, fairness, privacy and trust. The question is whether those reasons still justify the friction being created today.

Explore the Bureaucracy Fitness Test in our video/community discussion.

A useful test asks five questions.

1. What Pain Created This Rule?

Before removing a control, understand its history. What happened that caused it to exist? What risk was it designed to manage? What behaviour was it trying to prevent?

This matters because organisations are extraordinarily good at remembering the rule while forgetting the reason.

Once the original event disappears from corporate memory, compliance becomes detached from purpose. People know that three signatures are required, but nobody knows why. At that point, the process begins to acquire a slightly religious quality. “We have always done it this way” is not an explanation. It is organisational archaeology.

Understanding the original pain allows a better question: does the risk still exist, and is this still the best way to manage it?

2. What Does the Rule Cost Now?

Controls have visible benefits and invisible costs.

The benefit may be avoiding an error. The cost may be delay, duplicated work, cognitive load, reduced customer responsiveness, employee frustration and the loss of local judgment.

These costs rarely appear in the original business case because they are distributed. Ten minutes added to one task seems harmless. Ten minutes multiplied across 2,000 employees becomes an industry.

This is why bureaucracies can become enormous while every individual requirement appears small.

A five-minute form is almost never a five-minute form when multiplied by frequency, interruptions, checking, corrections, chasing and the occasional philosophical debate over whether “not applicable” means blank or N/A.

The right question is not merely, “Does this control reduce risk?” It is, “Does it reduce more risk than the friction it creates?”

3. Has the Protection Become a Substitute for Judgment?

Rules are particularly seductive because they remove responsibility. If the process says no, nobody has to say no.

If the committee approved it, nobody made the decision.

If all fourteen boxes were ticked, the outcome can be disastrous with everyone technically innocent.

This is the obedience trap.

A healthy control supports judgment. An unhealthy control replaces it.

Once employees discover that following the procedure is safer than producing the right outcome, they adapt quickly. Humans are remarkably good at learning the true rules of a system.

If challenging a pointless step creates career risk while following it creates customer pain for somebody else, guess which behaviour survives.

Compliance then becomes rational even when the result is absurd.

4. Can Someone Challenge the Rule Safely?

This may be the most important test.

Many organisations theoretically allow employees to question processes. In practice, challenging a longstanding control can make someone appear difficult, naïve about risk, disrespectful of history or worryingly enthusiastic about creating work for everyone.

So intelligent people stop asking.

A bureaucracy becomes dangerous when rules can be created easily but challenged only heroically.

Healthy systems build legitimate challenge into normal work. They ask periodically: what are we doing that no longer serves its original purpose? The aim is constructive challenge, not recreational rebellion.

A rule should not be immortal merely because its author has left the company.

5. Does the Rule Have an Expiry Mechanism?

There is a reason yoghurt has an expiry date and corporate policies generally do not.

We understand instinctively that food changes over time. Apparently, we are less confident that business conditions do.

Temporary controls have a remarkable tendency to achieve permanent employment. The emergency workaround becomes standard practice. The crisis committee develops recurring meetings. The additional report continues long after the crisis because stopping it now somehow feels more dangerous than starting it did.

A powerful design principle is therefore simple: new controls should require review.

Not “review someday.”

A date.

An owner.

A question: does this still earn its place?

This changes the default. Instead of requiring courage to remove bureaucracy, bureaucracy must occasionally justify its continued existence.

A Practical Example: The Approval That Nobody Was Really Giving

Imagine a large organisation where expenditure above a modest threshold requires three approvals. The process originally existed because spending discipline had been weak. Years later, almost every request is approved.

Managers complain about delay, but nobody proposes removing the approvals because the obvious question follows: “What if something goes wrong?”

So the organisation studies the data.

It discovers that the second and third approvers reject almost nothing. Their main function is not decision-making. It is reassurance.

The process is performing a psychological function: spreading responsibility.

This is important because simply deleting approvals may not work. People may recreate them informally through emails, meetings and “quick sense checks.” The scar tissue returns because the anxiety that created it remains untreated.

The organisation therefore redesigns the system rather than merely cutting steps. Low-risk purchases within clear boundaries move to a single accountable decision-maker. Exceptions trigger additional review. Spending patterns are monitored after the event. Managers receive clear decision principles, and unusual behaviour becomes visible through feedback rather than universal pre-approval.

Control has not disappeared.

It has moved. That is the difference between bureaucracy reduction and bureaucracy redesign.

One removes forms. The other removes unnecessary friction while preserving the intelligence of the control.

See how we teach this approach inside the CoEcosystem Academy.

The Real Shift

The real shift is from treating compliance as the highest organisational virtue to treating intelligent adaptability as the goal.

This does not mean abandoning discipline. Large organisations need rules. Hospitals need protocols. Banks need controls. Governments need due process. Airlines should not encourage pilots to express themselves creatively about landing procedures.

But there is an enormous difference between disciplined systems and obedient ones.

Disciplined systems understand why their controls exist. Obedient systems merely inherit them.

Disciplined systems protect important boundaries while allowing judgment inside them. Obedient systems treat deviation itself as suspicious.

Disciplined systems learn. Obedient systems accumulate.

This is where leadership matters. Leaders teach the organisation what kind of challenge is safe. If the person who simplifies a process is treated as reckless while the person who adds a control is treated as prudent, bureaucracy will grow. If career safety lies in saying “no,” the organisation will become extremely accomplished at not doing things.

Vision matters because it reminds people that the process is not the purpose. Storytelling matters because people need examples of courageous simplification that improved outcomes without abandoning responsibility. Feedback matters because rules should be tested against what they actually produce. Education matters because challenging bureaucracy constructively requires more skill than simply complaining about it.

And reward systems matter enormously. An organisation that celebrates people for removing unnecessary work sends a very different signal from one that only rewards those who successfully navigate complexity.

Bureaucracy, in other words, should be connective tissue rather than scar tissue. Enough structure to hold the organisation together, but not so much that it can no longer bend.

Sometimes progress is an innovation. Sometimes it is an AI system. Sometimes it is a new operating model.

And occasionally, progress is discovering that the most valuable transformation available to the organisation is deleting page seven of a form.

Further Reading

If this idea resonates with you, these books are useful companions for going deeper.

1. The Utopia of Rules, David Graeber. A provocative exploration of bureaucracy and the strange ways rules, administration and paperwork expand even in societies that claim to dislike them.

2. Seeing Like a State, James C. Scott. A powerful examination of what happens when institutions simplify complex human realities so they can be centrally understood and controlled. It is especially relevant to the gap between administrative neatness and lived reality.

3. Administrative Burden by Pamela Herd and Donald P. Moynihan. A valuable analysis of the learning, compliance and psychological costs created by administrative processes, particularly in public systems.

4. Rules for a Flat World by Gillian Hadfield A useful challenge to conventional thinking about rules and regulation, arguing for systems that can adapt more effectively to rapidly changing conditions.

5.The Logic of Failure by Dietrich Dörner A fascinating exploration of why intelligent people make poor decisions in complex systems, including the unintended consequences created by interventions that look sensible in isolation.

6. Simple Rules by Donald Sull and Kathleen M. Eisenhardt A practical argument for using a small number of well-designed rules to guide behaviour in complex environments rather than trying to control every possible situation.

Discussion Question

What process, approval, policy or report in your organisation began as sensible protection but may now have become organisational scar tissue, and when was the last time anyone was allowed to ask whether it still deserves to exist?