Draft a blameless postmortem focused on system fixes

Turn raw incident notes into a neutral, blameless postmortem report centered on timeline analysis, contributing conditions, and concrete preventative actions.

Prompt

Prompt
Act as an agile delivery lead. Transform raw incident notes into a neutral, blameless postmortem report focused entirely on process, technical, and environment vulnerabilities.

- Write in strictly objective, non-accusatory language, using passive or process-oriented phrasing rather than naming individuals.
- Construct a chronological timeline of detection, response, and resolution events.
- Identify underlying systemic contributors rather than stopping at individual human errors.
- Formulate specific preventative action items with measurable closure criteria.

Output format:### Incident Summary
- Impacted services, duration, and user impact severity

### Chronological Event Timeline
- Date/Time: Event observation or action taken

### Systemic Contributing Factors
- Environmental, tooling, and process gaps

### Action Items & System Safeguards
Columns: Action Item | Prevention Focus | Target Completion Date | Success Measure

Here are my incident notes:

Example output

Example for: Production deployment database outage

Incident Summary
  • Impacted Services: Customer Portal and User Authentication API
  • Outage Duration: 52 minutes (14:08 UTC - 15:00 UTC)
  • Severity: High (Users were unable to log in or process payments)
Chronological Event Timeline
  • 14:05 UTC: Scheduled database migration script executed as part of release v2.4.
  • 14:08 UTC: Automated connection pool exhaustion alerts triggered; login endpoints timed out.
  • 14:15 UTC: Deployment team halted release pipeline and engaged on-call database administrators.
  • 14:32 UTC: Lock contention identified on the user authentication table due to an unindexed migration query.
  • 14:48 UTC: Rollback script completed; database locks released.
  • 15:00 UTC: Portal health checks passed; incident declared resolved.
Systemic Contributing Factors
  • Pre-deployment testing gap: Staging database lacked production-scale dataset volume, hiding query lock latency during staging pipeline runs.
  • Deployment guardrails: The automated CI/CD pipeline allowed long-running schema changes to execute without an explicit lock timeout flag.
Action Items & System Safeguards
Action ItemPrevention FocusTarget Completion DateSuccess Measure
Implement query lock timeout limits in migration runnerTechnical guardrailNov 12Scripts abort safely after 5 seconds of lock contention
Mirror production table sizes in staging environmentTest environment fidelityNov 20Migration benchmark tests run on 1M+ mock rows
Update deployment checklist with schema change reviewProcess improvementNov 08Mandatory DBA review on all schema alters
Written by AI from this prompt. Your results will vary.

Paste your raw notes, chat snippets, or incident logs after the prompt in ChatGPT, Claude, or Gemini. Ask the model to convert the resulting action items into Jira ticket descriptions if you need ready-to-file tasks.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Project Management
Project Management

Extract a RAID log from meeting notes

Quickly pull out risks, assumptions, issues, and dependencies from raw, unstructured project sync notes into a clean tracking table.