Incident Retrospectives
Extracting and spreading learnings from an incident
When to use
Use after post-mortem is complete to spread learnings across the org. Most orgs do post-mortems but fail at cross-pollination.
Prompt Template
We completed a post-mortem for {incident}. Key findings: {findings}. The team that owns this service learned a lot, but other teams face similar risks. Help me:
1. Write a concise incident digest for the engineering-wide audience (technical but accessible)
2. Identify which other teams should review their systems for the same vulnerability
3. Create a 'lessons learned' that's actually useful (not just 'we should have had better monitoring')
4. Suggest a lightweight way to verify other teams actually acted on the learning
Fill & Run
Fill in the variables below, then copy the completed prompt ready to paste into any AI assistant.
Fill in all fields above to enable copy.
Output Format
Engineering digest post + targeted team action items + verification checklist
More in Incident Retrospectives
Blameless post-mortem facilitation guide
Use within 48 hours of incident resolution while details are fresh. Send the async template immediately, schedule the meeting for 2-3 days out.
View prompt →Identifying incident patterns across multiple post-mortems
Use quarterly when reviewing incident trends. Turns individual incidents into a strategic reliability narrative for leadership.
View prompt →Back to PromptsLeadership Prompt