Almost every disappointing strategy engagement shares a single origin. The team did not solve the wrong problem badly; it solved the wrong problem well. The analysis was rigorous, the slides were clean, the logic held together, and none of it mattered because the question underneath had never been properly examined. In medicine, no responsible practitioner writes a prescription before reaching a diagnosis. In strategy, the equivalent discipline is rarer than it should be, and its absence is expensive.
The temptation to skip ahead
Diagnosis is unglamorous. Clients rarely open a conversation by asking for one. They arrive with a solution already half-formed—”we need to enter the enterprise segment,” “we should acquire a competitor,” “our pricing is too low”—and they want validation and a plan. The pull toward prescription is strong on both sides of the table. The adviser wants to demonstrate value quickly; the executive wants momentum. Skipping the diagnostic phase feels like efficiency. It is usually the opposite.
Consider a mid-sized software company convinced its problem was sales. Revenue growth had stalled, and leadership’s instinct was to hire more account executives and rebuild the compensation plan. A team that took the brief at face value would have delivered a sales-effectiveness project. A proper diagnosis, however, revealed that the sales team was closing at a healthy rate—the real issue was that renewals were quietly collapsing because the product had fallen behind on reliability. Adding salespeople would have poured water into a leaking bucket, and the leaking bucket was an engineering and product problem, not a sales one.
What a real diagnosis contains
A diagnosis is not a restatement of the client’s concern in more elaborate language. It is a defensible account of what is actually happening and why. A useful diagnosis tends to include several distinct elements:
- A clear description of the observed problem in measurable terms, not adjectives.
- A separation of symptoms from underlying causes, with evidence linking the two.
- An identification of which causes are structural and which are incidental.
- An honest statement of what is not the problem, ruling out the tempting scapegoats.
- A sense of the forces that will resist change, because those forces are part of the condition.
The last point is often neglected. A diagnosis that ignores the organization’s incentives, history, and politics describes a patient in a vacuum. Real conditions exist inside real bodies, and the body pushes back.
Symptoms are seductive because they are visible
The reason teams anchor on symptoms is that symptoms announce themselves. Falling margins, rising churn, a missed quarter—these arrive with numbers attached and demand immediate attention. Causes are quieter. A retailer watching foot traffic decline may treat the decline as the problem and respond with promotions, when the cause is a slow erosion of assortment relevance that promotions cannot fix and may even accelerate by training customers to wait for discounts.
The discipline here is to keep asking why one layer deeper than feels comfortable. Margins are down—why? Because discounting rose. Why did discounting rise? Because inventory aged. Why did inventory age? Because buying decisions were made nine months earlier against a demand forecast that no longer held. The actionable problem lives at the bottom of that chain, not at the top where the pain is loudest. Prescribing a fix for the visible symptom leaves the mechanism intact, and the symptom returns.
Distinguishing the condition from the story about it
Every organization tells itself a story about why things are the way they are. That story is data, but it is not the same as the truth. Part of diagnosis is listening carefully to the internal narrative and then testing it rather than adopting it. If everyone agrees that a competitor is winning on price, that consensus is worth examining precisely because it is unanimous. Frequently the competitor is winning on convenience, or on a narrower and better-served customer segment, and “price” is simply the explanation that requires no one inside the company to change their own behavior.
A practical technique is to ask several people, separately, to explain the same problem. When the accounts diverge sharply, the divergence itself is diagnostic—it reveals that the organization does not share a common understanding of its own situation, which is often a deeper issue than the presenting complaint. Alignment cannot be built on a problem no one defines the same way twice.
Knowing when the diagnosis is finished
Diagnosis cannot continue forever; at some point analysis becomes avoidance. A workable test is whether you can state the problem in a single sentence that a skeptical executive would recognize as true and would not have written themselves before the engagement began. If the sentence is obvious, you have not diagnosed anything. If it is surprising but, once explained, hard to argue with, the diagnosis is doing its job.
Another signal is convergence: multiple independent lines of evidence pointing to the same underlying cause. When the financial analysis, the customer interviews, and the operational data all implicate the same structural issue, confidence is warranted. When they point in different directions, the work is not done, and any recommendation built on that shaky foundation inherits the uncertainty.
The cost of a confident wrong answer
Prescribing before diagnosing is not merely inefficient; it is actively harmful, because a well-executed solution to the wrong problem consumes the credibility and resources needed to address the right one. An organization that spends a year and a large budget reorganizing its sales force, only to find growth still stalled, becomes harder to move the second time. Change fatigue is real, and it is spent on the first, wrong initiative. The right initiative then has to overcome not only its own difficulty but the exhaustion left by its predecessor.
The discipline of diagnosis is ultimately a form of respect—for the client’s resources, for the difficulty of the problem, and for the truth that important questions rarely reveal themselves at first glance. The advisers and leaders who insist on it are not slower. They simply refuse to be fast in the wrong direction, and over any meaningful horizon that refusal is what separates advice that works from advice that merely sounds right.