Postmortems create knowledge, but rarely create memory.
Postmortems often capture what happened and what was learned, but the lesson may not become reusable unless it is promoted into owned systems and future workflows.
Postmortems often capture what happened and what was learned, but the lesson may not become reusable unless it is promoted into owned systems and future workflows.
Postmortems can create knowledge by recording what happened, what was learned, and what should change. They do not automatically create engineering memory.
Interpretation
The reusable lesson often remains trapped inside the postmortem artifact unless it is promoted into an owned place where future work will encounter it: tests, runbooks, repository guidance, workflow checks, models, or operational tooling.
Research Use
Use this evidence object when testing whether an organization preserves lessons in ways that improve later execution, rather than only preserving artifacts that explain past execution.