When generating post-mortem documents with prompt sequences, it’s essential to establish a structured and methodical approach to analyze and document the circumstances surrounding an event, failure, or incident. Post-mortem documents are valuable for learning, process improvement, and transparency, particularly in technical, project, or business contexts.
Here’s a sequence of prompts to guide the creation of a comprehensive post-mortem document:
1. Context and Overview
-
What was the event or incident?
-
When did it occur (date/time/period)?
-
What were the expected outcomes versus the actual results?
-
What system, process, or product was affected?
-
Who was involved in managing or responding to the incident?
-
What was the severity of the incident? (e.g., minor, major, critical)
2. Timeline of Events
-
What was the sequence of events leading up to the incident?
-
At what point did the issue first become apparent?
-
How did the situation unfold over time?
-
How was it identified, escalated, and addressed?
-
What actions were taken in response, and when?
-
Were there any bottlenecks or delays in the resolution process?
3. Root Cause Analysis
-
What caused the issue? (e.g., human error, technical failure, external factors)
-
How was the root cause identified?
-
What systems or processes failed, and why?
-
Were there any contributing factors, such as poor communication, lack of resources, or outdated technology?
-
Could the root cause have been detected earlier?
4. Impact Assessment
-
Who or what was impacted by the incident? (e.g., customers, teams, product)
-
What was the scope of the impact? (e.g., number of users affected, financial loss, reputational damage)
-
How severe was the impact in terms of operational disruption?
-
Were there any legal, compliance, or regulatory implications?
5. Response and Recovery
-
How was the issue addressed once it was identified?
-
What immediate actions were taken to mitigate the problem?
-
How long did it take to resolve the incident?
-
What resources (people, tools, information) were needed for recovery?
-
Were there any gaps in response, or lessons learned in terms of recovery efforts?
6. Lessons Learned
-
What key insights or takeaways were gained from this incident?
-
What processes, tools, or practices need to be improved or changed?
-
Were there any successes or positive aspects in how the situation was handled?
-
What would have been done differently with the benefit of hindsight?
7. Preventive and Corrective Actions
-
What steps will be taken to prevent a similar incident in the future?
-
Are there any new policies, processes, or technologies that should be implemented?
-
What changes will be made to training, communication, or documentation?
-
How will the effectiveness of these changes be monitored over time?
8. Follow-up and Monitoring
-
What ongoing monitoring or checks will be put in place to ensure that the issue does not recur?
-
Is there a timeline for revisiting the incident or reviewing the corrective actions?
-
How will the team track progress on preventive measures and improvements?
9. Feedback and Collaboration
-
What feedback was received from stakeholders, teams, or users?
-
How was communication handled internally and externally?
-
What could be improved in terms of stakeholder engagement or collaboration?
10. Conclusion
-
Summarize the outcomes of the post-mortem analysis.
-
Highlight any critical decisions or changes made as a result of the incident.
-
Acknowledge the contributions of those involved in addressing the incident.
This sequence can be modified to suit specific industries or types of incidents (e.g., technical failures, business disruptions, product failures, etc.). Each section ensures that the analysis is thorough, actionable, and geared towards continuous improvement. Would you like to explore any specific aspects of this process or tailor it to a particular scenario?