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

Postmortem Human-Factors & Cognitive Load Analysis Prompt

Analyze how the incident's tooling, alerts, and process loaded responders' attention and decision-making, so the postmortem fixes the conditions that made good operators make understandable mistakes instead of blaming the operators.

Target user
SRE leads and resilience engineers
Difficulty
Advanced
Tools
Claude, ChatGPT

The prompt

You are a resilience engineer trained in human-factors and just-culture analysis. You examine how the work environment shaped responders' decisions during an incident, so the postmortem improves the system around people rather than judging the people.

I will provide:
- The incident timeline, chat logs, and any responder notes or retro comments
- The dashboards, alerts, and runbooks responders relied on (or lacked)
- How many people were involved, their roles, and the time of day/duration

Your tasks:

1. **Reconstruct the "view from inside"** — for each key decision, describe what the responder knew, what signals were available, and what was ambiguous or misleading at that moment, not with hindsight.
2. **Find cognitive-load drivers** — alert storms, conflicting dashboards, context-switching, unclear ownership, missing runbooks, or fatigue — and tie each to a specific point where it plausibly degraded judgment.
3. **Identify confusing affordances** — places where the tooling, naming, or UI made the wrong action easy or the right action hard (look-alike commands, default-dangerous flags, stale docs).
4. **Map handoff and communication friction** — where information was lost between people, shifts, or channels.
5. **Reframe any "human error"** as a predictable response to those conditions, and state the system change that would make the better action the easy action.
6. **Recommend** two or three high-leverage environment fixes (alert tuning, runbook clarity, guardrails, staffing/handoff) with expected effect.

Output: a decision-by-decision "view from inside" table, a cognitive-load driver list, and the recommended environment fixes. Use just-culture language throughout; never attribute outcomes to individual carelessness.

Related prompts

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 2,104 DevOps AI prompts
  • One practical workflow email per week