Problem Solving: Find The Root Cause, The Minto Pyramid Principle, & More
5 of the best problem solving methods I've found
Alex Brogan
Most problems reveal their depth only under interrogation. The initial complaint — revenue declining, retention dropping, product launches failing — operates as symptom, not disease. Effective operators distinguish between proximate causes and root causes, then systematically excavate toward bedrock.
Root Cause Analysis: The 5 Whys Method
The 5 Whys framework, pioneered at Toyota, forces iterative questioning until you reach the structural source. A proximate cause represents the most immediately observable trigger. The root cause represents the underlying system failure that enabled the trigger.
Take a revenue decline:
Why did sales drop? Marketing qualified leads decreased.
Why did MQLs decrease? Campaign performance deteriorated.
Why did campaigns underperform? Creative messaging became stale.
Why did messaging go stale? No systematic creative testing process.
Why no testing process? Marketing operates reactively, not systematically.
Why did MQLs decrease? Campaign performance deteriorated.
Why did campaigns underperform? Creative messaging became stale.
Why did messaging go stale? No systematic creative testing process.
Why no testing process? Marketing operates reactively, not systematically.
The fifth why reveals the actual problem: operational structure, not campaign tactics. Fix the system, prevent the symptom's return. Most problem-solvers stop at the second or third why, addressing manifestations while leaving causes intact.
The method breaks down when problems have multiple contributing factors or when root causes exist outside your span of control. But it forces the essential discipline: keep digging until you hit bedrock.
The Minto Pyramid Principle
Barbara Minto's framework, developed during her tenure at McKinsey, structures problem-solving communication. The pyramid principle inverts typical analytical presentation — conclusion first, supporting arguments second, detailed evidence third.
This reversal serves cognitive efficiency. Decision-makers process conclusions, then selectively examine supporting logic as needed. The framework demands that you clarify your thinking before attempting to communicate it.
Process:
- Define the central question — the specific problem requiring resolution
- State your conclusion — the answer you're recommending
- Group supporting arguments — typically three primary pillars
- Order arguments logically — either by priority, chronology, or structural relationship
The pyramid forces intellectual honesty. If you cannot articulate three coherent reasons supporting your conclusion, your analysis remains incomplete. If your supporting arguments don't collectively answer the central question, you're solving the wrong problem.
Minto called this "a tool to help you find out what you think." The discipline of structuring arguments reveals gaps in reasoning that remain hidden in stream-of-consciousness analysis.
Ishikawa Diagram: Mapping Contributing Factors
The fishbone diagram, created by Kaoru Ishikawa for quality control, visualizes multiple potential causes branching toward a single effect. Unlike linear root cause analysis, the Ishikawa method acknowledges that complex problems typically emerge from interactions between several contributing factors.
Construction process:
- Define the problem as the "head" of the fish
- Identify contributing categories — for business problems, typically People, Process, Technology, Environment, Materials, and Methods
- Brainstorm potential causes within each category
- Analyze relationships between different causes
The diagram's value lies in systematic exploration rather than immediate solutions. By forcing examination across multiple dimensions, it prevents tunnel vision — the tendency to fixate on the most obvious or politically convenient explanation.
Consider a product launch failure. Technical execution might be flawless, but inadequate market research (Methods), insufficient staffing (People), and poor communication protocols (Process) could collectively doom the initiative. The Ishikawa diagram captures this multifactorial reality.
Inversion: Working Backward From Failure
Charlie Munger popularized inversion as a problem-solving technique: instead of asking "How do I succeed?" ask "How do I fail?" Then systematically avoid each failure mode.
Inversion leverages an asymmetric truth: avoiding stupidity proves easier than achieving brilliance. Most failures stem from predictable mistakes, not unforeseeable circumstances. By cataloging potential failure modes, you create a defensive checklist.
For launching a new product:
- How could this fail? No market need, poor execution, insufficient funding, competitive response, technical problems, regulatory issues
- How do I avoid each failure mode? Validate demand early, prototype extensively, secure adequate capital, analyze competitive dynamics, stress-test technology, research regulatory requirements
This approach proves particularly valuable for high-stakes, low-frequency decisions where learning from mistakes carries prohibitive cost. Better to fail hypothetically in analysis than actually in execution.
Inversion complements positive optimization. First, eliminate obvious failure modes. Then, among remaining options, optimize for success.
Issue Trees: Decomposing Complex Problems
Issue trees break large, ambiguous problems into smaller, answerable questions. The method applies structured decomposition — dividing complex issues into mutually exclusive, collectively exhaustive components.
Construction principles:
- MECE structure — each branch must be Mutually Exclusive and Collectively Exhaustive
- Actionable endpoints — terminal branches should represent specific, researchable questions
- Logical flow — the tree should guide systematic investigation
For declining customer retention:
Root question: Why is retention declining?
Primary branches: Acquisition quality, onboarding effectiveness, product satisfaction, competitive pressure
Secondary branches under Product Satisfaction: Feature gaps, performance issues, user experience problems, pricing concerns
Primary branches: Acquisition quality, onboarding effectiveness, product satisfaction, competitive pressure
Secondary branches under Product Satisfaction: Feature gaps, performance issues, user experience problems, pricing concerns
The tree provides investigative structure. Instead of analyzing "retention problems" generally, you examine specific hypotheses systematically. This prevents both analysis paralysis and premature conclusions.
Issue trees work best for strategic questions with multiple potential explanations. They're less useful for operational problems with obvious causes or technical issues requiring domain expertise rather than structured thinking.
These frameworks share common architecture: they force systematic rather than intuitive problem-solving. Intuition identifies problems quickly but often misdiagnoses causes. Systematic methods require more upfront investment but produce more durable solutions.
The meta-principle: match method to problem type. Root cause analysis for operational failures. Pyramid principle for communication and decision-making. Ishikawa diagrams for complex, multifactor issues. Inversion for high-stakes scenarios. Issue trees for strategic ambiguity.
Problems resist solutions not because they're unsolvable, but because they're incompletely understood. These frameworks force the discipline of understanding before acting.