Why Leaders Keep Solving the Wrong Problem
A CEO once called in outside help because his projects kept stalling, deadlines were slipping, and his team was frustrated. He knew exactly what the problem was: the business analysts were the bottleneck. They couldn’t keep up, and it was killing timelines.
There was just one issue. He’d already fired and replaced three business analysts. Each time, he was sure the next one would fix it. Each time, the same problems returned within weeks.
This is the most common failure mode in root cause analysis for leaders: mistaking the most visible symptom for the actual cause. The analyst wasn’t the problem — the analyst was where the pain surfaced. The real dysfunction lived deeper in the system, invisible to anyone who hadn’t mapped it properly.
If you’ve ever “solved” a problem only to watch it reappear in a slightly different form, you’ve experienced this firsthand. The issue isn’t that you lack intelligence or effort. It’s that you’re applying both to the wrong variable.
The Symptom Trap: Why Smart Leaders Misdiagnose
When something goes wrong in an organization, the human brain does what it’s built to do — it looks for the most obvious explanation and locks on. The sales team missed their number? Must be a pipeline problem. Customer churn spiked? Must be a product quality issue. Projects keep stalling? Must be the people in the bottleneck role.
This instinct serves us well in simple environments. If the kitchen is on fire, you don’t need a systems analysis — you need a fire extinguisher. But the decisions that keep leaders up at night are rarely simple. They involve multiple interacting variables, feedback loops, and second-order effects that make surface-level diagnosis dangerously misleading.
As Drago Dimitrov writes in Instant Competence: “I had seen this pattern before — leaders chasing symptoms instead of root causes. What they thought was a talent problem was likely something deeper.”
The tell is always the same: if replacing the obvious culprit doesn’t fix the outcome, the obvious culprit isn’t the root cause. The real issue is still hidden beneath the surface.
Root Cause Analysis Starts with Systems, Not Suspects
Effective root cause analysis for leaders requires a fundamental shift in thinking. Instead of asking “who or what is causing this problem?” you need to ask: “What system is producing this outcome, and which variables in that system are misconfigured?”
This is the core insight behind Step 3 of the Instant Competence framework — what Dimitrov calls “HD Vision.” The idea is straightforward: every outcome you care about is produced by a system of contributing variables. Your job isn’t to stare at the outcome and wish it were different. Your job is to map the system behind it.
Consider the formula:
Y = w₁a + w₂b + w₃c + w₄d + w₅e
Your outcome (Y) is the weighted result of multiple variables (a, b, c, d, e), each with a different degree of influence (the weights: w₁, w₂, etc.). Some variables matter enormously — a single adjustment moves the needle. Others are nearly irrelevant, no matter how much attention you give them.
Dimitrov calls these variables “knobs” — and the metaphor is useful. You can’t change your outcome directly. You can only change the knobs that drive it. Root cause analysis, then, is really about three things:
- Identifying which knobs exist in the system producing your undesirable outcome
- Diagnosing the current state of each knob
- Determining which knobs carry the most weight — which ones, if turned, would actually shift the result
The Body Temperature Test: A Simple Way to Practice
Before applying this to a high-stakes business scenario, consider how naturally you already do root cause analysis in everyday life — when you let yourself.
You feel cold. That’s the undesirable outcome (Y). Can you snap your fingers and change how cold you feel directly? No. You have to work through the system. What variables — what knobs — influence your body temperature feeling?
- The weather outside
- The thermostat / AC setting
- What you’re wearing
- When you last ate
- Whether you’ve been moving or sitting still
Now, before rushing to a solution, you diagnose: What changed? You weren’t cold an hour ago. Did the AC kick on? Did the sun go down? Are you sitting by a window? This diagnostic step — figuring out which variable shifted — is the essence of root cause analysis. And notice what you’re not doing: you’re not blaming the weather and giving up. You’re identifying which knob you can actually turn.
As Dimitrov puts it: “I can’t just snap my fingers and instantly change the state of my body temp feelz directly; I need to understand the system behind body temp feelz, identifying what components affect it and how.”
This is exactly the same process leaders need to apply to revenue declines, team dysfunction, product delays, and strategic stalls — just with more variables and higher stakes.
How to Apply HD Vision to Your Toughest Problems
Here’s a practical process for conducting root cause analysis that actually reaches the root, drawn from the Instant Competence methodology:
1. Define Your Outcome Variable Precisely
Before you can map a system, you need to know what system you’re mapping. What is the specific outcome that isn’t where you want it to be? Not “things aren’t going well” — but a measurable, observable result. Project completion rate. Customer retention at 90 days. Revenue per sales rep. Time from lead to close.
Vague outcomes produce vague diagnoses. Precise outcomes reveal precise systems.
2. Break the Outcome into Contributing Variables
Ask: what factors combine to produce this outcome? List them without judgment. At this stage, you’re mapping the territory — not deciding what matters most.
For the CEO with stalling projects, the variables weren’t just “analyst quality.” They included the client feedback process, how development teams were structured, the sequencing of decisions, the clarity of project scoping, and communication channels between departments. The analyst was one variable in a system of many.
3. Assess the Weights
Not all variables matter equally. Dimitrov uses the analogy of chess pieces: “A queen in chess has greater influence over the game than a pawn.” A single turning click on one knob may produce more change than a full rotation on another.
Ask: if I could change only one variable, which would have the greatest impact on the outcome? That’s your highest-weight variable. That’s where root cause analysis should focus.
4. Diagnose Current States with Data, Not Assumptions
“We need realistic inputs for accurate outputs,” Dimitrov writes. “The measurement of your system’s current variables is akin to monitoring a patient’s vital signs before making a diagnosis.”
This is where most leaders go wrong. They assume they know the current state of each variable based on general impressions rather than actual measurement. The CEO “knew” the analysts were the problem — but he’d never measured the feedback cycle time, mapped the handoff points, or tracked where delays actually originated in the workflow.
5. Look for What Changed
Problems don’t appear from nowhere. Something shifted. Which variable moved? When did the outcome start deteriorating, and what happened in the system around that time? This temporal question cuts through noise faster than almost any other diagnostic tool.
6. Check for What’s Missing
One of the most powerful analytical tools in the Instant Competence framework is what Dimitrov calls “Omission Neglect” — noticing what’s absent. What variable isn’t being discussed? What data isn’t being collected? What question hasn’t been asked? Often, the root cause lives in the blind spot — the variable no one thought to include in the system map.
The Real Root Cause: A Case Study Resolution
When the CEO’s situation was analyzed through this systems lens, the real problem emerged. It had nothing to do with analyst talent. The dysfunction came from two structural issues:
First, clients were being overwhelmed with complex, disjointed decisions at each development iteration. The proper flow should have been agreeing on functions and the big picture first, before diving into minutiae. Instead, clients faced a firehose of granular choices they weren’t equipped to make quickly.
Second, the development teams were siloed — sitting in a holding pattern, waiting for a complete feedback loop that created an artificial bottleneck. The analysts weren’t slow; they were trapped in a broken process.
The solution wasn’t replacing people. It was restructuring how client feedback was gathered and how development teams operated concurrently. A systems fix, not a personnel fix.
This is the power of proper root cause analysis: it transforms expensive, repeating failures into one-time structural corrections. The CEO stopped cycling through analysts, the projects stopped stalling, and the team stopped feeling blamed for a systemic problem.
Three Questions to Start Today
You don’t need to master the entire Instant Competence framework to begin improving your root cause analysis immediately. Start with three questions the next time you face a recurring problem:
- “If I’ve already tried the obvious fix and it didn’t work, what does that tell me about where the real cause lives?” — The failed fix is data. It eliminates one variable and points you toward the rest of the system.
- “What are all the knobs in this system — not just the one I’m staring at?” — Force yourself to list at least five variables that contribute to the outcome. Most leaders stop at one or two.
- “What changed?” — Trace the problem back to when it started. Something in the system shifted. Find what moved, and you’ll find your root cause.
Root cause analysis isn’t about being smarter. It’s about being more systematic — resisting the urge to blame the most visible variable and instead mapping the system that’s actually producing your results.
Ready to Think Differently?
The approach described in this post is part of Drago Dimitrov’s Instant Competence system — a battle-tested methodology for leaders who need to make the right call, even when the path isn’t clear.
Read Instant Competence to get the complete 7-step framework, with real case studies and practical exercises for diagnosing systems and finding true root causes.
Or start with the free Clarity Worksheet — a guided tool for defining and solving your most pressing challenge.
For leaders who also need to analyze businesses systematically, Dimitrov’s second book What Does This Company Do? applies the same systems thinking to qualitative business analysis — 32 spectrums that reveal what a company actually does, beyond the financials.