Postmortem Attendance Policy

Who attends postmortems matters. The policy that gets the right people without it becoming a meeting bloat.

Required

The required attendance list is small on purpose. People who were in the incident plus a senior tech lead who can commit the team to action items. More than four required attendees usually signals an unclear postmortem owner.

• Incident commander. Owns the timeline and decisions during the incident; owns the narrative in the postmortem.
• Scribe. Carried the live notes during the incident. Has the timestamps and context the IC needs to verify.
• On-call engineers. The responders who held keyboards during the incident. Carry the firsthand technical context that nobody else has.
• Senior tech lead. Can commit the team to action items without going back for approval. Without this attendee, the postmortem produces wishes rather than work.

Optional

The optional list is broad and the bar for in-room attendance is high. Async sharing of the published postmortem reaches the audience that does not need to be in the meeting.

• Adjacent teams. Dependency teams whose systems were involved. Useful when the incident crossed service boundaries.
• Product management. Useful when the incident had material customer impact and PM owns the customer-comms followup.
• Leadership. Per-incident judgement call. Sev-1 with public visibility usually warrants exec attendance; lower severities usually do not.
• Async share. The published doc reaches the rest of the org. Attendance is optional; reading is not.

Avoid

Two failure modes kill the discipline: bloating the meeting until it becomes ceremony, or skipping the postmortem when the team is busy. Both produce predictable consequences.

• Mandatory org-wide attendance. 30 people in the room is a status meeting, not a learning meeting. Keep it small or split into review and broadcast.
• Skipping the postmortem. Always-do rule. Async writeups are a valid alternative; skipping is not, regardless of how busy the team is.
• Published attendance list. Each postmortem records who attended. The list catches under-engagement before it becomes a pattern.
• Quarterly policy review. Audit the attendance pattern each quarter. Drift catches itself when the policy is reviewed regularly.