Postmortem as Org Learning
Compounding knowledge.
Overview
Postmortems carry value beyond the team that wrote them. Treated as the substrate for organisational learning, the postmortem library compounds into institutional knowledge that survives engineer turnover and outlasts any one team.
- Compounding knowledge. Each postmortem preserves a lesson and a fix. The aggregate is the team’s incident memory.
- Searchable library. Postmortems in a central searchable system. Pattern-matching the next incident becomes possible.
- Cross-team sharing. Postmortems readable across teams. Adjacent teams learn from each other’s incidents.
- Trend analysis plus onboarding. Cross-postmortem trends drive investment; new engineers read recent postmortems as part of onboarding.
The approach
Three habits make postmortems compound: a searchable library that everyone can reach, cross-team sharing as the default, and reading postmortems as part of onboarding.
- Searchable library. Notion, Confluence, or a custom wiki with full-text search. Tagged by service, severity, and root-cause class.
- Cross-team visibility. Postmortems are public to the engineering org by default. Privacy is the exception, not the rule.
- Onboarding reading list. New on-call engineers read the last 10 postmortems for their service before taking the rotation.
- Quarterly trend analysis. Walk the postmortem set each quarter. Recurring root-cause classes drive engineering investment.
Why this compounds
The library doubles as institutional memory. Engineers leave; the postmortems stay; the next on-call inherits the lessons rather than relearning them.
- Organisational learning. The library produces real institutional knowledge that survives engineer turnover.
- Faster onboarding. New engineers benefit from accumulated postmortems on day one. Ramp time shortens visibly.
- Cross-team learning. Adjacent teams pattern-match incidents from another service’s history.
- Year-one investment, year-two habit. The first library is heavy lift. By year two the cadence runs itself and new postmortems automatically join the corpus.