The fires are visible. The system producing them is not.
Margin goes the wrong way, and the obvious cuts do not move it. A delivery date slips no matter how many people get added. The transformation is three quarters in, the spend is real, and the status reports have stopped being something you trust. A platform gets funded, launched, and still does not return what it promised. Customer commitments get harder to keep, and leadership spends more time explaining the variance than removing it.
And somewhere in the building, a major commitment is about to be signed that no one is privately sure the organization can absorb.
That is the signature of a constraint that does not live where the pain shows up. Every fix lands on the symptom, and the symptom comes back.
Execution Recoveries
What the numbers actually looked like.
Each one started as a different problem. Each one was breaking somewhere other than where it showed.
HOW THE WORK STARTS
One problem. What it’s costing. A narrow window to move it.
Engagements do not start as transformation programs. They start with one important problem already costing the business something material — margin, time, customer confidence, delivery control, market window, or leadership attention.
The first move is to make the bleed visible, isolate the constraint driving it, and define a correction tight enough to know whether it is holding. The work is judged by whether the measure moves — not by the deck, not by the hours, and not by the explanation. No framework rollout. No discovery phase that bills like a deliverable. If the measure does not move, you will know quickly — and so will I.
CURRENT TERRAIN
AI is where the missing page shows up now.
Somewhere in your company, an AI business case is being built. The demo will work. The numbers will reach for speed, margin, productivity, and leverage. Some of that leverage will be real.
The question is whether the business can carry it.
That is where I start. Not with the model, the roadmap, or the vendor promise — with the operating page missing from the business case. Who works differently when this goes live? Which decisions move closer to the signal? What work stops so the new way has room? Where does output become value instead of noise? Who owns the handoffs when the tool creates more than the organization can govern?
That page has gone missing in every wave I have worked through. ERP did not write it. Cloud did not write it. Digital transformation did not write it. AI will not either — because the case is written to get approved, and naming who has to change is how cases stop getting approved.
Writing that page is the work.
The Field Notes below are where I show it.
FIELD NOTES
Operating reads on why critical investments fail to convert — drawn from thirty years inside stalled programs, live rebuilds, and the systems beneath the visible problems.