Case Studies

What does structural diagnosis look like in practice?

A difficult organisational situation rarely arrives with a clean label.

It may arrive as an unexplained discrepancy, a reporting problem, a governance concern, an uncomfortable decision, or simply the growing sense that something no longer makes sense.

The challenge is not only to identify what went wrong.

It is to understand what was happening around the problem while meaningful choices still existed.

These case studies show the framework applied to situations where authority, information, incentives, reporting, pressure and decision-making interacted in different ways.

They are not presented simply as stories of failure.

They show what becomes visible when the structure around a situation is examined rather than the situation being reduced to the actions of individual people.


What the analysis produces

Each case study uses the same underlying diagnostic approach.

The analysis examines:

  • who has authority;
  • who carries the consequences;
  • what information is available and who can independently verify it;
  • where pressure is accumulating;
  • where reporting may have separated from operational reality;
  • what incentives affect acknowledgement;
  • where explanations are replacing clarification;
  • what events could narrow the remaining options;
  • and what the decision environment permits people to know and do.

The resulting report is not a retrospective explanation of why everyone should have known better.

It is a structured answer to a more useful question:

Given what was knowable at the time, what was happening to the decision environment?

That is also what a Centreline Clarity engagement is designed to produce.


Five Situations. Five Different Expressions of the Problem.

Barings

When authority outruns verification

Nick Leeson became one of Barings’ most successful traders while simultaneously controlling functions that should have provided independent verification of his reported results.

The issue was not simply whether one individual was trustworthy.

It was whether the organisation had retained the ability to know independently what was actually happening.

Primary condition: Authority Without Verification
Also illustrates: Pressure Without Visibility · Reporting Without Operational Contact

Diagnostic mechanism: Power Asymmetry

→ Read the Barings Case Study


City Harvest

When acknowledgement becomes costly

The City Harvest case provides a different kind of structural problem.

The question is not simply whether concerns existed. It is what happens when the social, institutional, or relational cost of challenging an established authority changes what people are willing to question openly.

A governance structure can remain formally intact while its practical capacity to challenge becomes increasingly constrained.

Primary condition: Incentives That Distort Acknowledgement
Also illustrates: Authority Without Verification · Language That Reassures Without Clarifying

Diagnostic mechanism: Authority Sacralization

→ Read the City Harvest Case Study


WeWork

When seeing the problem does not produce action

WeWork demonstrates why information alone is not enough.

Signals, concerns and contradictory information can exist within an organisation without producing effective intervention when the incentives surrounding acknowledgement favour continuation.

The question becomes:

What happens between seeing something and being able to act on it?

Primary condition: Incentives That Distort Acknowledgement
Also illustrates: Pressure Without Visibility · Language That Reassures Without Clarifying

Diagnostic mechanism: Incentive Capture at Scale

→ Read the WeWork Case Study


Wirecard

When evidence fails to converge

Wirecard demonstrates a different failure of institutional visibility.

Important signals existed across different people, institutions and information channels. Yet the existence of evidence did not automatically produce effective scrutiny.

The diagnostic question is therefore not merely:

Was there evidence?

but:

What happened between evidence existing and the organisation acting on what it meant?

Primary condition: Language That Reassures Without Clarifying
Also illustrates: Authority Without Verification · Incentives That Distort Acknowledgement

Diagnostic mechanism: Regulatory Inversion

→ Read the Wirecard Case Study


Before You Sign

When formal reporting says “on track” and operational reality says otherwise

The first four cases examine situations whose consequences are now known.

Before You Sign is deliberately different.

It examines a decision environment before the outcome is known.

Formal reporting indicates that an implementation remains on track. Operational signals suggest that the underlying conditions may not support that conclusion.

Nothing has necessarily failed.

But the organisation is approaching decisions that could make changing course substantially more difficult.

The question is not:

Who is right?

It is:

What is actually known, what remains uncertain, and how much room remains to find out before the next commitment?

Primary condition: Reporting Without Operational Contact
Also illustrates: Pressure Without Visibility · Responsibility Without Control

Diagnostic mechanism: Implementation Displacement

→ Read Before You Sign


Four Failures. One Decision Before the Outcome.

The first four cases are retrospective.

Their outcomes are known.

That makes hindsight tempting.

The fifth case deliberately removes that advantage.

It asks what the framework can establish while the situation is still unfolding and the outcome is not yet known.

That distinction is important.

Centreline Clarity is not intended merely to explain disasters after they happen.

The purpose of the framework is to make the decision environment more visible while meaningful options may still remain.

That is the territory of Late but Not Too Late.

Explore Late but Not Too Late


What Would You Receive?

The case studies are deliberately presented in the same form as the underlying diagnostic work.

They are not demonstrations of clever terminology.

They are examples of what happens when a situation is broken down into:

identity → situation → constraints → pressure → irreversibility → failure mode → risks → actions → reactions → monitoring → non-actions

The purpose is to answer a practical question before anyone engages us:

What would I actually get if I brought Centreline Clarity a difficult situation?

The answer is not a verdict.

It is a structured view of the situation that allows the person responsible for the decision to see what may otherwise remain distributed across reports, people, assumptions, incentives and competing explanations.


Have a Situation of Your Own?

You do not need to know what the problem is called.

You do not need to have established that something has gone wrong.

You only need to have reached the point where something about the situation no longer makes sufficient sense to leave unexamined.

→ Submit a Snapshot