PM Evolution Over Years

Format changes.

Overview

Postmortem evolution recognises that the postmortem template should change as the team learns what produces real follow-through and what produces theatre. Sections get added (customer impact, contributing factors, action-item ownership), sections get removed (the ones nobody fills out usefully), per-team variations emerge for the workload they actually face, and the team reads peer-company postmortems to import good ideas. Rigid template adherence kills learning; deliberate evolution preserves it.

• Format changes. Per-year template iteration; the postmortem doc matures with the team.
• New sections added. Customer impact quantification, contributing-factor analysis, action-item ownership all became defaults over years of practice.
• Sections removed. Sections that did not produce value get cut; the template stays focused on what actually drives follow-through.
• Per-team variation plus industry exemplars. Each team adapts the template to its workload; reading peer-company postmortems imports good ideas.

The approach

The practical approach is to run an annual template review (what produced action, what produced theatre), peer-review template changes before adoption, document the rationale for each change so future evolution has context, deliberately consume peer-company postmortems for new ideas, and let teams adapt the template to their workload while preserving cross-team consistency on the load-bearing sections.

• Per-year template review. Annual review against follow-through data; the template evolves based on what produced action.
• Peer review changes. Template changes reviewed before adoption; preserves quality and surfaces objections.
• Documented rationale. Per-change the rationale committed; future evolution has context for why current sections exist.
• Industry exemplars plus per-team adaptation. Read peer-company postmortems; per-team adaptation respects workload differences while preserving cross-team consistency.

Why this compounds

Postmortem evolution discipline compounds across years. Each iteration produces a better template; each better template produces better postmortems; each better postmortem produces better follow-through. After a few years, the team has a postmortem practice that materially improves reliability rather than producing well-formatted documents nobody reads.

• Postmortem quality. Iterative template produces real improvement; the doc matures with the team’s incident maturity.
• Team adoption. Per-team adaptation produces real adoption; teams use the template because it serves them rather than because it is mandated.
• Cross-team learning. Industry exemplars produce real learning; good ideas import faster than the team would derive them.
• Institutional knowledge. Each iteration teaches what produces action versus theatre; the team learns its own postmortem-to-action conversion rate.

Postmortem evolution discipline is an operational discipline that pays off across years. Nova AI Ops integrates with incident telemetry, surfaces template patterns, and supports the team’s incident-process discipline.