Seeing Failure Clearly
Medicine figured this out a long time ago.
You don’t wait until a patient collapses to run diagnostics. You build systems — regular check-ups, blood panels, imaging — specifically designed to catch what isn’t visible yet. The whole premise is that by the time something feels wrong, the damage is already done. Early detection isn’t caution. It’s the discipline that makes intervention possible.
Business hasn’t learned this lesson. Not really.
Most organisations run diagnostics after the collapse. After the project is six months over schedule. After the vendor relationship has broken down. After the steering committee has lost confidence and the board is asking uncomfortable questions. At that point, the diagnostic isn’t insight — it’s a post-mortem. The question shifts from how do we correct this to how did we get here.
The gap between those two questions is expensive.
I’ve watched this pattern across twenty years of enterprise programs. The failure almost never arrives as a sudden event. It accumulates quietly — through assumptions that go unchallenged, through complexity that gets normalised, through problems that get managed around rather than through. The status reports stay green. The steering committee nods. The executive sponsor gets reassurance when they should be getting diagnosis.
What makes this hard is that comfort is indistinguishable from safety — until it isn’t.
When everything looks fine, the instinct is to leave it alone. But fine-looking and fine are not the same thing. A program that is drifting toward failure looks almost identical, month to month, to a program that is on track. The surface signals are nearly the same. The difference is underneath — in the assumptions that haven’t been stress-tested, in the dependencies that are quietly fraying, in the decisions that were deferred and then forgotten.
Here is what I’ve found useful: treating success and failure not as binary states but as a spectrum you are always somewhere on.
This reframe changes the question. Instead of are we succeeding? — which almost always produces a yes, because the bar gets adjusted to whatever is currently happening — the question becomes to what degree are we succeeding, and what is pulling us in the other direction?
That second question is harder to answer. It requires looking at things that are easier not to look at. But it’s the only question that produces actionable information.
The questions worth asking regularly — not when things feel wrong, but before that:
Where are we actually failing, even slightly? Not catastrophically. Not visibly. Just — where is performance below what we expected or committed to?
Where is complexity accumulating? Programs don’t fail at a single point. They fail because complexity accumulated across multiple points simultaneously, and no one had visibility across all of them.
What is not moving as planned, and why? Not the official reason. The actual reason. The distinction matters.
What are we managing ad hoc? Every workaround is a symptom. When workarounds become routine, the symptom has become infrastructure.
What are we assuming will resolve itself? These are the most dangerous items on any program. Things that require active intervention but have been silently reclassified as things that will eventually sort themselves out.
What are we not looking at? Every organisation has blindspots — areas where the discomfort of looking is high enough that collective attention drifts away. Name them.
Where do we need an outside perspective? Not because internal teams lack capability. Because first-time exposure to a situation produces a quality of attention that familiarity eliminates. Fresh eyes see what proximity hides.
The last note from my own thinking on this: it is often better to panic comfortably than to be comfortable instead of panicking.
That sounds paradoxical but it isn’t. The goal isn’t anxiety — constant alarm is as useless as constant calm. The goal is to be at ease with looking at hard things. To be the kind of leader who can sit in a room with a difficult diagnostic and not need it to say something reassuring. To hold the discomfort of an honest picture without flinching, and then act from it.
That capacity — to see clearly without needing what you see to be comfortable — is rarer than most leadership frameworks acknowledge. And it is the thing that separates programs that correct early from programs that collapse late.
Medicine calls it early intervention. I’d call it the discipline of not looking away.
