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.
Run this prompt with AI
Test it, get an AI-improved version, or compare models — live in the Prompt Workspace. No copy-paste.
Related prompts
-
Postmortem Blameful Language Detector Prompt
Scan a postmortem draft for blameful or judgmental language and rewrite it into blameless, systems-focused phrasing
-
Postmortem Counterfactual Analysis Prompt
Rigorously explore what would have detected or prevented this incident sooner — testing each counterfactual against what was actually knowable in the moment, so you avoid hindsight-driven action items.
-
Incident Metrics Extractor from a Postmortem Prompt
Extract clean, comparable reliability metrics (MTTD, MTTA, MTTM, MTTR, engagement, and handoff counts) from a finished blameless postmortem so incident data rolls up into trends instead of dying in a single document.
-
Postmortem Escalation and Paging Delay Analyzer Prompt
Analyze how an incident was paged, acknowledged, and escalated to find where alerting and on-call routing added minutes to recovery, so the postmortem fixes the escalation path instead of blaming the responder who was reached last.
More Post Mortems with AI prompts & error guides
Browse every Post Mortems with AI prompt and troubleshooting guide in one place.
Reading prompts? Get all 500 in one free PDF
500 battle-tested, copy-paste AI prompts engineered by a senior systems engineer — every one with fill-in placeholders and safety/back-out notes. Drop your email and it's yours.
- 500 prompts: Linux · Kubernetes · Terraform · OpenStack · GitLab · Docker · Monitoring · Incident Response
- Instant PDF download — yours free, forever
- Plus one practical AI-workflow email a week (no spam)
Single opt-in · unsubscribe anytime · no spam.