Find the root cause of an operational issue
Drill down through recurring symptoms to identify systemic causes and design prevention fixes rather than temporary patches.
Prompt
Act as an operational problem-solving specialist using the Five Whys methodology. Before providing an analysis, ask me exactly 3 short numbered questions in one message and wait for my response: 1. What specific incident or failure occurred? 2. What temporary fix was applied? 3. Who is directly involved in the process? Once I reply, map the issue through five successive levels of causation, ensuring each level targets process or system breakdowns rather than human blame. Output format: A numbered chain from Why 1 to Why 5 with short causal statements; a section titled Root Cause Summary; and a section titled Preventive Countermeasures with 2 immediate systemic fixes.Example output
Paste into ChatGPT, Claude or Gemini and answer the three questions it sends back. To test the diagnosis further, ask the AI to suggest a simple early-warning metric for the new root cause.
Make it repeatable
Keep using this prompt without pasting it in every time.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Map branching root causes for multi-factor incidents
Analyze systemic breakdowns across parallel technical, operational, and communication branches instead of relying on a single 5 Whys chain.
Distinguish enduring workplace tools from trend hype
Filter enterprise software and process fads through enduring utility principles. Use it before approving new software licenses or department overhauls.
Separate verified facts from guesswork in incident reports
Sort timeline events in post-incident logs into proven evidence versus speculative blame so your team addresses real root causes.
Untangle a recurring disagreement to find the root issue
Break down circular arguments into underlying facts, misaligned priorities, and emotional stakes. Use it when team or relationship conversations keep stalling.
Identify perverse incentives in a proposed policy
Expose unintended consequences, metric gaming, and perverse incentives hidden inside proposed rules. Perfect for managers drafting new KPIs or policies.
Isolate the primary constraint in an operational workflow
Pinpoint the single limiting bottleneck in a multi-step process so your team avoids wasting effort on non-constraining tasks.
- Resolve conflicting advice with first principles
- Weigh hidden switching costs before changing tools
- Classify decisions into reversible and one-way doors
- Find a creative third option past an either-or trap
- Improve a broken process by subtracting unnecessary steps
- Separate actionable leading indicators from vanity metrics