postmortem

Improved Prompt

Project Postmortem Analysis Report Template

Objective:
Create a comprehensive postmortem analysis report documenting a recent system failure incident. The report should provide an in-depth analysis, including a clear timeline of events, the root cause of the issue, the steps taken to resolve it, and recommendations for future prevention.

Report Structure:

1. Executive Summary (1 paragraph)

• Concise overview of the incident, its impact, and the resolution.
• Purpose of the report and what it covers.

2. Chronological Timeline of Events (Bullet points)

• Explicitly outline the sequence of events that led to the failure.
  • Include exact timestamps.
  • Highlight key actions taken by the team.
• Show the progression of the problem, step by step.

3. Technical Analysis (2-3 paragraphs)

• Detailed explanation of what happened technically.
  • Identify the root cause of the failure.
  • Describe the system components involved.
  • Explain how the failure propagated through the system.
• Use technical terms where necessary; define them in the next section.

4. Technical Terms Used (List with definitions)

• List all technical terms used in the report.
• Define each term in simple, non-technical language.
• Cross-reference any terms mentioned in the technical analysis section.

5. Resolution Steps (Bullet points)

• Exactly list each command executed or action taken during the recovery process.
  • Include command syntax.
  • Explain the rationale behind each step.
  • Highlight any challenging or unusual solutions required.
• Describe the final resolution that restored service.

6. Lessons Learned & Next Steps (2-3 paragraphs)

• Reflect on what went well during the incident response.
• Identify areas that need improvement in the process or system.
• Propose concrete, actionable recommendations for the future.
  • Suggest system enhancements for resilience.
  • Recommend process improvements for incident management.
  • Propose training or documentation updates.

7. Conclusion (1 paragraph)

• Summarize the key findings.
• Reiterate the importance of the recommendations.
• Encourage prompt action on the suggestions.

Formatting Guidelines:

• Use Markdown format.
• Headings should be H2 (##) and H3 (###) level.
• Bullet points for lists.
• Bold or italicize key points as necessary for emphasis.
• Maintain a clear, structured, and logical flow throughout the document.