Thinking on Program Recovery
Writing on structural failure, execution discipline, and what actually happens when programs stop delivering. No frameworks. No methodology decks.
The Executive Dashboard Is Not a Record
Five workstreams roll into the one number an executive has time for. That assembly step, not any single report, is where the program actually gets misrepresented.
Evaluation Is the Product
Ninety four percent accurate is not an evaluation. What a regulated environment actually requires, and why a reviewer with no criteria is worse than no reviewer at all.
Your AI Pilot Was Never Going to Production
The demo worked. Everyone was impressed. Eighteen months later, nothing is in production. The model was never the problem.
What the Status Report Is Actually Saying
Everyone reads the status report. Almost nobody reads it correctly. The real information is not in the RAG rating. It is in the language that changed since last week.
Scope Is Not the Problem
Scope creep is the most blamed cause of program failure. It is almost never the real one. The problem was already there before the first requirement changed.
The Program Is Not Late. It Is Dead.
A delayed program has an execution problem. A dead program has lost the conditions that would make recovery possible. The difference matters more than anyone wants to admit.
Why Program Recovery Fails in the First 30 Days
Most programs that fail do not fail because of bad execution. They fail because nobody is willing to say out loud what everyone already knows.
The Difference Between a PM and a Program Recovery Lead
When a program is in trouble, the first instinct is usually to find a better project manager. That instinct is wrong.
Five Signs Your Program Has a Structural Problem, Not an Execution Problem
Programs fail in two ways. Execution failure is visible. Structural failure hides behind execution symptoms until it is too late.
