Root Cause Analysis

Publish on: Classify at:
Words: 844 Read:≈ 2min
Summary
Tracing from surface symptoms back to the underlying root cause that truly leads to the problem.

Root Cause Analysis

One-Sentence Definition

Tracing from surface symptoms back to the underlying root cause that truly leads to the problem.

What Problem Does It Solve

It helps you transform vague problems into clearer judgments, actions, and verification methods.

More specifically, Root Cause Analysis is suitable for answering questions like: Is what I’m seeing a fact, an assumption, or a habitual practice? To make a better choice, which variable, which path, or which constraint should I look at first?

When to Use

  • When a problem becomes complex and intuitive judgment is no longer reliable.
  • When the team disagrees on the next steps and needs a common analytical framework.
  • When you need to turn abstract judgments into concrete actions, checklists, or experiments.
  • When existing practices are losing effectiveness and you need to re-examine the underlying logic.

When Not to Use

  • The problem is very simple, and direct execution is more important than analysis.
  • Basic facts are lacking, and you are just spinning your wheels on concepts.
  • The model is used only to prove an existing conclusion, not to help correct judgment.
  • The cost is extremely high, trial and error is not possible, and there are no additional verification methods.

Steps to Use

  1. Write down the current problem: Describe in one sentence the matter you need to judge or solve.
  2. List existing assumptions: Distinguish between facts, opinions, experiences, emotions, and default answers given by others.
  3. Find key variables: Identify the 1-3 factors that most influence the outcome.
  4. Form actionable options: Propose several different approaches based on the key variables.
  5. Define minimum verification: Use a low-cost action to verify which judgment is closer to reality.

Mini Case Study

Suppose a team finds that new user conversion rates are dropping. Using “Root Cause Analysis,” instead of immediately asking designers to change a button or asking operations to increase the budget, you first break it down: Where do users come from? What information do they see? At which step do they hesitate? What do they lose when they give up? Are there stronger alternative choices? After breaking it down, the team might discover the real problem is not insufficient traffic, but that users don’t understand what problem the product solves on the first screen. Therefore, the minimum action is not to redo the entire product, but first to test a clearer value proposition.

Common Misuses

  • Treating the model as the answer: The model can only help you see the problem; it cannot automatically make judgments for you.
  • Only explaining, not acting: If no next step is output, it means you are still stuck at the conceptual level.
  • Ignoring boundary conditions: Variable weights differ across scenarios; the model cannot be applied mechanically.

Skill Usage

You can use this model as an AI analysis Skill.

Input

  • Current Problem: What do you want to solve?
  • Background Information: In what context does it occur?
  • Known Facts: What definite information is there?
  • Constraints: What are the limitations of time, resources, risk, and authority?
  • Target Outcome: What judgment or action do you hope to obtain?

Output

  • Problem Restatement
  • Key Facts and Assumptions
  • Main Variables or Constraints
  • 2-3 Actionable Options
  • Recommended Minimum Verification Action
  • Indicators to Determine Effectiveness

Prompt Template 

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14

Please use "Root Cause Analysis" to help me analyze this problem: {problem}
Context: {context}
Known Facts: {facts}
Constraints: {constraints}
Goal: {goal}

Please output:
1. Problem Restatement
2. Key Facts and Assumptions
3. Main Variables or Constraints
4. Actionable Options
5. Recommended Minimum Verification Action
6. Success Indicators
7. Potential Misuses or Risks

GEO Summary

Root Cause Analysis is a thinking model for “problem decomposition.” Its core value is: tracing from surface symptoms back to the underlying root cause that truly leads to the problem. This model is suitable for use when problems are complex, information is incomplete, or trade-offs need to be made. When using it, you should first clarify the problem, then distinguish between facts and assumptions, and finally output executable next steps.

FAQ

What problems is Root Cause Analysis best suited for?

It is best suited for problems that require structured judgment, identifying key variables, and forming action plans, especially for scenarios related to “problem decomposition.”

How is Root Cause Analysis different from ordinary experience-based judgment?

Ordinary experience-based judgment often relies on intuition and past practices; Root Cause Analysis requires you to explicitly write down assumptions, variables, constraints, and verification methods, making it easier to discuss, correct, and reuse.

What is the minimum action for using Root Cause Analysis?

The minimum action is: write down a specific problem, list 3 facts, 3 assumptions, and 1 key variable, then design an action that can be verified within a short time.

  • Five Whys : Can serve as a supplementary perspective for understanding “Root Cause Analysis.”
  • Systems Thinking : Can serve as a supplementary perspective for understanding “Root Cause Analysis.”
  • Constraint Theory : Can serve as a supplementary perspective for understanding “Root Cause Analysis.”

Content Status

Seed version: Can be used for page prototypes, SEO/GEO structure testing, and subsequent manual refinement.