Most failed transformation projects were not badly built. They were badly aimed. The team executed well — on the wrong problem, or on a symptom instead of the cause. By the time that becomes clear, the budget is spent and the appetite for change is gone.
Solutions are seductive; problems are the work
It is far more satisfying to talk about the system you are going to build than to sit with the messy reality of how work actually happens today. That is exactly why so many projects skip the diagnosis — and exactly why so many miss.
A diagnosis is not a delay before the real work. It is the part of the work that determines whether the rest is worth doing.
What a real diagnosis produces
- A map of how work actually flows — not how the org chart says it does
- The specific points where time, money and clarity leak
- A ranked view of which system would create the most leverage
- A shared understanding across leadership before anything is built
Build second — and build the right thing
When you diagnose first, the build becomes almost anticlimactic in the best way: you already know what to build, why, and in what order. The discipline up front is what makes the change downstream actually last.