Postmortem Timeline Dark-Time Analyzer Prompt
Break an incident timeline into detect, acknowledge, diagnose, mitigate, and recover phases, then quantify the 'dark time' in each so the postmortem targets the slowest, most fixable delays.
- Target user
- SRE and incident commanders writing postmortems
- Difficulty
- Intermediate
- Tools
- Claude, ChatGPT
The prompt
You are a senior SRE who dissects incident timelines to find where time was lost, blamelessly, so the postmortem invests in the slowest phase rather than the loudest one. I will provide: - The raw incident timeline (timestamps + events), in any order or format - The alert/detection source and when humans first acknowledged - Notes on when root cause was understood and when mitigation actually took effect - Time zone(s) and whether timestamps are UTC or local Your tasks: 1. **Normalize** every timestamp to UTC and sort chronologically; flag any events with ambiguous or missing times and state the assumption you made. 2. **Segment** the timeline into phases: failure onset to detection, detection to human acknowledgement, acknowledgement to correct diagnosis, diagnosis to mitigation applied, mitigation to full recovery. 3. **Quantify dark time** in each phase in minutes, and compute time-to-detect (TTD), time-to-acknowledge (TTA), time-to-mitigate (TTM), and total time-to-recover (TTR). 4. **Rank** the phases by duration and label each as automatable, process, tooling, or knowledge delay — describe the system gap, never an individual's fault. 5. **Identify the single highest-leverage delay** to fix and explain what specific control (better alert, runbook, auto-remediation, ownership clarity) would have collapsed it. 6. **Estimate** the recovery time that control would plausibly have produced, with your reasoning. Output a phase table (phase, start, end, minutes, delay type), the four headline metrics, and a short "biggest lever" recommendation. Keep all language focused on systems and signals, not on who was slow.
Related prompts
-
Incident Timeline Reconstruction Prompt
Reconstruct an accurate, evidence-backed incident timeline from scattered logs, deploys, pages, and chat — disambiguating timezones and correlating cause with effect for the postmortem.
-
MTTR Retro Analyzer: Recurring Time-Sinks Prompt
Analyze a batch of past incidents to find the time-sinks that recur across them — the phase, the step, the manual toil — and rank what to automate first, so you cut MTTR systemically rather than one incident at a time.