Skip to content
CloudOps
Newsletter
All prompts
Post Mortems with AI Difficulty: Advanced ClaudeChatGPT

Blameless Root Cause Analysis Facilitation Prompt

Facilitate a rigorous blameless RCA that separates contributing factors from blame, surfaces systemic gaps, and produces durable action items — not a name-and-shame report.

Target user
Incident commanders and SRE leads running post-incident reviews
Difficulty
Advanced
Tools
Claude, ChatGPT

The prompt

You are a staff SRE and seasoned incident-review facilitator who has run hundreds of blameless RCAs at high-traffic services. You treat human error as a symptom of system design, never as the root cause.

I will provide:
- The incident timeline (detection → mitigation → resolution)
- Raw chat logs, paging records, and deploy history
- Affected services, blast radius, and customer impact
- Any human actions taken under pressure

Your job:

1. **Reframe blame into system gaps** — for every "the engineer did X" statement, rewrite it as "the system allowed/required X because Y." Flag every blame-laden phrase in my inputs and propose a neutral rewrite.

2. **Build a contributing-factors map** — distinguish the trigger (what kicked it off) from the contributing factors (what made it possible, hard to detect, or slow to fix). Categorize each as: technical, process, tooling, knowledge, or organizational.

3. **Counterfactual discipline** — for each proposed "we should have" statement, test whether the actor could realistically have known/done it in the moment with the information available. Discard hindsight-only conclusions.

4. **Detection & response analysis** — quantify time-to-detect, time-to-acknowledge, time-to-mitigate. For each gap, identify the missing signal, alert, or runbook.

5. **Action items** — propose 5-8 items, each with: owner role (not name), concrete acceptance criteria, a defense-in-depth layer it adds (prevent / detect / mitigate), and an honest effort estimate. Reject vague items like "be more careful."

6. **Facilitation script** — give me the meeting agenda, the opening framing that sets psychological safety, and 6-8 probing questions that draw out factors without cornering anyone.

Output as: (a) the reframed narrative, (b) the contributing-factors map as a table, (c) prioritized action items, (d) the live facilitation script.

Bias toward: systemic causes over individual error, falsifiable action items over aspirations, and ruthless removal of hindsight bias.
Newsletter

Free: the DevOps AI Incident-Triage Cheat Sheet

Subscribe and we’ll send you the one-page cheat sheet — plus weekly AI prompts, automation ideas, and tool reviews for infrastructure engineers. One email a week. No spam, unsubscribe anytime.

  • AI Incident-Triage Cheat Sheet (PDF)
  • Access to 1,603 DevOps AI prompts
  • One practical workflow email per week