Root Cause — Five Whys
Walk from incident symptom to systemic fix with the five whys.
Related prompts
More prompts with similar tags or categories.
Draft incident communications from the facts I provide. Produce: 1. Internal Slack update (technical, timeline-focused) 2. External status page update (user impact, workaround, next update time) 3. What not to say yet (unknowns) Calm, factual tone. No ETA unless confident.
Summarize research to inform a decision on [topic]. Include: - Common approaches and when each fits - Tradeoffs (complexity, cost, operability) - What our codebase already assumes - Recommendation with reversible vs one-way door flagged Link to official docs where possible. Mark uncertain claims.
Research how comparable products solve [feature/problem]. Structure: 1. 3–5 reference products or patterns 2. What works well for users 3. What to avoid (complexity, lock-in, privacy) 4. Implications for our constraints (stack, team size, timeline) 5. Recommended MVP scope Cite sources. No marketing fluff — focus on mechanics users feel.