RCP-007-001-001-FIVE-WHYS-v1.00a
CRAFT RECIPE START
RECIPE_ID: RCP-007-001-001-FIVE-WHYS-v1.00a
TITLE: 5 Whys Root Cause Analysis
DESCRIPTION: Implements the Toyota-originated "5 Whys" technique for systematic root cause analysis. This iterative interrogative method drills down through symptoms to uncover the fundamental cause of any problem. Enhanced with AI coaching, it guides users through structured problem-solving with intelligent follow-up questions and analysis validation. Ideal for business challenges, process improvements, and strategic decision-making.
DIFFICULTY: medium
CATEGORY: CAT-Analysis
SUBCATEGORY: SUBCAT-Problem-Solving
PROMPT TEMPLATE:
I want you to become my Root Cause Analysis Coach using the 5 Whys methodology. Your goal is to help me find the root cause of a problem through iterative questioning and analysis.
Based on my input, you will generate 3 sections:
**1) Revised Root Cause**
[Provide your analysis of the current root cause based on our discussion. Be specific and actionable]
**2) Suggestions**
[Provide suggestions on what details could improve our root cause analysis]
**3) Questions**
[Ask the next "Why" question to dig deeper, along with 1-2 clarifying questions]
We will continue this iterative process for at least 5 "Why" cycles, refining our understanding until we identify the true root cause.
{analysis_framework}
**Initial Problem Statement**: {problem_statement}
**Context**: {context}
**Impact**: {impact_description}
**Previous Attempts**: {previous_solutions}
{whys_history}
{additional_guidance}
After completing the 5 Whys analysis, provide:
1. **Root Cause Summary**: Clear statement of the identified root cause
2. **Causal Chain**: Visual representation of the why-chain from symptom to root
3. **Recommended Actions**: Specific steps to address the root cause
4. **Prevention Measures**: How to prevent recurrence
If you understand, begin by analyzing my problem statement and asking the first "Why" question.
PARAMETERS:
- problem_statement: string, required=True, description="Clear description of the problem you're experiencing"
- context: string, required=False, default="", description="Background information about when/where the problem occurs"
- impact_description: string, required=False, description="How this problem affects your business/project"
- previous_solutions: string, required=False, default="None attempted yet", description="What solutions have been tried before"
- analysis_framework: string, required=False, default="Use standard 5 Whys approach", choices=["standard", "fishbone", "systematic", "lean"], description="Analysis framework preference"
- whys_history: string, required=False, default="", description="Previous why-answers if continuing analysis"
- additional_guidance: string, required=False, default="", description="Specific areas to focus on or avoid"
EXAMPLES:
1. Business performance analysis:
```python
result = quick_recipe(
"https://www.aicookbook.ai/recipes-via-craft-api/rcp-007-001-001-five-whys",
problem_statement="Our customer retention rate dropped 25% in the last quarter",
context="This started after we launched our new pricing model",
impact_description="We're losing $50K MRR and team morale is low",
analysis_framework="systematic"
)
```
2. Technical issue investigation:
```python
result = quick_recipe(
"https://www.aicookbook.ai/recipes-via-craft-api/rcp-007-001-001-five-whys",
problem_statement="Website loading time increased from 2s to 8s",
context="Started last week, affecting all pages",
previous_solutions="Upgraded server capacity but no improvement",
additional_guidance="Focus on recent deployments and third-party integrations"
)
```
3. Team productivity challenge:
```python
result = quick_recipe(
"https://www.aicookbook.ai/recipes-via-craft-api/rcp-007-001-001-five-whys",
problem_statement="Development team missing sprint commitments for 3 sprints straight",
impact_description="Product roadmap delayed by 6 weeks",
context="Team of 8 developers, mix of senior and junior",
analysis_framework="lean",
whys_history="Why 1: Too many unplanned tasks. Answer: Support tickets taking 40% of time"
)
```
INTEGRATION NOTES:
This recipe works well with:
- Decision-making frameworks for solution evaluation
- Project management recipes for implementation planning
- Risk analysis recipes for prevention strategies
The 5 Whys process typically takes 15-30 minutes of iterative discussion. Document each why-answer pair for future reference and pattern recognition.
BEST PRACTICES:
1. Start with a specific, observable problem (not a solution or blame)
2. Base answers on facts and data when possible
3. Avoid jumping to conclusions - let the process reveal insights
4. Include relevant stakeholders in the analysis
5. Focus on process/system issues rather than people
6. Validate root cause by working backwards through the chain
PARAMETER VALIDATION:
- problem_statement: Must be specific and factual (min 10 words recommended)
- context: Keep focused on relevant details (max 300 words)
- whys_history: Format as "Why X: [Question] Answer: [Response]" for clarity
- analysis_framework: Each framework emphasizes different aspects of analysis
CRAFT RECIPE END
