Before the Pattern Is Named
Organisations rarely fail because nobody saw a problem.
More often, they fail because pressure gradually changed what the system around the problem could acknowledge, verify, or act upon.
The people closest to the situation may have noticed something was wrong long before the organisation could say, with confidence, what was happening.
- A dashboard may still look healthy.
- A report may still be technically correct.
- The person responsible may still be trusted.
- The board may still be meeting.
- People may even be raising concerns.
And yet something has changed.
Information no longer travels as it once did. Authority and accountability begin to separate. Explanations become more reassuring than clarifying. The cost of acknowledging a problem rises. Decisions continue to accumulate while the ability to change them begins to narrow.
At this point, the problem often does not have a name.
That matters.
If you know what a problem is called, you can search for it. You can find a framework, a checklist, a professional specialty, or a recognised intervention.
But many consequential organisational situations are encountered before the pattern is named.
Someone simply knows that something is not making sense.
The purpose of this framework is to examine that space.
It does not begin by asking:
What kind of failure is this?
It begins by asking:
What is happening to the decision environment around it?
What the Framework Looks For
The framework looks for six structural conditions that can cause pressure to accumulate faster than visibility increases.
They do not need to appear dramatically. In many situations, they develop quietly and reinforce one another.
1. Authority Without Verification
When the people making decisions control (or depend upon) the information used to judge those decisions, the organization can appear informed while becoming progressively less able to know whether its understanding is reliable.
The question is not simply whether someone can be trusted.
It is:
What allows the organisation to independently establish whether the information carrying that authority is reliable?
→ Explore Authority Without Verification
2. Responsibility Without Control
When someone is held responsible for an outcome without possessing the authority, information, resources, or decision rights needed to materially alter what produces it, accountability can become detached from control.
The formal structure says:
You own this.
The operational structure says:
You cannot actually change this.
The question is:
Who can actually change what is producing the outcome AND do they have enough authority to do so?
→ Explore Responsibility Without Control
3. Pressure Without Visibility
When the demand to decide or act increases faster than the organisation’s ability to understand the situation, urgency can begin consuming the very visibility needed for a sound decision.
Pressure is not itself the problem.
The question is:
Are we being forced to act faster than we can reliably understand what we are acting on?
→ Explore Pressure Without Visibility
4. Reporting Without Operational Contact
When formal reporting becomes increasingly detached from the conditions it is supposed to represent, the organization can remain well informed about its reports while becoming poorly informed about reality.
A report does not need to be false to become misleading.
The question is:
What does this report tell us about reality… and what would we see if the report were wrong?
→ Explore Reporting Without Operational Contact
5. Incentives That Distort Acknowledgement
When recognising a problem becomes individually, socially, or professionally costly, people can rationally choose not to make what they see institutionally visible.
Someone can simultaneously believe:
This matters.
and:
I should be careful about saying this.
The question is:
What does it cost someone to be the first person to say that something is wrong?
→ Explore Incentives That Distort Acknowledgement
6. Language That Reassures Without Clarifying
When language reduces the perceived uncertainty, conflict, or urgency surrounding a situation without materially increasing understanding of what is actually happening, an organization can experience a sense of resolution without resolving the underlying uncertainty.
The question is:
What became more certain… and what merely became more reassuring?
→ Explore Language That Reassures Without Clarifying
The Conditions Interact
These are NOT six independent failure categories. They are conditions that can coexist and reinforce one another.
A reporting system can lose contact with operational reality.
That can increase dependence on the people controlling the information.
Pressure can then increase faster than visibility.
People who recognise the discrepancy may hesitate to acknowledge it because doing so carries a personal or institutional cost.
Language can then absorb the remaining uncertainty into increasingly reassuring explanations.
Nothing necessarily looks catastrophic at any individual point.
But the decision environment has changed.
The organization may still be functioning normally while becoming progressively less capable of seeing, questioning, verifying, or changing what matters.
This is why the framework looks at relationships between conditions, rather than treating any single one as proof of failure.
How the Pattern Becomes Difficult to See
A situation can therefore become progressively harder to see clearly even while the systems around it continue to produce information, approvals, explanations, and decisions.
Three related patterns matter here.
Before the Pattern Is Named
A situation can deteriorate for some time before anyone can describe the pattern clearly.
Individual observations may be real. Concerns may have been raised. Contradictions may be visible.
But what people know has not yet become sufficiently shareable, defensible, or actionable to change how the situation is understood.
This creates a gap between noticing something and being able to name it in a way that changes what the system can acknowledge or act upon.
The absence of a recognised problem does not necessarily mean the absence of a problem.
It may mean that the evidence has not yet become socially sufficient to support a different interpretation.
→ Explore Before the Pattern Is Named
Assurance Laundering
A related problem occurs when legitimate forms of assurance begin to function as evidence for a larger conclusion that they were never designed to establish.
- An approval can be genuine.
- A review can be genuine.
- A control can be functioning.
- A report can be accurate.
Yet those things may collectively create confidence about a question that nobody actually established they were answering.
The result is not necessarily false assurance.
It is the transfer of confidence from a narrower question that was answered to a larger question that remains unresolved.
This is what we mean by Assurance Laundering.
→ Explore Assurance Laundering
Late but Not Too Late
The significance of these patterns is not simply that something may eventually go wrong.
Timing matters.
There is a period in which changing course has become costly, but meaningful options still remain.
That is Late but Not Too Late.
Late means that reversing course (or even pausing to take a better look) has begun to carry consequences.
Not too late means that significant irreversibility has not yet been established.
The question is therefore not only whether a problem exists.
It is whether the structure of the situation is already making recognition, verification, or correction materially harder than it was before.
→ Explore Late but Not Too Late
What the Framework Produces
The output is not a score or a prediction.
It is a structured map of the decision environment as it currently stands.
It examines:
- where pressure is accumulating;
- where authority and accountability have separated;
- where information can or cannot be independently verified;
- where formal reporting has lost contact with operational reality;
- where incentives are affecting what can safely be acknowledged;
- where language may be reducing discomfort without reducing uncertainty;
- where options that appear open are quietly narrowing;
- and where the situation may be more time-sensitive than it currently appears.
The purpose is not to tell people what to decide.
It is to make the structure around the decision visible.
That distinction matters.
A diagnosis can establish that something is structurally wrong without pretending to know, in advance, which decision an organisation should make.
What the Framework Is Not
The framework is not a risk score, prediction model, compliance assessment, investigation, or substitute for legal, financial, regulatory, technical, or other specialist advice.
Nor does it assume that every unusual signal indicates wrongdoing.
A person can be trustworthy.
A report can be accurate.
A concern can be mistaken.
A project can genuinely be on track.
The question is whether the structure surrounding the decision gives the organization sufficient ability to establish what is true, what remains uncertain, what is changing, and what options remain available.
The framework examines the decision environment rather than assigning motives.
See the Framework in Practice
The framework was developed through observation, but it is best understood through application.
These five case studies show different ways that pressure, authority, information, incentives, and time can become misaligned.
Four examine situations whose consequences eventually became visible.
One examines a decision environment before the outcome is known.
Together, they demonstrate what becomes visible when the structure around a problem is examined rather than the problem alone.
Barings
When authority outruns verification.
A situation in which the people carrying the consequences could not independently establish what was happening inside one of the bank’s most profitable operations.
City Harvest
When questioning becomes costly.
A situation in which formal governance remained present while the social and institutional cost of challenging an established authority increasingly constrained what could be acknowledged.
→ Read the City Harvest Case Study
WeWork
When everyone can see, but nobody can act.
A situation in which important information was available, concerns were raised, and yet individually rational incentives continued to support the prevailing trajectory.
Wirecard
When evidence cannot converge.
A situation in which evidence existed across multiple channels, but those signals failed to become effective institutional scrutiny.
→ Read the Wirecard Case Study
Before You Sign
When the reports say “on track” and operations say otherwise.
A live-style implementation scenario in which formal project reporting and operational reality begin to diverge while meaningful choices still remain.
Recognise Something, But Don’t Yet Know What It Is?
You do not need to know what the problem is called before asking us to look at it.
If something in your organization does not make sense… if the reports, incentives, authority, operational reality, or available choices no longer seem to line up, a Snapshot is a starting point for examining the situation structurally.
No confidential details are required.
Centreline Clarity 