How to Diagnose a Business Before Trying to Fix It

There’s a strong pull toward action: something looks broken, so fix it. The problem is that what looks broken is usually a symptom, and fixing a symptom without understanding its cause tends to just relocate the problem.

A real diagnosis starts by mapping how work actually moves through the business — not the org chart version, the real one. Then it separates what’s visibly failing from what’s actually causing the failure. Often these turn out to be different things entirely: the reporting delay isn’t a tooling problem, it’s a hand-off problem three steps upstream.

Only once the actual constraint is named does it make sense to talk about solutions — technology, process, or people. Diagnosis first, intervention second. Reversing that order is the single most common reason transformation projects don’t stick.