Incident PM Checklist

Pre-PM.

Overview

A pre-postmortem checklist guides the preparation work before the meeting. Timeline assembled, impact quantified, contributing factors drafted, action items proposed, attendees confirmed; the meeting itself becomes far more productive when this work is done up front.

• Timeline assembled. Slack messages, alerts, deploy events collected into one document before the meeting; the meeting analyses rather than reconstructs.
• Impact quantified. Customer impact, revenue impact, internal impact measured before the meeting; concrete numbers beat estimates negotiated live.
• Contributing factors listed. Root causes and contributing factors drafted before the meeting; the meeting refines and confirms rather than starting from scratch.
• Action items and attendees prepared. Initial action items drafted, right people invited (engineering, on-call, product, any affected team representative).

The approach

Templated pre-PM document, named scribe, time-boxed prep, linked artefacts. The template structures the work; the discipline is filling it in before the meeting rather than during it.

• Use a template. Shared PM template across the team produces comparable documents; every PM has the same shape so cross-PM analysis is possible.
• Assign a scribe. One person owns the pre-PM; collects timeline, impact, and draft factors; clear ownership prevents pre-PM stalling.
• Time-box the prep. Pre-PM prep bounded to a few hours, not a few weeks; supports timely PMs that meet the deadline.
• Linked artefacts. Slack threads, dashboards, deploy logs linked in the pre-PM; evidence-based PMs survive scrutiny.

Why this compounds

The checklist compounds across PMs. Each PM produces lessons that feed back into the checklist; pattern recognition emerges across PMs; PM completion rates climb as the work shrinks.

• Faster PMs. PMs become faster as the checklist matures; less rework, more productive meeting time.
• Higher quality PMs. Output stays consistent; action items concrete, root causes documented, real learning produced.
• Cross-PM pattern recognition. Comparable PMs surface trends; recurring root causes and recurring action items become visible.
• Cultural maturity. Team treats PMs as work, not formality; the discipline becomes part of engineering identity rather than imposed process.

The incident postmortem checklist is one of those operational disciplines that pays off across years. Nova AI Ops integrates with incident data, surfaces patterns across PMs, and supports the team's learning discipline.