Start with structure, then replace every placeholder with information that is true, relevant, and natural for your context. These templates are intentionally skeletal so your final writing does not sound mass-produced.
A strong postmortem compares outcomes with original goals and expectations, uses timelines and evidence instead of memory alone, distinguishes contributing factors from convenient stories, captures both successes and failures, and converts important lessons into specific actions or reusable practices.
Project postmortem Project/goals: [x] Success criteria: [x] Outcome vs plan: [x] Timeline/major changes: [x] What went well: [evidence + enabling condition] What did not: [evidence + contributing condition] Lessons: [repeat/change] Actions: [owner + date + success check] Open questions: [x] Reusable artifacts/process changes: [x]
Lessons-learned table Observation | evidence | why it mattered | contributing condition | repeat/change | action | owner | due date
Blameless issue analysis Event/outcome: [x] Expected behavior: [x] Observed behavior: [x] Conditions that contributed: [x] Signals available at the time: [x] Safeguards that worked: [x] Improvement action: [x]
Postmortem quality check Baseline visible? [ ] Evidence beats memory? [ ] Successes captured? [ ] No personal blame? [ ] Uncertainty labeled? [ ] Actions owned? [ ] Lessons stored for reuse? [ ]