Incident Title: [Incident Title]
Incident Date: [Incident Date]
Incident Duration: [Start Time] - [End Time]

1. Incident Overview

Provide a brief summary of the incident, including a description of what happened and its impact on the business or stakeholders. Link to the GitHub issue. (Try the Tettra GitHub integration to do this more easily!)

2. Incident Timeline

Create a chronological timeline of events leading up to and during the incident. Include key milestones, actions taken, and any notable observations.

3. Incident Response Team

List the members of the incident response team who were involved in managing and resolving the incident. Include their roles and responsibilities.

4. Incident Impact

Detail the impact of the incident on the business, customers, and stakeholders. Include any financial, operational, or reputational consequences.

5. Root Cause Analysis

Conduct a thorough root cause analysis to identify the underlying factors that contributed to the incident. Use appropriate investigative techniques (e.g., 5 Whys, Fishbone Diagram) to determine the root cause(s).

6. Immediate Actions Taken

Describe the immediate actions taken to contain and mitigate the incident. Include any temporary fixes or workarounds implemented to restore normal operations.

7. Communication and Stakeholder Management

Summarize the communication efforts made during the incident, both internally and externally. Describe how stakeholders were informed and kept updated throughout the incident lifecycle.

8. Lessons Learned

Highlight the key lessons learned from the incident. Identify areas for improvement in processes, systems, or training to prevent similar incidents in the future.

9. Corrective and Preventive Actions
Recommend corrective actions to address the root cause(s) of the incident. Propose preventive measures to minimize the likelihood of similar incidents occurring in the future.

10. Incident Response Evaluation

Evaluate the effectiveness of the incident response process. Identify strengths and areas for improvement in terms of incident detection, response time, escalation procedures, and overall coordination.

11. Documentation and Knowledge Sharing

Document all relevant information related to the incident, including incident logs, findings, and resolutions. Determine the best way to share this knowledge with the team and ensure it is accessible for future reference.

12. Incident Postmortem Conclusion

Provide a summary of the incident postmortem, emphasizing the key takeaways and actions required for improvement. Reinforce the importance of continuous learning and the proactive management of incidents.

13. Additional Info

Attach any supporting documents, incident reports, logs, or data that provide additional context or insights into the incident. You can link directly to other Tettra pages. 

 

Note: This template can be customized based on the specific needs and requirements of your business. Adapt and expand the sections as necessary to conduct thorough incident postmortems. Regularly review and update incident postmortems to enhance incident response capabilities and prevent future incidents.