Root Cause Analysis
5 Whys + Fishbone Hybrid
When a problem keeps returning: a full 5-Whys chain, then a six-category fishbone so you don't miss a cause the chain skipped.
The Prompt
five-whys-and-fishbone-hybrid.md
You are a root cause analyst using a hybrid 5-Whys + Fishbone (Ishikawa) method. PROBLEM STATEMENT: {{problem}} CONTEXT: - Environment / system: {{environment}} - What has already been tried: {{tried}} - Constraints: {{constraints}} INSTRUCTIONS: 1. Restate the problem as a clear, measurable "problem is X, should be Y" statement. 2. Run 5-Whys: ask "why" at least five times. Show every why on its own line - do not collapse steps. 3. Cross-check the root cause(s) against a Fishbone across: People, Process, Equipment/Tools, Materials/Inputs, Environment, Measurement. Flag any category with plausible contributing factors even if the 5-Whys chain missed them. 4. Distinguish: root cause(s) | contributing factors | symptoms. 5. Propose 2 - 3 corrective actions per root cause, each tagged [Quick fix / Systemic fix], with the trade-off of each. 6. End with one paragraph: "If you fix nothing else, fix this - because..." OUTPUT FORMAT: - Problem statement (1 line) - 5-Whys chain (numbered) - Fishbone table (6 categories × findings) - Root causes vs contributing factors vs symptoms - Corrective actions (table: Action | Type | Effort | Root cause addressed) - Closing "fix this first" paragraph CONSTRAINTS: - Do not jump to a solution before completing the 5-Whys chain. - If information is missing to continue a why, state the assumption explicitly rather than inventing data. - Keep each why answer to one sentence.
Negative prompt
Included when you copy the prompt
Do not invent facts, logs, or attempted fixes that are not in the inputs. Do not skip to solutions before the 5-Whys chain is complete. Do not merge fishbone categories or drop empty ones - list all six. Do not treat a person as the root cause when a process, tool, or incentive explains the evidence.
Fill in your details below - this prompt updates as you type, then copy it.
Fill in your details
0 of 4 filled. Preview updates as you type - then copy the finished prompt (negative prompt included when present).
five-whys-and-fishbone-hybrid.md
Prompt preview
You are a root cause analyst using a hybrid 5-Whys + Fishbone (Ishikawa) method. PROBLEM STATEMENT: {{problem}} CONTEXT: - Environment / system: {{environment}} - What has already been tried: {{tried}} - Constraints: {{constraints}} INSTRUCTIONS: 1. Restate the problem as a clear, measurable "problem is X, should be Y" statement. 2. Run 5-Whys: ask "why" at least five times. Show every why on its own line - do not collapse steps. 3. Cross-check the root cause(s) against a Fishbone across: People, Process, Equipment/Tools, Materials/Inputs, Environment, Measurement. Flag any category with plausible contributing factors even if the 5-Whys chain missed them. 4. Distinguish: root cause(s) | contributing factors | symptoms. 5. Propose 2 - 3 corrective actions per root cause, each tagged [Quick fix / Systemic fix], with the trade-off of each. 6. End with one paragraph: "If you fix nothing else, fix this - because..." OUTPUT FORMAT: - Problem statement (1 line) - 5-Whys chain (numbered) - Fishbone table (6 categories × findings) - Root causes vs contributing factors vs symptoms - Corrective actions (table: Action | Type | Effort | Root cause addressed) - Closing "fix this first" paragraph CONSTRAINTS: - Do not jump to a solution before completing the 5-Whys chain. - If information is missing to continue a why, state the assumption explicitly rather than inventing data. - Keep each why answer to one sentence.
Examples
Example input
Problem: Same SKUs go out of stock every Friday afternoon even though Monday inventory looks healthy. Started six weeks ago after we switched to a new 3PL. Lost ~$18k in weekend ads that pointed at empty PDPs. Environment: Shopify + 3PL warehouse; replenishment is a weekly spreadsheet from merchandising. Tried: Raised safety stock 20%; asked 3PL to pick faster on Fridays. Still stocked out. Constraints: Cannot change 3PL this quarter; one ops hire; no new WMS budget.
What you should get
Problem statement: Friday available-to-sell is 0 on 12 - 18 hero SKUs; Monday ATS is 40 - 90 units. Target: ATS > 20 through Sunday. 5-Whys: Friday sell-through > replenishment cadence → weekly PO lands Tuesday AM → Friday demand was underestimated after ad calendar changed → demand forecast still uses last-year weekday mix → no one owns a promo-adjusted forecast. Fishbone: People (no owner for promo vs inventory), Process (weekly PO lock Monday 10am), Equipment (spreadsheet, not ATS), Materials (3PL cut-off 2pm Thu), Environment (weekend ads), Measurement (forecast ignores campaign calendar). Root cause: Replenishment calendar is decoupled from the ads calendar. Contributing: 3PL Thursday cut-off. Symptom: Friday OOS. Fix this first: Move PO lock to after the ads calendar is frozen, or auto-hold weekend ads when ATS < 20 - everything else is a symptom of that mismatch.
When to use this prompt
Use it when
- You need help with managers.
- You need help with engineers.
- You need help with operators.
- You need help with founders.
Skip it when
- You only need a one-line ask with no constraints, format, or context.
- You cannot supply the fill-in details the template asks for.
- A different category or tool-specific workflow fits the job better.
How to get a good result
Done when
Problem statement: Friday available-to-sell is 0 on 12 - 18 hero SKUs; Monday ATS is 40 - 90 units. Target: ATS > 20 through Sunday. 5-Whys: Friday sell-through > replenishment cadence → weekly PO lands Tuesday AM → Friday demand was underestimated after ad calendar changed → demand forecast still uses last-year weekday mix → no one owns a promo-adjusted forecast. Fishbone: People (no owner for promo vs inventory), Process (weekly PO lock Monday 10am), Equipment (spreadsheet, not ATS), Materials (3PL cut-off 2pm Thu), Environment (weekend ads), Measurement (forecast ignores campaign calendar). Root cause: Replenishment calendar is decoupled from the ads calendar. Contributing: 3PL Thursday cut-off. Symptom: Friday OOS. Fix this first: Move PO lock to after the ads calendar is frozen, or auto-hold weekend ads when ATS < 20 - everything else is a symptom of that mismatch.
Common mistakes
- Leaving problem, environment, tried vague - the model then invents placeholders.
- Asking ChatGPT, Claude, Gemini, or Perplexity for a shorter answer after a long structured prompt - that throws away the format rules.
- Stopping when the first draft appears instead of checking it against the success criteria below.
FAQ
- What do I fill in before I copy this prompt?
- Replace these placeholders with your details: problem, environment, tried, constraints. Required fields are marked on the page. The prompt text updates as you type.
- Which AI tools is this prompt written for?
- It works best with ChatGPT, Claude, Gemini, Perplexity. Copy the filled prompt and paste it into the tool you already use.
- What should a good result look like?
- Problem statement: Friday available-to-sell is 0 on 12 - 18 hero SKUs; Monday ATS is 40 - 90 units. Target: ATS > 20 through Sunday. 5-Whys: Friday sell-through > replenishment cadence → weekly PO lands Tuesday AM → Friday demand was underestimated after ad calendar changed → demand forecast still uses last-year weekday mix → no one owns a promo-adjusted forecast. Fishbone: People (no owner for promo vs inventory), Process (weekly PO lock Monday 10am), Equipment (spreadsheet, not ATS), Mate…
- What are common mistakes with this prompt?
- Leaving problem, environment, tried vague - the model then invents placeholders. Asking ChatGPT, Claude, Gemini, or Perplexity for a shorter answer after a long structured prompt - that throws away the format rules. Stopping when the first draft appears instead of checking it against the success criteria below.
Best for
- Managers
- Engineers
- Operators
- Founders
Related Prompts
More prompts like this — same topic and style.