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
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
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.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Structure vague project lessons into searchable entries
Transform unstructured retrospective notes into categorized, searchable knowledge base entries with specific triggers and preventative actions.
Convert retro feedback into actionable lessons learned
Transform messy sprint retrospective comments into a structured lessons learned register with root causes and assigned owners.
Analyze timeline and budget trade-offs for scope requests
Turn vague stakeholder feature requests into clear trade-off scenarios. Use this when clients or leaders request additions without considering cost or delay.
Turn engineering updates into marketing launch timelines
Convert technical dev release notes into clear go-to-market milestones with lead times. Use this when your marketing team struggles to plan campaigns around developer jargon.
Explain budget variances and propose corrective actions
Turn raw spend figures and project status notes into an objective financial variance memo. Includes root cause, financial impact, and actionable recovery steps.
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.