The Diagnosis Problem: Why Enterprises Keep Fixing the Wrong Thing
Organisations are extremely good at solving the problem in front of them. The trouble is that the problem in front of them is usually a symptom.
The problem you fix is rarely the problem you have
Enterprise organisations are extremely good at solving the problem in front of them. Pipeline is down, so the sales team is retrained. Delivery slipped, so a new tracking tool is bought. Attrition rose, so compensation is reviewed. Each response is reasonable, each consumes real budget, and none of them work for long — because the symptom was treated and the cause was never named.
Root cause analysis is the discipline of refusing to act until the real mechanism is understood. In advisory work it is the single highest-return activity available, because it is the difference between spending a year fixing the wrong thing and spending a quarter fixing the right one.
Why organisations skip the diagnosis
The reasons are rarely about capability. They are structural.
Speed is rewarded more than accuracy. A leader who announces a fix in week one looks decisive. A leader who spends three weeks understanding the problem looks slow — right up until the first leader's fix fails.
The symptom has an owner; the cause usually doesn't. Declining win rates land on the CRO's desk, but the cause may sit in product positioning, pricing governance, or delivery credibility. Causes that cross functional lines have no natural owner, so they go unexamined.
Existing narratives are comfortable. Every organisation carries received explanations — "our market is more price-sensitive", "the region is difficult", "the team needs more training". These narratives survive because nobody tests them, and they quietly steer investment for years.
What rigorous diagnosis actually involves
Evidence before opinion. Real diagnosis starts with primary evidence: deal-level data, transcripts of lost opportunities, delivery timelines, customer interviews, frontline conversations. Not the summary deck — the underlying record. Aggregated reporting hides exactly the variance that explains the problem.
Causal chains, not cause lists. A list of contributing factors is not a diagnosis. A diagnosis states a mechanism: this happens, which produces that, which is why the outcome you see occurs. If the chain can't be written as a sentence, the work isn't finished.
Disconfirmation as a habit. For every hypothesis, the question is what evidence would prove it wrong — and then going to look for that evidence. Analysis that only accumulates support for the first idea is advocacy wearing the costume of research.
Segment before you conclude. Averages are where causes go to hide. A flat overall win rate often conceals one segment collapsing and another growing. Cut the data by segment, geography, deal size, and team before drawing any conclusion.
Talk to the people closest to the work. The frontline almost always knows what is wrong. What they lack is a forum where saying it is safe and consequential. Creating that forum is often the fastest diagnostic instrument an organisation has.
Bringing in expertise that doesn't exist internally
Some causes cannot be diagnosed from inside. Regulatory shifts, technical architecture, category dynamics in an unfamiliar market — these need someone who has seen the pattern before.
The ability to convene the right subject matter expert, from anywhere in the world, within days rather than months is a genuine strategic advantage. It compresses the diagnostic phase and, more importantly, breaks the internal consensus that keeps a wrong explanation alive. An outside expert with no stake in the existing narrative will say the thing everyone suspects but nobody has voice to say.
A test for whether you have a diagnosis
Ask three questions before approving any remedy:
- Can we describe the cause as a mechanism, in one sentence, without using the word "lack"?
- What evidence would have shown us this explanation is wrong, and did we look for it?
- If this cause is real, what else should also be true — and is it?
If the answers are thin, what you have is a plausible story, not a diagnosis. Investing behind a story is how organisations spend a year and a budget arriving back where they started.
The takeaway
Deep research is not a delay to action; it is what makes action worth taking. The organisations that compound advantage are the ones willing to spend disproportionate effort understanding the problem — because every downstream decision, investment, and hire inherits the quality of that understanding.
If a persistent problem in your business has survived more than one attempted fix, a 20-minute diagnostic can identify what the previous attempts missed. Book a free consultation.
Kamakshi Wason is Executive Director of TF Global Advisory Partners, where she leads enterprise engagements across strategy, program delivery, corporate events, and revenue enablement — backed by experience managing complex projects for top Fortune 500 organisations and clients, across 500+ international projects and stakeholders from more than 50 countries.
