Most organisations treat compliance as evidence that their systems are safe.

They build policies, document processes and collect evidence that procedures were followed. Regulators ask for proof that controls exist and organisations produce it. Auditors ask for documentation and organisations produce more.

Gradually this activity becomes how organisations show they are in control. If a system passes audit it’s assumed the system is working properly.

But compliance and safety aren’t the same thing. Compliance shows that rules were followed, whereas safety requires that risks were actually understood and controlled.

Compliance offers safety through documentation

In theory, if regulators define rules and organisations follow them, risk should be reduced. Compliance frameworks are built on that assumption - follow the controls, maintain the documentation and the organisation will operate within acceptable limits.

In simple, small-scale environments the rules often map closely to the real risks. A checklist can prevent obvious mistakes and documentation can make responsibilities clear.

But as organisations grow, the relationship between rules and risk weakens. The rules stay the same while the system changes.

Operational reality diverges from the framework

Operational reality rarely matches the framework that’s supposed to describe it.

Teams encounter situations the compliance documents never anticipated. Systems evolve - new integrations appear, products change and staff turnover alters how work is done. When this happens the work continues but the documentation no longer describes it accurately - the gap between reality and documentation grows, processes are adjusted informally, exceptions appear and workarounds become business as usual.

Updating the compliance framework to match reality takes time, coordination and the agreement of the business. Most organisations choose the easier option - just leave the documents as they are.

Sometimes the gap appears because the system changes faster than the documentation, but in many organisations the gap isn’t accidental at all.

Compliance frameworks are often designed to satisfy regulators and auditors rather than to describe how the system actually works. Controls are written in ways that can be demonstrated easily, even if they only partially reflect operational reality.

In practice the distinction is usually understood by everyone involved. The compliance framework exists to satisfy the audit while the real system continues to operate through informal practices and operational judgement.

The compliance framework describes the organisation regulators want to see, not the organisation that actually exists.

Once documentation diverges, compliance becomes theatre

When documentation departs from reality its purpose changes.

Instead of describing how the system actually works, it describes how the organisation wants the system to look.

Compliance teams become responsible for maintaining this appearance. Their role isn’t to redesign the system but to ensure that the documented controls still satisfy auditors and regulators.

And so operational judgement gives way to managing the documentation.

Audits are rarely welcomed inside organisations. They slow work down, interrupt teams and often arrive with unrealistic expectations about how the system is supposed to operate. Nobody wants to be the person who blocks delivery because of an audit finding.

Auditors understand this as well. Their job depends on maintaining access and cooperation from the organisations they review. An audit that constantly obstructs operations will quickly become unpopular, and unpopular auditors aren’t invited back.

Before long both sides settle into a pattern - auditors look for evidence that controls exist, and organisations provide that evidence. As long as the documentation appears credible and the formal requirements are met, both sides can complete the exercise without disrupting the system too severely.

The result is a process that verifies the presence of controls more reliably than it verifies whether those controls actually work.

The question changes from whether the system is actually safe to whether the organisation can demonstrate that the required controls exist.

The difference sounds trivial but in practice it changes everything.

This behaviour resembles what Richard Feynman once described as cargo cult science. The rituals of science were reproduced carefully - the equipment, the procedures, the reports - but the discipline that made science work was missing.

Compliance regimes can drift into the same pattern. Policies exist, controls are documented and audits are performed, but the connection between those rituals and the real risks inside the system becomes weak.

A compliant system can still be dangerous

History provides plenty of examples.

Enron passed multiple audits before its accounting practices collapsed. Lehman Brothers continued to meet formal reporting requirements while using transactions such as Repo 105 to temporarily move liabilities off its balance sheet. Theranos passed regulatory inspections while the technology behind its tests failed to work reliably. FTX operated for years with investors, auditors and advisors who accepted governance signals that later proved meaningless.

In each case the organisations were able to produce evidence that controls existed. The frameworks worked well enough to satisfy auditors and investors, even while the underlying systems were breaking.

Cybernetics has a principle sometimes summarised as POSIWID: the purpose of a system is what it does. If a compliance regime reliably produces successful audits while real operational risk remains poorly understood, then passing audits is the system’s real purpose.

What failed wasn’t the existence of documentation but the reality those documents were supposed to describe.

A control may exist in documentation while being ineffective in practice. A process may appear complete while the real work happens outside the documented path. A risk may be visible to the people operating the system but invisible to the framework that claims to manage it.

Because the organisation passes audit, leadership assumes the system is under control.

The signal that something is wrong is suppressed by the evidence that the framework is satisfied.

Risk continues to grow, but the reporting structure is no longer designed to see it.

People adapt to the incentives the system rewards

If operational staff raise concerns that fall outside the compliance framework, they often discover that those concerns have nowhere to go. The framework already declares the system acceptable.

Over time people learn the practical rule - solve the problem but don’t challenge the framework.

Compliance teams adapt as well. Audits need to produce findings but the audit function also depends on maintaining cooperation from the organisation it reviews. Auditors who are constantly obstructive, pedantic or confrontational quickly become ineffective.

Findings are expected but they tend to focus on issues that can be addressed without disrupting the system too severely. The safest professional position becomes keeping the existing controls in place. This produces the same pattern of adaptive silence seen elsewhere in organisations.

Another set of incentives operates outside the organisation. Compliance has become an industry in its own right. Firms sell certification programmes, advisory services and frameworks designed to demonstrate that an organisation meets recognised standards.

Passing an audit becomes a credential that can be shown to regulators, investors and customers. In many industries compliance certifications have become standard requirements in procurement processes and investor due diligence.

The result is a system that rewards the production of compliance evidence. Organisations become better at demonstrating that the framework exists than at ensuring that the framework reflects operational reality.

The organisation eventually divides into two worlds - the real system that people operate and the documented system that auditors review.

The organisation becomes better at passing audits than managing risk

Once this separation exists, governance weakens rapidly.

Decisions begin to optimise for audit outcomes rather than operational safety. Controls are added because they satisfy frameworks, not because they improve the system. Documentation grows while understanding shrinks.

The people in charge believe the organisation is becoming safer because the evidence of compliance is increasing, but in reality the opposite happens. The system becomes harder to understand, challenge and fix.

Compliance didn’t fail because the rules were wrong. It failed because the organisation confused documentation with judgement.

Safety requires people who understand how the system actually works and have the authority to change it.

Compliance only requires evidence that the rules were followed.

What this explains

Organisations that pass every audit can still suffer catastrophic failures.

Incidents often reveal controls that technically existed but were ineffective in practice. The documentation said the risk was managed, but the system behaved very differently when it was actually used.

Operational staff sometimes feel that raising concerns about real risks is futile. The framework already declares the system acceptable so the concern appears to contradict the evidence.

Leadership teams often react with surprise when failures occur. From their perspective the organisation was compliant, and compliance was assumed to mean safety.

Documentation inside organisations continues to expand even while the systems themselves become harder to understand.

When compliance becomes the visible measure of responsibility, producing evidence becomes easier than improving the system.

What comes next

Once compliance badges become the primary sign of control, organisations begin to build structures that resemble governance but avoid the exercise of judgement.

Committees multiply, processes expand and decisions move through formal rituals that create the appearance of oversight while leaving the underlying authority unclear.

From the outside these structures look like maturity but internally they often serve a different purpose - they distribute responsibility so widely that nobody is clearly accountable for difficult decisions.

At that point governance debt shows up in its most obvious form - the organisation is surrounded by processes designed to demonstrate control, but those processes can’t resolve the difficult decisions that actually determine whether the system is safe.

Compliance can show that rules were followed, but safety still depends on someone accepting responsibility for whether the system itself is safe.

Most organisations claim to value disagreement. The people in charge encourage challenge and describe debate as a sign that decisions are being made properly. Teams are told that raising concerns is part of their responsibility.

In the early stages of a business this is often true. Small groups argue openly about product choices, technical approaches and commercial risks because the people involved have to live with the consequences of those decisions. Disagreement happens because the people doing the work still have the authority to change it.

Over time the level of disagreement often declines. Meetings become calmer, proposals are discussed with fewer objections and decisions seem to happen quickly. From the outside this looks like maturity, and leaders often interpret it as evidence that the organisation is aligned.

But disagreement rarely disappears because all the problems were solved - it disappears because people learn that disagreeing has a cost.

Disagreement creates friction

Raising an objection changes the tone of a discussion. It slows the meeting down and exposes assumptions. Someone has to defend their reasoning, and alternatives have to be considered. It also puts someone’s judgement on display, which means they can end up looking wrong in front of their colleagues.

Even in organisations that claim to welcome such challenge, these moments can still be uncomfortable. They interrupt momentum and reveal uncertainty. When moving things forward matters more than examining the assumptions, people quickly learn that disagreement isn’t always welcome.

Nobody has to say it out loud - people notice when objections are ignored, when someone who pushes back is described as difficult or when a meeting turns out to be ceremonial because the decision was already made elsewhere.

Disagreement only matters if someone can decide

When authority is clear, arguments have somewhere to land. The person responsible for the outcome listens to the competing views and eventually decides between them. The discussion may be uncomfortable, but it changes the shape of the decision.

When authority is unclear, disagreement becomes much harder to justify. Arguments move between teams without anyone responsible for deciding. Challenging a proposal may create tension without affecting the result. When people see that arguments don’t change outcomes, many simply stop arguing.

At that point raising objections starts to look risky.

Unclear authority makes disagreement risky

When nobody clearly owns a decision, raising an objection exposes the person making it but doesn’t guarantee the issue will be resolved.

People quickly recognise this. If raising a concern only creates political exposure without changing the outcome, the rational response is to stop pushing the issue.

Objections become softer, direct criticism turns into cautious questions, and difficult issues are deferred until later discussions that never quite happen.

The organisation continues to talk about decisions, but people challenge them less.

Consensus is the safer behaviour

Participants focus on avoiding disagreement rather than examining the assumptions behind a proposal. Discussions still happen but they are no longer about testing ideas. They are about maintaining agreement.

Silence begins to look like support, and the absence of objections starts to look like confidence in the decision.

Leaders often mistake that calmness for evidence that the organisation is working well.

The most capable people stop arguing first

Competent people pay attention to how decisions actually happen rather than how they are described. When they see that disagreement rarely changes an outcome, they stop putting effort into arguments the organisation has no way to resolve.

They continue contributing to the work but they withdraw from debates that they know will lead nowhere.

So the organisation becomes quieter without becoming more certain.

Silence starts to look like agreement

Once disagreement disappears, the information it would have brought into a discussion disappears with it.

Problems stop being raised, risks go unmentioned, and decisions are made with less information even though the organisation still believes everyone agrees.

Over time people adapt to what they see happening around them. They stop raising objections that won’t change the outcome. The organisation doesn’t eliminate disagreement through policy - it disappears through individual behaviour.

The result is adaptive silence - people still see the risks but they no longer bring them into the decision.

This is why many failures only appear obvious in hindsight - after the outcome is known, the weaknesses in the decision seem clear.

Inside the organisation those weaknesses were often visible much earlier but by the time the decision was made, the people who saw them had already learned that disagreeing wouldn’t change the outcome.

So they stopped disagreeing.

What this explains

Adaptive silence explains why organisations often seem calm before major failures. Absence of disagreement gives the impression that risks have been resolved when in reality they’ve simply stopped being discussed.

It also explains why capable people often say privately that problems were obvious long before the failure occurred.

The organisation didn’t lack intelligence - it had just learned to suppress disagreement.

What comes next

Once disagreement disappears, organisations still need ways to reassure themselves that decisions are sound.

In many industries that reassurance comes through process and compliance work. Documentation increases, controls are formalised and evidence is produced to show that the required steps were followed.

These mechanisms are often necessary - regulators, customers and auditors expect organisations to demonstrate that they operate in a controlled way. Over time whole industries form around producing that evidence, and organisations begin collecting certifications and compliance badges as proof that they are operating safely.

But once internal challenge disappears, those same mechanisms begin to carry a different weight. Following the process starts to look like proof that the decision itself was safe, and external certifications start to look like proof that the organisation itself is safe.

But compliance isn’t the same thing as safety.

Sometimes vision looks like leadership

Every business has a view about why it exists and where it’s going. In early-stage businesses, that narrative usually comes from the founder.

In well-run businesses the founder sets the direction but can still be challenged, and everyone knows who makes the call. People discuss risk openly, the person making the decision owns the outcome, and ambition for the future doesn’t excuse weak decisions in the present.

In some businesses, the founder’s vision starts to override the formal roles. Instead of asking who’s responsible for a decision, people defer to the founder. Formal structure still exists on paper, but senior people avoid deciding without first checking with the founder. People see confidence and assume it means the founder is right. They start working on what they think the founder wants, and over time more and more decisions depend on that one person’s judgement.

This doesn’t begin as dysfunction - it begins because letting one person decide is simpler. Real trade-offs are awkward and disagreement takes time to resolve, so someone who can make the call feels efficient rather than risky. Decisions move faster, friction drops and fewer arguments take place because everyone knows who will decide in the end. If decisions keep moving quickly and nothing obvious breaks, investors relax and employees start to see one person making the calls as efficiency rather than something to worry about.

It looks like leadership, and sometimes it is.

But the governance problem begins when the business can’t make important decisions without that person present.

Prestige is a barrier to scrutiny

Media attention makes fundraising easier. When money comes in and the early numbers look good, people start assuming the founder’s judgement is sound everywhere - not just where it has actually been tested.

That assumption affects who ends up on the board. Directors are chosen for their profile and networks - not because they are likely to push back. Once that pattern sets in, criticism inside the business is easier to dismiss as negativity or lack of alignment. Objections are treated as slowing things down.

In high-profile cases such as Elizabeth Holmes and Sam Bankman-Fried, the collapse was dramatic. Before that, the businesses looked successful, and the founder’s celebrity changed how people behaved. Leaders deferred controls they should have implemented early on. They skipped or delayed verification and accepted assertions without independent testing because challenging them meant slowing a winner.

Youth or ambition weren’t the problem. People postponed basic controls because nobody wanted to challenge a celebrated founder.

Most businesses don’t collapse like that, but the same behaviour happens in less dramatic ways in many of them.

Public recognition makes it harder to challenge the founder. When a founder appears on a high-profile list such as Forbes 30 Under 30, investors, employees and directors can see the endorsement. The founder is publicly associated with success before the business has faced real stress. Board members see that the market has validated this person, and employees see that investors believe in them. Questioning the founder now risks looking like doubt, not just inside the business but outside it as well.

As a result, directors ask routine questions less forcefully and soften their requests for evidence. They ignore weaknesses they can already see because they hesitate to slow down a business that investors and the press are celebrating.

Prestige doesn’t remove risk - it makes people less willing to confront it.

Businesses built on one person’s judgement can’t self-correct

Senior leaders who are meant to decide begin to wait instead. Meetings drag because nobody wants to commit to a position that might later be overturned, decisions stack up until the founder is available, and projects pause while they wait for approval.

As this repeats, people stop making decisions without checking first. They stop saying things they think will be rejected, and disagreements become personal because challenging a decision means challenging the individual behind it. The board adjusts around the founder instead of critiquing the plan itself. If that person is suddenly unavailable, the business stalls because it has never operated without their final sign-off.

If the founder were unreachable for ninety days, would the business continue to make decisions? Or would it wait?

If it would wait, the business already depends on that one person.

Charisma isn’t the issue. Many businesses are built by forceful founders. The problem begins when other capable people stop making calls of their own, when questioning a decision feels like questioning the individual, and when the board treats alignment with the founder as success.

In that situation, work pauses until the founder weighs in. Controls are postponed because “there’s a plan” and responsibility moves upward because everyone knows the final word will sit at the top anyway. People schedule more meetings because they want reassurance before committing and want to avoid being overruled.

The business may continue to grow and even perform well for a while, but when pressure increases the cracks show. Decisions slow further and errors go uncorrected. The business discovers that nobody knows how to decide without one person.

That isn’t inspiration - it’s dependence.

What this explains

When one person’s judgement overrides everyone else’s role, problems sit unresolved for longer.

The business may grow quickly, and it may look aligned and even outperform for a time. But bad news travels more slowly. People think twice before raising doubts, and silence is mistaken for agreement. When pressure increases, people defend the leader’s position instead of testing the evidence.

The point of governance is to make it normal to disagree without it becoming personal, and to make responsibility clear. When authority is about personality rather than role, people stop challenging decisions.

Failure doesn’t usually arrive all at once. It builds through postponed checks, softball questions and decisions that nobody examined properly.

What comes next

When questioning a founder becomes uncomfortable, people don’t suddenly become blind. They still see the risks and the weak assumptions. They simply become more careful about saying so.

Meetings run more smoothly because fewer people challenge the direction. Disagreement moves offline or disappears altogether. The business looks aligned, but that alignment comes from caution rather than conviction.

This is how the next problem begins. Not through formal power shifts, but through behaviour. Capable people choose silence because there is a cost to speaking up.

The next essay examines that change in behaviour.

We always blame the decision

When a project fails, a product misfires, a regulator intervenes or a target is missed, the organisation conducts a review. There’s a post-incident report, a post-implementation review, a board discussion or an audit response. These are necessary parts of governance.

The review reconstructs the timeline of events. It identifies key moments and isolates the decision that appears to have led to the outcome. Someone approved the launch, signed off the risk or chose to proceed.

The conclusion is familiar - the decision was wrong. We moved too early, or we underestimated the risk, or leadership misjudged the trade-off.

Such a reassuring explanation implies that a functioning decision structure existed and that the failure resulted from flawed judgement within it. But in many serious failures the problem wasn’t the decision - it was that the organisation had never clearly designed who had the authority to decide.

Reviews are built to find decisions

Formal reviews are designed to analyse decisions. In the aftermath of failure, boards, regulators and executives need a coherent narrative, a root cause and accountable owners. The process assumes that at some identifiable moment a defined authority weighed explicit trade-offs and chose a course of action.

If that structure already exists in the organisation, then analysing judgement makes sense. The difficulty arises when authority was never properly designed into the organisation. The review still needs a decision, so it settles on the most visible approval and treats it as the root cause. The most senior participant becomes the decision-maker. Thus, the absence of clear authority is reinterpreted as a bad decision.

The review isn’t designed to conclude that nobody had clearly defined authority. It’s designed to evaluate how authority was used.

Process is not authority

Post-calamity remediation usually follows the same logic. If the failure was a bad decision, the solution is to constrain decisions more tightly. Additional approval gates are introduced, committees are formed, policies are updated and sign-offs multiply.

This feels rational - something went wrong at a decision point so the decision process is strengthened. But process and authority operate at different levels. Process defines the steps, but authority defines who has the final say and who carries the risk.

If it wasn’t clear whether Product or Risk had the final say on launch, adding a joint sign-off doesn’t fix the ambiguity - it just puts two signatures where there was one. If they disagree, who wins? If the launch fails, who owns it? If those questions aren’t answered, nothing has changed.

Creating an escalation path doesn’t solve this either. If nobody knows who has the final say at the top, the escalation doesn’t help. Process can support authority but it can’t replace it.

More process, same ambiguity

When failure is blamed on a bad decision, behaviour changes but the underlying power structure doesn’t.

People respond predictably. Meetings expand because greater participation reduces individual exposure. Documentation increases because written records are defensible, and approval chains lengthen because shared signatures distribute responsibility. Each change is rational but still none clarifies who has the final say.

Over time additional steps accumulate while the original uncertainty remains. Responsibility becomes diffused and decisions slow down, not because judgement is more measured, but because ownership is unclear. The organisation appears more controlled but it’s still uncertain who decides.

The cargo cult of learning

Each review produces visible action. Root cause analysis is conducted, action trackers are maintained, executive sponsors are assigned and controls are added.

It looks like learning but if nobody has clearly defined who decides, those rituals can’t fix the problem. They change the paperwork but they don’t change the power. The surface structure shifts but the underlying lines of authority don’t.

The organisation leaves the review believing it has acted because it has altered something observable. What it hasn’t done is clarify who has the final say. So the next failure happens under the same rules.

Some failures are bad decisions

Not every failure is structural. Some decisions are simply wrong.

But you can only say that if the system around the decision was clear. It must have been obvious who had the final say, what risks they owned and what trade-offs they accepted.

Only then does it make sense to judge the decision itself. If those things were never clear, blaming judgement misses the point.

What this explains

If failures keep being blamed on bad decisions when the real problem is unclear authority, the organisation is fixing the wrong thing.

It changes behaviour, it adds steps, it increases oversight. It doesn’t clarify who decides.

Judgement depends on structure. If it’s unclear who has the final say, who owns the risk and how disagreement is settled, fragile decisions are inevitable, no matter how capable the people are.

When that confusion is repeatedly treated as poor judgement, nothing changes. Each review adds more process without settling who is in charge.

If the problem is structural, the fix has to be structural - make authority explicit.

For every serious decision area, the organisation should be able to answer:

• Who has the final say?

• Who owns the risk if it goes wrong?

• Who can stop it?

• How are disputes settled?

• Where is the decision recorded?

If those answers are unclear then nobody is really in charge.

Process can support clarity but it can’t create it.

What comes next

When it’s unclear who decides, and that confusion keeps being blamed on judgement, the problem doesn’t remain a minor irritation.

Each cycle of failure and review adds controls without answering the basic question of who has the final say. Over time, unclear lines of authority become normal practice. Committees multiply, reporting lines expand, but nobody quite remembers when the confusion started.

At that point the issue is no longer a single bad decision or a single weak review. It’s a system that’s just built that way.

The next question isn’t how to run better post-mortems. It’s whether a system built on years of unclear authority can be untangled at all.

Speed is not decisiveness

Speed is often mistaken for decisiveness because at a glance they look similar. Both involve activity, feel urgent and create the impression that something is happening. But they aren’t the same thing.

Decisiveness begins with authority. Somebody has to be explicitly empowered to decide – not just to recommend – but to choose a course of action. That authority only matters if it’s paired with accountability because the person making the decision must also accept ownership of the outcome, including failure. Without that pairing, authority is just performance.

Real decisions are rarely made with complete information. They are made under uncertainty, with incomplete data, real trade-offs and unclear second-order effects that exist whether or not anybody acknowledges them. Exercising judgement under those conditions is what decision-making actually involves.

Making a decision doesn’t guarantee a good outcome, but avoiding a decision guarantees that events will decide for you.

Decisiveness also depends on permission to be wrong. If being wrong is punished more than being indecisive, people protect themselves by avoiding that commitment. Work continues, discussions multiply and activity replaces choice.

Speed theatre asks for none of this. It substitutes activity for a decision. The activity feels responsive, reversible and socially safe. It looks like progress, but it avoids the moment where somebody would have to own a choice.

Speed theatre optimises for looking busy - not for being correct.

Speed theatre replaces decision-making

Speed theatre always shows up in the same patterns.

Work starts before anyone decides which direction to take. Teams are told to “get moving” while the key questions remain unresolved.

This isn’t iterative delivery. Iteration improves a chosen direction. Speed theatre avoids choosing one at all.

Instead of deciding what matters, the work is reshuffled. Nothing is cancelled or committed to.

Parallel initiatives appear because everything is treated as a priority. When asked to choose, the answer is “all of them.” Nothing is stopped, so everything continues.

Iteration language covers the lack of a decision. “We’ll learn as we go” becomes a way to defer commitment rather than a method for reducing uncertainty and supporting a decision.

None of this is accidental. These patterns exist because they feel safer for individuals. Nobody has to say no, be visibly wrong or own a trade-off. Risk stays inside the work instead of being addressed by a decision owned by a person.

The cost only becomes visible later.

Speed theatre feels safer than deciding

Speed theatre protects people from exposure. If nothing is ever clearly decided, nobody can be clearly wrong.

In organisations where process is a substitute for authority, authority is diluted across roles and committees. When outcomes go badly, the explanation becomes “this is how the process works,” not “that was my decision.”

Trade-offs are avoided - choosing one priority means rejecting another, and rejection creates conflict - so it’s easier to approve everything and let capacity sort it out later.

When failure does arrive there’s always visible effort to point to – slides, meetings, deliverables. The absence of a decision is obscured behind the work done.

This persists because certain incentives are the same for everyone in the organisation - being visibly wrong carries more personal cost than allowing ambiguity to continue. A clear decision names the person responsible. Ongoing activity points to a process.

As a result, momentum, responsiveness and effort are praised because they don’t expose individuals. Clear decisions do.

Speed theatre allows people to appear in control without accepting the consequences of deciding.

The decisions you don’t make become permanent constraints

Decisions that aren’t made explicitly don’t disappear - they just become constraints.

When work begins without a clear decision, the choice is still made. It’s just made by default rather than by someone.

Governance depends on explicit choices, named owners and defined trade-offs. Speed theatre removes all three. There’s nothing to review, nothing to challenge and nobody clearly accountable.

Assumptions are treated as facts. The real constraints only appear later - budgets already spent, systems already integrated, commitments already made. By then the work is under way and stopping is difficult.

By the time failure becomes visible, reversing course means undoing work, contracts and commitments. What looks like momentum is the result of decisions made by default rather than by someone.

At that point governance can only react. Stopping now means admitting earlier indecision and absorbing visible loss. Continuing hides it.

This is governance debt. Not a single bad call, but a series of decisions that were never made explicitly.

Speed theatre is easy to recognise

You can see speed theatre in how work starts, how delivery is praised and how governance behaves.

These patterns aren’t signs of bad people or low effort – they show a system that rewards avoiding decisions while preserving the appearance of progress.

Operational patterns

• Work is approved to start but nobody can state the decision it implements.

• “Phase zero” artefacts multiply while go or no-go decisions never occur.

• Stopping an initiative requires more meetings than starting it did.

Delivery patterns

• Teams are praised for velocity while outcomes remain undefined.

• Deadlines move but scope is never consciously re-chosen.

• Multiple solutions are funded because choosing one would upset somebody.

Governance patterns

• Steering committees exist but nothing is ever decided there.

• Silence is treated as alignment.

• Risks are logged but nobody owns the ones that matter.

• When these patterns are present, failure is the predictable result of decisions that were avoided and later denied.

What this explains

Speed theatre isn’t a delivery problem. It’s a governance failure that shows up as activity without decisions.

When organisations confuse action with decisiveness they create systems that look busy while avoiding decisions.

Work starts early, effort is visible and progress can be dashboarded, but nobody clearly chooses a direction. By the time outcomes appear, they look like execution problems. The damage was done earlier, when decisions were deferred and ownership was unclear.

Speed theatre doesn’t mean nobody cares – it means the system rewards visible effort more than it rewards judgement. Over time, people adjust to the reality and so the organisation becomes good at moving and bad at deciding.

That’s how failure is built into the organisation long before it’s visible.

What comes next

Speed theatre isn’t a personality flaw or a delivery technique gone wrong. It’s a symptom of a governance structure that avoids explicit decisions.

By the time you see motion without direction the underlying problem is already there - diluted authority, unclear ownership, and incentives that reward activity more than judgement.

The next essays step back from delivery and examine the structures and incentives that sustain this pattern - how authority exists on paper but not in practice, how process replaces personal responsibility and why organisations keep systems that avoid clear decisions.

Speed theatre is what this looks like in action.

What comes next examines the system that produces it.

Assigning titles is a governance decision

Many organisations treat titles as labels. They see them as a way to explain roles, motivate people or make hiring easier. A title goes on a business card, a LinkedIn profile or a job ad.

Because of that, titles are treated as cosmetic. They’re useful for recruitment, pay bands and reassurance, but not something that’s seen as shaping how the organisation actually operates.

That’s why you often hear the same refrain in the same breath – “titles don’t really matter here”. They’re described as informal, flexible or secondary to “how we really operate”.

That way of thinking is comfortable, but it’s wrong.

Giving someone a title is a governance decision. It determines who can act, who gets listened to and who pays for failure – often without anyone realising it.

Ignoring those governance questions when titles are bestowed doesn’t make them disappear – it just means the answers are never made explicit.

Titles only really matter under pressure

When things are calm, people talk things through, interrupt each other and defer to the people who actually do the work.

That stops happening under pressure. When uncertainty arises people start looking for hierarchy, seniority and titles. Decisions go to whoever has the most senior-sounding title regardless of intent, culture or how the work is actually done.

External parties do the same. Investors, auditors, partners and regulators usually only see titles, not how decisions are actually made inside the organisation.

“Titles don’t matter here” is governance avoidance

Founders often say this with pride. What it usually means is that authority hasn’t been designed yet and is being left unresolved.

At small scale, constant interaction fills this gap. People talk all the time, share context and work things out informally.

That works briefly, but as scale arrives it stops working. Authority remains implicit, decisions drift and governance debt starts to accumulate.

Titles become decision shortcuts when authority is unclear

When time is short, process disappears first. Role descriptions are ignored and decision frameworks get bypassed.

Decisions end up with whoever has the most senior-sounding title, even when someone else is responsible for delivery. The decision gets made by the title and there’s no mechanism to reassign authority or accountability.

Governance debt forms when authority, ownership and capability are misaligned

Titles often give people authority even when they don’t own the work or understand it. Decisions are taken by those insulated from the consequences of making them.

When things go wrong, everyone shares the blame. When things go right, one or two people take the credit. Post-mortems explain what happened, but they don’t settle who was responsible for delivery or who had the right to decide.

That misalignment – authority separated from ownership and capability – is governance debt in its purest form.

Inflated titles hard-code authority

Startups hand out inflated or vague titles to secure early hires, reassure investors or manufacture credibility. Handing out those titles feels inconsequential at the time but it isn’t.

Once issued, titles become politically difficult to undo unless you fire someone. Later structure has to bend around those early assumptions. The distortions get carried forward as the organisation grows, even when they no longer match reality.

This isn’t accidental. The modern title fetish is largely a Silicon Valley export.

Venture markets rewarded the appearance of maturity long before maturity existed. Titles became pitch-deck artefacts. “Head of Sales” sounded safer than “first salesperson”. “CTO” sounded reassuring even when there was no technology organisation to lead.

Startups kept the symbols and discarded the constraints that once made them meaningful. They copied the symbols but not the capabilities.

This is classic cargo-cult thinking – copy the external form, ignore the internal mechanism and expect outcomes to follow.

In practice, the result is that senior titles approve decisions while someone else is left to deliver and absorb the fallout.

Titles feign governance until scale exposes the cost

Assigning titles feels like progress. It creates the appearance that structure is agreed, makes chaos feel organised, signals control and delays the hard work of deciding who actually owns what.

Copying titles is cheaper than building capability. Deciding who can decide what takes time, but issuing a title takes minutes.

So organisations reach for the easy button.

As headcount rises, the informal alignments that once worked in place of explicit decisions stop working. Every unclear title adds friction to decisions and escalation. Meetings multiply to compensate, and speed drops even as “capacity” increases.

What looked harmless early becomes structurally expensive later.

Poorly thought-out titles distort where decisions get made. Authority ends up with people who don’t carry responsibility, while responsibility lands with people who lack authority. The org chart stops describing reality, but everyone continues to act as if it does.

Titles only work when authority comes with accountability

The claim here isn’t that titles are stupid. Large systems need simple ways to indicate who’s in charge.

But a title is only meaningful if the organisation can answer three questions:

• What decisions can this role make?

• What outcomes does this role own?

• What happens when those outcomes fail?

When the answers are unclear, the title is a liability.

Titles are neither good nor bad but issuing them without explicitly defining their authority and accountability is a high-interest form of governance debt.

By the time organisations admit they have a title problem, what they really have is a structural problem in how authority and accountability were assigned in the first place – one they postponed until it became expensive.

What this explains

Titles aren’t an HR hygiene issue – they’re one of the earliest ways organisations allocate authority.

When titles are issued casually they hard-code authority early. Under normal conditions that may not matter much but under pressure it matters immediately.

This is why title problems rarely show up as “title problems” – they appear as slow decisions, unclear ownership, endless escalation or leadership that looks busy but never decisive. When the problems show up, who actually decides things was settled years ago.

In practice, many organisations already run on their titles, whether they planned it or not. The org chart shapes who gets listened to and who doesn’t, without anyone stopping to question it.

What comes next

Titles are an early way governance debt gets locked in. They shape authority before anyone realises it’s happening.

The next essays shift from who is allowed to decide to how decisions are avoided, diluted or endlessly deferred once organisations grow.

• How speed and urgency become substitutes for judgement.

• How meetings and forums replace clear decision ownership.

• How roadmaps and escalation processes absorb risk without resolving it.

Later in the series the focus shifts again to why these patterns become hard to reverse and why even competent people end up defending systems that no longer work.

The theme stays the same throughout – governance debt isn’t created by bad intent – it’s created by structures that make avoidance easy and accountability optional.

If this were only about individual leaders, the same failures wouldn’t repeat so predictably across different teams and companies.

Behaviour changes before rules do

Exception culture is one of the fastest ways governance debt accumulates because people start acting differently before anyone decides that the rules have changed.

Exceptions are easy to justify when the normal process doesn’t solve the problem, and the risk isn’t visible at the time the decision is made.

The problem isn’t the exception itself. The problem is what happens when the organisation treats such changes in behaviour as if nothing changed.

An unacknowledged exception is a rule change

An exception is a deviation from the normal way of working. If nobody has to acknowledge it as such, the way work is done has already changed.

In practice most organisations approve exceptions without doing four basic things:

• Naming the trade-off being accepted.

• Assigning ownership.

• Recording the risk or how it will be managed.

• Defining when normal behaviour will resume.

So work continues and the system absorbs the exception but the organisation’s understanding of how it now operates isn’t updated. People continue to treat the system as if the exception never existed. The work moves on, and nothing in the system brings the exception back into view.

A single exception usually has little impact. Repeated exceptions that are never addressed change how the system behaves.

Repeated exceptions become the default

Exceptions recur in the same parts of an organisation because that’s where the normal process doesn’t work. Without an explicit decision to stop them, temporary deviations become the default.

After a few repetitions people plan and decide based on what has happened before, not on what the rules say. Behaviour changes but governance doesn’t. That’s how governance debt is created.

This happens without a single obvious bad decision being made. Each exception widens what people treat as normal without anyone explicitly agreeing to the consequences.

Over time people stop referring to these situations as exceptions at all. They stop saying “this isn’t how it’s supposed to work” and start saying “that’s just how things are”.

The organisation starts acting differently while still claiming to follow the same rules. In that gap decisions default to whoever happens to be involved at the time rather than to any explicit authority. That’s where governance debt lives.

Exceptions postpone proper decisions

Exception culture is often defended as pragmatism – the commercial way, the can-do attitude, “agility”. But when nobody is honest about its limits this just becomes a way of pretending trade-offs don’t exist.

Exceptions allow work to continue without deciding what can’t be done. Nobody has to commit to a limit, so instead of confronting those limits the organisation postpones the decision by treating each case as “special.”

The cost doesn’t disappear – instead it gets displaced onto teams, timelines and the organisation’s ability to plan.

Teams are repeatedly asked to handle cases differently. Over time there is no longer a single standard way of working - only a growing set of exceptions. Work takes longer, but no single decision accounts for the delay.

Scale removes shared understanding

Small teams feel the impact of exceptions immediately. They handle them through shared knowledge rather than explicit decisions, and the cost shows up directly as confusion, delay, rework and fatigue.

Larger organisations pay a different price – they lose the ability to explain how work is actually done.

As people leave the organisation, the reasons for exceptions leave with them. The exceptions remain, but nothing explains why they exist or when they should stop.

What began as flexibility turns into unpredictability. Once coordination across teams matters, that unpredictability becomes a serious risk.

What this explains

Exception culture doesn’t make an organisation more adaptable. It just makes it harder for anyone beyond the immediate participants to understand.

In such an environment nobody can say which rules really matter. Risk is carried implicitly by individuals because decisions are made without clear authority or organisational ownership. When something fails it becomes impossible to explain which exception mattered or why it was allowed to persist.

Exceptions are unavoidable. Failing to recognise them is not.

An exception can be a real decision but only if it’s treated like one:

• The trade-off must be named.

• Someone must own it.

• Its cost must be understood.

• Its boundaries must be clear - what it applies to, how long it lasts and what authority and standards remain unchanged.

When behaviour changes without that work being done, someone else ends up dealing with the consequences later.

A system is defined by what it produces, not by what it claims to produce. As unacknowledged exceptions accumulate, its purpose changes without ever being discussed or agreed.

What comes next

Exception culture survives when nobody can say “this stops now”. Nobody has the authority or the obligation to end deviations once they are no longer justified.

Until that changes, exceptions stop being temporary and become the way work is actually done. At that point the organisation is no longer choosing how it operates – it’s discovering it after the fact.

The next question is where that authority is supposed to live, and why it so often isn’t home.

Ownership is assumed, not defined

Every organisation claims it has ownership of decisions but very few can name who owns which decisions, or what authority that ownership carries.

Ask who owns a decision and the answers sound reasonable enough to pass without challenge – it “sits with the team”, it’s “shared”, it’s “aligned across functions”.

These phrases are treated as signs of maturity, but in practice they describe the absence of a decision-maker. They don’t identify who has the right to decide – they just confirm that no one wants to say who has the right to decide.

Sorting out ownership later doesn’t create authority

If ownership isn’t explicit at the moment a decision is made, then no one was authorised to decide. That gap can’t be fixed later by reviewing who was involved, who attended meetings or who was held accountable once the outcome was known.

Assigning ownership after the fact doesn’t create authority – it only disguises the fact that the decision was made without it. The organisation gets the comfort of a named owner while the underlying failure remains unresolved.

This is how organisations mistake post-hoc accountability for governance. Decisions are allowed to proceed without authority, and responsibility is sorted out later, but only if the outcome is bad. The lack of authority that caused the problem in the first place is never addressed.

When ownership is vague, decisions don’t stop happening – they just happen without anyone clearly authorised to make them. Work moves forward, consequences accumulate and the organisation adapts to outcomes it never properly agreed to.

Shared ownership breaks under pressure

Shared ownership works only while there is agreement. As soon as people disagree, nobody is authorised to resolve the issue, so escalation becomes the formal path forward.

In practice, escalation is slow or avoided. Decisions stall, meetings increase, and work continues only because people keep moving, not because anyone has decided.

Eventually something forces a resolution – time pressure, someone more senior stepping in, fatigue or politics. The decision exists but nobody clearly owns it. It can always be reopened because no one can honestly say, “This was my call.”

Ownership gaps are always filled

A missing owner doesn’t leave a void. Authority reappears informally rather than being explicitly assigned. It ends up with whoever sits closest to authority, controls information, or keeps pushing.

This doesn’t always happen because people want control – more often it happens because someone just wants things to work. Decisions get stuck, consequences are real and someone feels responsible for the outcome even without formal authority, so stepping in becomes the least bad option.

The organisation benefits from this behaviour because it keeps work moving. Over time this informal authority becomes normalised – not because it was a conscious decision but because nothing else was available.

These structures form without being acknowledged and are defended as necessary once in place. The organisation insists it’s flat and collaborative while being governed by people whose authority was never formally assigned. Governance debt doesn’t form because authority exists, but because it exists without visibility or constraint.

Scale exposes the damage

In small teams unclear ownership causes fewer problems because the same people are involved in most decisions and can resolve issues informally. Mistakes are noticed quickly and fixed without escalation.

As organisations grow, that tolerance disappears. Decisions begin to cross teams, products, contracts and regulators. Each boundary makes unclear authority harder to work around. People spend their time coordinating with each other instead of making decisions.

As a result, headcount increases and throughput falls.

This is often described as bureaucracy, but it isn’t – it’s the cost of never deciding who decides.

Titles don’t grant authority

Adding titles is a common response – Head of, Lead, Sponsor.

Titles imply ownership without granting authority. Everyone assumes the title holder can decide but the title holder assumes consensus is still required, so nothing moves.

Ownership means someone is allowed to make the decision – not that they hold a particular role.

If a person can’t say clearly and publicly that they own a decision and accept its trade-offs, then ownership doesn’t exist.

Unclear authority drives defensive behaviour

Teams no longer know whose decisions carry authority, so people act defensively rather than decisively. Escalation depends on who you involve rather than a defined process.

Capable people disengage - not because the work is difficult but because the rules are unclear.

The organisation continues to function, but under pressure it can’t act decisively because nobody was ever authorised to decide.

What this explains

Governance debt isn’t only created by deferred decisions – it’s also sustained by unclear ownership.

When decisions have no clear owner, people make them anyway without a formal mandate.

Over time, rules and steps appear where someone should have been able to decide.

Organisations become slower - not because they lack talent or effort - but because they never resolved who was allowed to decide.

This is why governance debt is so persistent. It embeds itself in everyday behaviour - not policy documents.

What comes next

When ownership is vague, organisations introduce workarounds to keep work moving – one-offs, temporary workarounds, special cases.

These exceptions feel justified at the time but they’re also how whatever ownership remains is eroded.

The next essay examines exception culture and why it’s one of the fastest ways to turn governance debt from a problem into the normal way work gets done.

Governance debt is caused by decision avoidance

Governance debt is often explained as the result of difficult decisions made under pressure.

That explanation is comforting because it suggests that failure comes from moments of bad judgement – a wrong call made too fast, in imperfect conditions. It sounds decisive and action-orientated.

That explanation doesn’t survive scrutiny.

In reality most governance debt isn’t created by bad decisions - it’s created because decisions, risks and assumptions are never properly recognised, described or discussed in the first place. Disagreement is suppressed or never actually takes place. Meanwhile silence is mistaken for alignment and ignorance is treated as an acceptable state in a “fast-moving environment”.

By the time failure shows up the behaviour that caused it is already routine.

Governance debt isn’t technical debt

Technical debt results from conscious trade-offs. A team knows it’s taking a shortcut – and in most cases there’s a reason, an owner, a rationale and at least an implicit understanding that something bad has been accepted in exchange for speed or convenience.

Governance debt is different because it usually doesn’t come from explicit trade-offs. Instead it comes from avoidance, blindness and silence – often disguised as pragmatism, social awareness or maturity.

Technical debt comes from choosing to accept a known compromise whereas governance debt comes from not making a judgement at all.

Governance debt is created when a decision that matters never happens.

Everything that follows describes how organisations learn to live with that failure.

Deferral

The decision is deferred until it no longer looks like a decision.

Deferral is often justified as a response to urgency.

“We don’t have time to deal with this now.”

“Let’s get through this phase first.”

“We’ll come back to it later.”

Sometimes that’s true but more often deferral happens because people lack the competence to recognise or describe the issue clearly enough to understand that a decision needs to be made, or to make the right decision.

They defer because:

• They don’t fully understand what’s at stake.

• They can’t describe the trade-offs.

• They don’t have the confidence or capability to have a difficult conversation.

• They don’t realise it’s their decision to make.

• Doing nothing is easier than thinking.

Deferral is treated as prudence because it looks calm and carries no immediate cost.

Silence

Risk is seen and left unspoken.

More damaging than deferral is demurral – the choice not to raise an issue at all.

This is the most common way decisions disappear.

People notice problems – they sense risk, feel unease and then they say nothing.

They stay quiet because:

• Politeness is valued over clarity.

• Disagreement is framed as negativity.

• Certain views are politically or socially fashionable and therefore protected.

• Questioning the consensus carries reputational risk.

Silence is rational behaviour in systems that reward smoothness, alignment and narrative coherence. Speaking up is costly. Saying nothing is safe.

This isn’t a failure of courage – it’s a rational response to an environment that actively discourages the wrong kind of judgement.

Blindness

What isn’t safe to see eventually can’t be seen.

The most dangerous cases aren’t deferral or demurral but failure – or refusal – to recognise that a governance issue exists at all.

Deferral and silence delay decisions. Blindness removes the decision entirely.

Sometimes this is genuine incapability. Many people simply don’t see the problems that sit one step beyond what’s in front of them. If something looks familiar and hasn’t failed yet, it’s treated as safe. “It’s worked so far” is mistaken for understanding why it works.

But very often the blindness is wilful. Someone senses that something is wrong but pursuing it would:

• Disrupt the agreed narrative.

• Conflict with personal incentives.

• Challenge an ideological or reputational agenda.

• Force uncomfortable trade-offs.

In some organisations speaking up about real risks can damage your career. When raising a problem leads to discipline or isolation, people learn quickly to stay quiet. The signal is ignored not because it was invisible but because acknowledging it would be costly.

This isn’t ignorance – it’s how people stay employed.

Assumption

Silence is laundered into innocence.

Many governance failures are explained with one phrase:
“Everyone assumed…”

What actually happened is simpler. The issue was noticed, but no one raised it. The premise was never tested, the risk was never named, and no decision was forced.

“Everyone assumed” is what gets said afterwards, once an explanation is required.

Assumptions aren’t neutral. They are decisions that were never validated. Treating silence as shared understanding isn’t trust — it’s avoidance.

When those assumptions eventually fail, the blame shifts to delivery or circumstances, not to the decision that was never made.

Conformity

Judgement becomes personally unaffordable.

Governance debt isn’t primarily a process failure. It’s a failure to exercise judgement when it matters.

Organisations that treat disagreement as a behavioural problem select against judgement. Over time, people who raise difficult issues leave or are sidelined while those who maintain harmony advance.

This is often justified in the language of values, safety and inclusion. The result is simple – the people who raise uncomfortable issues don’t last.

As organisations grow, judgement is one of the first things they lose. HR functions compound the problem by enforcing behavioural conformity in the name of safety, values and consistency. Discomfort is treated as harm, disagreement as misconduct and questioning the premise as poor collaboration. People who still exercise judgement are pushed out.

On top of this is a social demand to be polite, inclusive and blind to differences in actual merit.

In these environments, people learn quickly what is safe.

Agreeing is safe. Questioning isn’t.

Over time disagreement disappears, not because problems are solved but because raising them comes at a cost.

Without disagreement, there’s no way to see who actually understands the risks involved. Competence becomes invisible.

When a system can no longer tell the difference between good judgement and bad judgement, it can’t govern risk.

At some point capability becomes irrelevant - judgement disappears because it has a personal cost.

Denial

The system defends the behaviour that is breaking it.

Denial begins when the problem can’t be safely discussed.

Attempts to question judgement are treated as personal rather than substantive. Concerns are reframed as unkind, elitist or inappropriate.

Instead of engaging with the issue, organisations add process, reporting and governance theatre. They substitute appearance for understanding.

The result is a feedback loop:

• Judgement declines.

• Risks aren’t examined or are explained away.

• Governance debt accumulates.

• Failure appears sudden and inexplicable.

• The response further weakens judgement.

Nothing stabilises at this stage. The system continues to degrade because the cause can no longer be named.

What this explains

Governance debt isn’t mysterious. It’s created when organisations:

• Avoid naming decisions.

• Suppress disagreement.

• Fail to recognise risk.

• Care more about how something sounds than whether it’s right.

• Ignore who actually understands the risks.

When governance environments become culture-war terrain, the quality of decision-making collapses. Facts are filtered through allegiance, disagreement becomes betrayal and silence becomes the only neutral position.

When the organisation fails, the decisions that caused the failure were the ones that were never made.

Undoing it requires clarity, conflict and competence.

Most organisations choose not to do this.

What comes next

The next essays move from diagnosis to structure. They examine how governance debt is locked in after decisions are avoided and why it becomes harder to undo over time.

Specifically:

• How unclear ownership allows non-decisions to persist.

• How exceptions become permanent without anyone choosing them.

• How speed and delivery theatre replace judgement.

• Why boards often reinforce these patterns instead of correcting them.

Governance debt is not technical debt

Technology leaders understand technical debt. We cut corners to ship faster, and we accept the future cost.

Treating governance debt as the same sort of problem as technical debt, just in a different department, is a mistake.

Governance debt behaves differently in practice. It accumulates invisibly and by the time it’s obvious it’s too late to address without real pain.

Technical debt lives in systems while governance debt lives in decisions.

Technical debt can be managed

None of this means technical debt is trivial – it just means it is, in principle, survivable.

Technical debt has three characteristics that make it so.

First, technical debt is observable. Engineers can point to it – they can show you the brittle module, the duplicated logic or the missing tests. It has a location.

Second, technical debt is reversible. Given time, money and competence, most technical debt can be paid down by refactoring, rewriting or replacing. The work is hard but the path is clear.

Third, technical debt is owned. Even in dysfunctional organisations technical debt usually has a notional owner – a team, a system or an architect. Someone can be made accountable for reducing it.

Governance debt is hard to see, hard to measure and risky to name

Governance debt accumulates when decisions are deferred, ownership overlaps, or authority is unclear. It shows up as “temporary” arrangements that never expire, exceptions that become norms, and formal governance that no longer reflects how work actually gets authorised.

Unlike technical debt, governance debt is:

• Hard to see.

• Hard to measure.

• Politically dangerous to point out.

There is no Jira ticket for “unclear decision-making authority”, and no dashboard for “who actually owns this risk”. A refactor can’t fix a board that doesn’t understand what it has delegated.

By the time governance debt becomes visible it usually manifests as secondary failures such as delivery stalls, regulatory breaches, missed deals, internal conflict or sudden executive churn. The organisation reacts to the symptom rather than the cause.

Governance debt compounds

Technical debt tends to grow linearly. Governance debt compounds.

Each unresolved decision makes the next decision harder, and each exception creates precedent. Every vague role boundary increases the surface area for conflict. Over time, people stop asking who decides and start optimising for survival – escalation avoidance, consensus theatre or quiet workarounds.

This is where speed theatre emerges as a predictable symptom of unresolved governance debt. The organisation appears busy, productive and decisive, while real decisions are endlessly deferred or quietly buried. Motion replaces judgement.

From the outside this pattern is blamed on poor execution, but in reality people are burned out from making progress without clear decisions.

You can refactor code without threatening anyone’s identity, but you can’t refactor governance without clarifying authority and accountability.

Paying down governance debt requires answering uncomfortable questions:

• Who actually owns this decision?

• Who’s accountable when it goes wrong?

• What authority was implied but never explicitly granted?

• Which “temporary” compromises are now structural?

Weak governance survives on ambiguous authority. These questions remove that ambiguity.

That’s why organisations tolerate governance debt far longer than technical debt. It’s socially cheaper to ship another workaround and high-five in the Sprint Review than to resolve an authority problem at the top.

Decision systems fail before delivery systems do

Strong technology organisations don’t fail because they lack talent or funding. They fail because they can’t make and sustain clear decisions as they scale.

Technical debt slows you down. Governance debt eventually stops you.

If you only invest in architecture, tooling and delivery practices, you’re optimising the wrong layer. The hardest problems are not in the codebase – they’re in the decision system that surrounds it.

And unlike technical debt, governance debt never repays itself because unresolved decisions don’t decay – they compound.

What this explains

Governance debt isn’t created by bad intent or incompetence – it’s created by deferral.

The decision to “deal with it later” feels prudent, collaborative and low-risk in the moment but in reality it’s the moment at which ambiguity gets normalised and authority starts to collapse.

When this happens repeatedly, judgement debt doesn’t just accumulate – it becomes structural.

What comes next

Deferral doesn’t exist on its own. It depends on ambiguity about who owns a decision and who bears its consequences.

The next essay looks at how vague ownership turns temporary indecision into a permanent operating model, and why organisations tolerate it long after it becomes dangerous.

Failure is usually blamed on inputs

When a scale-up fails people reach for the same explanations – the product wasn’t quite right, the team wasn’t strong enough or the company ran out of money.

Such reasons are familiar because they feel actionable, and for people wired for action – who tend to inhabit scale-ups – this is reassuring. You can change a product, replace people, raise another round. Failure can be framed as a problem of execution or timing rather than structure.

These are socially safe explanations. The product issues can be discussed without assigning blame. Any talent gaps can be attributed to hiring mistakes or market conditions and funding shortfalls can be written off as bad luck or macroeconomic shifts.

Also, these explanations are sometimes simply true. Poor products do fail, weak teams do underperform and undercapitalised businesses do run out of runway. There’s no serious argument that these factors don’t matter or that they never cause failure.

But the problem isn’t that these explanations are wrong – it’s that they are often incomplete.

What these narratives share is that they focus attention on inputs rather than on the system that turns those inputs into decisions. They imply that success would have followed if only the ingredients had been better. They ignore the possibility that the chef may be bad.

Some organisations degrade after initial success

There’s a class of failure that these explanations struggle to account for.

It appears not at the idea stage, and not in obviously under-resourced companies, but later – after initial success. The product has customers and revenue and the team is experienced and often impressive on paper. Funding is sufficient and growth has already occurred.

Rather than collapse suddenly, these organisations drift. Progress becomes noisy but limp, decisions take longer and exceptions multiply. Work continues but outcomes become harder to explain.

When pressure arrives such as a market shift, a regulatory issue, a major customer demand or a failed deal, the organisation doesn’t adapt cleanly – it fractures.

This pattern doesn’t describe every failure but it’s a familiar pattern for anyone who has worked inside scale-ups beyond their first growth phase, participated in turnaround efforts or been involved in due diligence, project rescue and post-mortem reviews.

If product quality, talent or capital were the primary limiting factors in these cases, failure would tend to appear earlier and more obviously. Instead, something else is degrading quietly while the organisation appears to function.

Something else is failing first.

Product, talent and funding do not control decisions

Product, talent and funding matter. They are essential for success but they aren’t control systems.

Product determines what a company is trying to build.

Talent determines who is doing the work.

Funding determines how long the company can keep going.

But these don’t determine how decisions are made when trade-offs are real. Nor do they define who has authority when priorities conflict. And they don’t ensure that risk is identified early or acted on decisively.

Those functions belong to governance, or more precisely, to judgement exercised through authority.

When governance is weak, organisations don’t become chaotic – they become polite. Decisions are deferred rather than challenged, performance expectations are softened in the name of psychological safety and escalation becomes socially risky.

Over time, competence is not rewarded for being correct but for being agreeable. Teams optimise for narrative coherence rather than outcomes. Strong engineers and operators learn to work around the system instead of through it. Or they leave.

I’ve seen well-funded teams circle the same issue month after month because no one was prepared to make a binding decision. I’ve seen senior technical judgement overridden by roadmap theatre because escalation paths were unclear or unsafe. I’ve seen additional funding used to hire around indecision rather than confront it.

In these environments, talent and money don’t correct structural weakness. Instead they absorb its consequences, allowing it to persist.

Governance debt is masked by early success

Weak governance rarely causes immediate failure. Instead it allows unresolved decisions to accumulate.

Ownership is left vague because clarifying it would be uncomfortable. Exceptions are granted because speed feels more important than consistency, and decisions are deferred because there is always another milestone to hit first.

As long as revenue grows and funding continues, these issues remain masked. Talented people compensate, money absorbs inefficiency and progress continues – at least superficially.

This is how governance debt is silently financed by ostensible success.

The organisation appears healthy but its decision-making capacity is degrading. And by the time symptoms surface the debt is already mature and ready to be paid back.

Product, talent and funding narratives avoid accountability

The product, talent and funding excuses for failure abound because they sound plausible, are easy to discuss and are difficult to contest. They sit at the right level of abstraction and they allow boards, executives, and investors to diagnose failure without actually questioning accountability or decision-making authority. They preserve existing power structures while still sounding like corrective exhortations.

What’s missing isn’t intelligence or intent but judgement exercised with consequence.

In many environments this absence is reinforced rather than challenged. Confidence is rewarded over clarity, and leadership is performed as a role rather than demonstrated through decisions. In a LinkedIn world, optics travel faster than evidence.

As a result organisations gravitate toward explanations that feel progressive, humane and culturally acceptable even when those explanations leave the underlying failure untouched.

This is not stupidity – it is avoidance.

Judgement fails before performance

The first thing to fail isn’t innovation or morale – it’s clarity of decision-making.

Decisions take longer to reach, escalation paths become ambiguous and work proceeds without clear outcomes because stopping feels harder than carrying on. People stay busy but meetings multiply, and activity increases while judgement declines.

By the time the product is blamed or funding becomes critical, the organisation has already lost its ability to exercise authority coherently under pressure.

What this explains

Product, talent and funding are essential but they aren’t sufficient.

Most scale-ups don’t fail because they lacked the right inputs.

They fail because their organisations could no longer convert those inputs into clear, accountable decisions when it mattered.

Call it governance debt if you like. What actually accumulates is judgement debt.

That is what turns promising companies into expensive disappointments.

What comes next

If judgement debt is the underlying cause then the important question isn’t why things eventually broke but how that debt was created in the first place.

The next essays explore the mechanisms that make this failure mode persistent – deferral, vague ownership, exception culture and the substitution of motion for judgement.

There are no quick fixes – there are only choices – which are usually made earlier than people realise.

Introduction

This is the opening essay of Governance Debt, a publication about why technology scale-ups fail — not through lack of product, talent or funding, but through accumulated governance debt.

It’s written for people who have been held accountable for failures that only made sense in hindsight - and for those who don’t want to wait for failure to understand what went wrong.

Technology businesses accumulate a hidden liability called governance debt. It’s a strong predictor of outcomes that product quality, talent and funding alone can’t explain.

Governance debt isn’t created by incompetence - it’s created by decisions that feel rational at the time.

Deferring governance feels rational but fails at scale

Technology businesses treat governance as something they can ignore until it forces itself into view. They tell themselves it can wait until after product–market fit, growth or the “real work” is done.

Governance gets talked about as a “proper enterprise” worry, a bureaucratic overhead or a sign that a business has lost its edge.

In early-stage and growth-stage businesses structure is framed as the enemy of speed. Discipline becomes the enemy of creativity.

That belief isn’t just wrong - it’s structurally dangerous because it pushes organisations to defer decisions that determine control, risk and accountability.

Every scale-up that fails leaves a trail of decisions that were individually defensible but collectively damaging to the organisation. It begins with informal operating models that were “good enough for now”, delivery shortcuts that saved time without regard to downstream consequences, commercial commitments disconnected from delivery reality and decision ownership left deliberately vague to avoid conflict or awkward conversations about risk.

Such decisions aren’t exceptional mistakes - they’re default behaviour in fast-moving organisations and the seed of what eventually becomes ungovernable complexity.

The most expensive words in a growing technology business aren’t “this is broken” - they are “we’ll deal with it later”. I’ve said them myself more times than I care to admit. They never age well.

What “later” actually means is simple - we are choosing to defer structure and predictability while we keep amassing obligations we don’t know how to honour.

By the time the symptoms show up - missed delivery dates, regulatory friction, client escalations, internal instability - the underlying debt is already baked in.

At that point governance isn’t something you can just add but something you’re forced to repair under pressure, usually after the damage is done.

Physicist Richard Feynman described a class of ideas as not even wrong – ideas so poorly-grounded that they can’t even be meaningfully falsified. The way most technology businesses talk about governance falls into that category. Governance is framed as a future concern, a maturity milestone or a compliance exercise while the decisions that actually create governance debt get treated as normal, pragmatic and unavoidable.

Those decisions aren’t unavoidable – they’re choices made for short-term convenience that become nearly impossible to undo later.

Governance debt shows up late

Governance debt is often missed because its effects rarely appear where or when it’s created.

Decisions that weaken ownership, blur accountability or normalise exceptions rarely cause immediate failure. They feel contained, reversible and low-risk. Their consequences emerge later, under pressure, in parts of the organisation far removed from the original decision.

By the time the symptoms appear - failed audits, stalled deals, delivery breakdowns or forced restructures - the underlying causes are already embedded in the operating model. The organisation experiences the failure, but no longer remembers the choices that made it inevitable.

That time lag is what makes governance debt so dangerous. It allows structurally damaging decisions to pass as sensible judgement calls right up to the point that they can no longer be unwound.

Early governance mistakes are hard to undo

Start-ups tell themselves they’re too early for governance. They treat structure as something that will make sense later once the product works and the business is real.

This is nonsense.

The early years are when governance choices are cheapest to make and easiest to reverse. They’re also when the most irreversible damage gets done.

The most common example is titles. Handing out vanity executive roles in the early days feels harmless - making your first engineer the CTO, calling the person with the idea the CEO, turning loyalty and early effort into permanent authority.

Those decisions hard-code who gets to decide, who can’t be challenged and who becomes difficult to remove later without blowing up the business. I’ve warned founders not to do this and watched them do it anyway. It almost always ends the same way.

Founders rarely admit this but many scale-up failures are not caused by market conditions or product problems - they’re caused by early governance mistakes that made it impossible to change management, shift control or remove the wrong people when the organisation outgrew them.

So start-ups don’t get a free pass on governance. They just get a longer fuse.

Looking fast matters more than being sound

Technology businesses claim they value speed. What they actually value is the appearance of speed.

They measure output, motion and activity because those metrics are easy to count. They track tickets closed, features shipped, sprints completed and roadmap milestones hit. They don’t track coherence, decision quality or whether the organisation is becoming easier or harder to run over time.

This distorts reality. Teams learn that looking fast matters more than being sound. Shipping something that makes the roadmap look healthy gets rewarded even if it adds risk, complexity or rework. Slowing down to clarify ownership, resolve a structural dependency or say no to a bad idea is framed as obstruction.

Agile culture amplifies this problem rather than fixing it. In theory it’s meant to support disciplined learning and controlled delivery but in practice it’s an excuse to defer real decisions indefinitely. Short planning horizons replace real prioritisation and backlogs become dumping grounds for unresolved trade-offs. Velocity metrics reward motion instead of judgement. Iteration becomes a way of avoiding the hard work of making a clear decision and living with its consequences.

This isn’t just a process failure – it’s a failure at the top of the organisation.

When things are uncertain, people in charge feel pressure to keep things moving because motion looks like control. When the right answer is unclear, shipping something – anything! – creates the illusion of progress. Delaying a decision in order to understand the real risk feels like weakness in a culture that confuses decisiveness with competence.

The result is speed theatre. Work gets broken into smaller pieces, roadmaps get constantly reshuffled and delivery plans get rebranded every few months but the underlying problems don’t get solved. The organisation stays busy while its structural debt quietly grows.

That behaviour compounds governance debt. Complexity increases every time a business substitutes motion for judgement. Every time a structural problem is deferred instead of resolved the eventual fix becomes more expensive, political and harder to implement without causing collateral damage.

Speed without coherence isn’t a competitive advantage - it’s a liability that eventually has to be paid for.

The businesses that scale well aren’t the ones that move the fastest in their early years. They’re the ones that are willing to slow down at the right moments to make decisions that will still make sense when the organisation is ten times bigger than it is today.

Boards and regulators spot failure before founders do

Boards and regulators tend to notice governance failure before founders do - not because they’re smarter, but because their roles force them into parts of the business founders never have to inhabit.

This is why experienced buyers and investors ask questions that founders find irritating.

Founders see problems as delivery friction, people issues and market pressure because that’s what they experience day to day. Boards and regulators see the same problems as unclear ownership, unmanaged risk and commitments the organisation can’t reliably honour. They care less about output and more about whether accountability, control and decision-making still hold together.

From a board’s point of view, governance debt shows up as personal and financial exposure. When ownership is unclear nobody can certify that risks are being properly managed. When decisions aren’t recorded nobody can describe why a bad call was made. When delivery depends on heroes nobody can credibly sign off on forward plans. What looks like operational mess inside the business looks like board failure from the outside.

This is where the quality of governance membership starts to matter and where a lot of businesses fail themselves. Many boards are stacked with people who look good on paper but don’t do the actual work of governance. Some are reputation hires who were brought in for credibility rather than competence. Some are founders’ friends who are there for loyalty rather than independence. Some are executives from large organisations who have never actually operated in a fragile, under-resourced environment. Some are what I think of as governance zombies - they turn up to meetings, nod at the right moments, ask safe questions and then disappear again without ever forcing a hard conversation. If you replaced them with a particularly polite houseplant, the board minutes would look much the same.

Such boards do not uncover governance debt early - they normalise it.

Instead of challenging unclear ownership, undocumented risk and incoherent commitments they accept management narratives at face value. Instead of demanding evidence that the organisation can actually honour its promises they focus on whether the slide deck looks reassuring. Instead of intervening when heroics become normal they praise the team for “pulling it off again”.

That’s not oversight. It’s governance theatre that does nothing to change the underlying risk.

When the board itself is performing governance rather than doing it, regulators end up being the first serious adults in the room. That’s a bad time to find out who has actually been paying attention.

This is why governance problems eventually become board problems. They translate directly into valuation risk, deal risk and liability risk. Buyers discount businesses that can’t explain how they actually operate. Investors lose patience with management teams who can’t demonstrate control over their own commitments. Directors start worrying about their own legal exposure long before founders accept that something is structurally wrong.

Meanwhile regulators see the same pattern through a different lens.

They don’t care about velocity, culture or narrative. They care about whether obligations are being met, risks are being managed and the organisation can prove it knows what it’s doing. When governance debt is high, compliance failures aren’t accidents - they’re design outcomes.

What makes regulatory failure so brutal is that it arrives late and lands hard. For years everything looks fine. Then a single incident forces a deep inspection, at which point regulators don’t find one problem - they find a whole system that can’t explain itself. Controls are missing, responsibilities are unclear, exceptions have become normal and decisions can’t be reconstructed. Nobody can credibly say who signed off on what.

By the time this happens it’s already too late to fix.

This is why founders are always shocked by regulatory blow-ups. They think the failure came from outside but in reality it was baked into the business years earlier when governance was treated as something that could be deferred.

Boards and regulators are not pessimists - they’re lagging indicators.

They see governance debt first because they’re the first people who are forced to care about whether the organisation is legally defensible, audit-ready and survivable under scrutiny. Founders usually only see it later when it has already become an existential problem.

The final trap is that businesses respond to governance failure by “performing compliance” instead of changing behaviour. They add policies, dashboards and process while leaving decision-making untouched. That doesn’t reduce governance debt - it just conceals it.

Real governance isn’t a maturity phase - it’s a choice.

Deferring it isn’t pragmatism - it’s a decision to run the business without knowing if it’s defensible.

Some businesses make that decision consciously but most drift into it.

Either way the bill still arrives - and when it does there are no cheap fixes left.

There is no fix - but there is a choice

There’s no single intervention that pays down governance debt once it has accumulated.

There’s no framework you can adopt, no tool you can buy and no policy pack you can roll out that will undo years of deferred decisions.

What does exist is a choice about how the organisation is run from this point forward.

Taking governance seriously doesn’t mean slowing everything down.

It means being explicit about who decides, what risks are being accepted and what obligations the organisation is taking on - even when doing so is uncomfortable, politically awkward or commercially inconvenient.

It means accepting that some decisions will take longer because real trade-offs have to be dealt with rather than deferred. It means tolerating visible disagreement instead of manufacturing false alignment. It means writing things down not for compliance theatre but so responsibility can be traced when the pressure arrives.

Most importantly it means treating governance as an operating discipline rather than a maturity milestone.

Organisations that manage governance debt well are not more bureaucratic. They are more understandable - to themselves, to their boards and to the people who will eventually be forced to rely on their decisions holding up under scrutiny.

That understandability has a cost - it shows up as friction, slower commitments and fewer heroic recoveries.

But it is vastly cheaper than discovering too late that the business can’t explain itself when it needs to most.

Governance debt isn’t inevitable, but avoiding it requires choosing coherence over comfort, judgement over motion and accountability over narrative - consistently, and long before failure makes the choice for you.