Root Cause

Root Cause Analysis (WHERE -> WHY)

When to Apply

• Buffer enters YELLOW or RED zone
• Actions executed but metrics not moving (Layer 1 OK, Layer 2 stalling)
• Significant KPI decline detected
• Review engine Question 5 triggers (was root-cause analysis correct?)
• Any time "why isn't this working?" is asked

Core Framework

Stage 1 — WHERE (Locate the Problem)

MECE decomposition of the underperforming Goal into Drivers, identifying which specific Driver(s) are stalling.

Goal buffer: YELLOW (45% consumed, 34% progress)

WHERE analysis (MECE decomposition by Driver):
  Social growth:      45% of target   Low post frequency -> Low engagement
  -> Low follower growth -> Less audience feedback -> No content ideas
  (loop restarts)

Intervention (4-Step Process)

1. Identify the loop in the causal graph
2. Evaluate each node for intervention viability:

• Controllable by us? (exclude external factors)
• Executable at low cost?
• High ripple effect when broken?

1. Project the virtuous cycle that results from intervention
2. Generate concrete Actions via 3-option choice

Best intervention point: "No content ideas" (controllable, low cost, high ripple)

Projected virtuous cycle:
  Content ideas from research -> Higher post frequency ->
  Better engagement -> Follower growth -> More feedback ->
  More content ideas (positive loop)

Decision Rules

1. WHERE before WHY — always locate the gap before investigating causes
2. MECE decomposition — WHERE analysis must be mutually exclusive, collectively exhaustive
3. Verification status is mandatory — every causal node must be tagged
4. Hypotheses must be tested — don't build Actions on unverified hypotheses
5. Action targets on verified nodes — only target verified, controllable causes
6. Vicious cycles get priority — breaking a negative loop has outsized impact

Anti-Patterns to Detect

| Anti-Pattern | Signal | Response | |---|---|---| | Coin-flip cause | Cause is negation of problem | "This restates the problem. What's the specific mechanism?" | | Logical leap | Gap in causal chain | "Insert 'therefore' between these nodes. There's a missing step." | | Skipping WHERE | Jumping to WHY without locating gap | "First, which specific Driver is stalling? MECE decompose." | | Unverified action targets | Building Actions on hypotheses | "This cause is unverified. Verify before investing resources." | | Ignoring vicious cycles | Linear analysis of circular problem | "These causes form a loop. Breaking the cycle has outsized impact." | | Symptom treatment | Acting on surface symptom, not root cause | "This addresses the symptom. Let's drill one more layer to the mechanism." |

---

Anticipative Execution Reminder

When applying this framework, produce the FULL output immediately. Do not ask the founder which parts to analyze or which options to consider. Infer from business context, present the complete deliverable, and let the founder react to concrete work — not abstract choices.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: masterleopold
• Source: masterleopold/anty-framework
• License: MIT
• Homepage: https://4n7y.com

Install and usage instructions live in the source repository linked above.