← Back to Template Library
Engineeringengineeringincidentpost-mortemreliabilityon-call

Incident Post-mortem

Captures the timeline, contributing factors, detection gap, and the team's honest read on root cause — not just the proximate trigger. Designed to surface patterns across incidents when synthesized.

7 questions~25 min to complete

Use this template

Create a draft session from this template, then customize it before publishing.


Questions

1.

Walk me through the incident from your vantage point. What did you first notice, and when?

Include timing, what you were looking at, and what your initial read was.

Long textRequired
2.

What do you think actually caused this — not just the proximate trigger, but the conditions that made the trigger possible?

Think about: missing safeguards, knowledge gaps, deployment process, monitoring gaps, architectural assumptions.

Long textRequired
3.

How did we find out something was wrong? Was that fast enough?

Consider alerting thresholds, on-call coverage, customer reports, internal dashboards. What would have caught it sooner?

Long textRequired
4.

How would you rate the severity of the impact on users or the business?

Think about downtime duration, data affected, number of users impacted.

Rating scaleRequired
5.

What made the response harder than it needed to be?

Runbook gaps, unclear ownership, tooling issues, needing to wake someone up to ask a question — anything that slowed the fix.

Long textRequired
6.

Have we seen something similar before? If so, did we think we'd fixed it?

Even a loose resemblance counts — same system, same class of failure, same team involvement.

Long textOptional
7.

What's the one change that would most reduce the chance of this class of incident happening again?

Be specific. 'Better monitoring' is less useful than 'alert when the queue depth exceeds 10k for more than 2 minutes'.

Long textRequired

What you'll get

After each completed session, Mayetik generates a structured AI summary. Here's an example of the output format — the actual content reflects each respondent's answers.

Sample AI summary

Key themes from this session

The respondent's answers highlighted three recurring themes — each supported by specific examples drawn from their experience. The summary captures what was said, not what was expected.

Standout insights

Two responses stood out as unusually detailed and pointed to an area worth following up on. The full text of each answer is preserved below the summary.

Suggested next steps

Based on the patterns in this session, the AI identified three concrete actions for the project team to consider. These are drawn directly from the respondent's own suggestions.

Generated from 7 questions · ~25 min session


Ready to start from this template?

The template will be created as a draft session, so you can adjust the title, questions, and wording before publishing.