post mortem
[/ˌpəʊst ˈmɔː.tem/]
AUTHOR: Tiziano Gasparet
Definition
Post-mortem is the systematic analysis of a concluded event (lost game, bug, imperfect product) to extract applicable lessons. It is not self-criticism: it is causal mapping of variables that led to the result.
Technical Connection
Why does the Monolith archive this? Because post-mortem is the engine of continuous learning. Without analysis → error repeats. With archived analysis → error becomes protocol.
Practical Application
- Time: analysis within 24h of event, fresh memory
- Structure: Origin → Connection → Challenge → Peace of Mind → Technical Note
- Archiving: Markdown in Monolith, tags for future search
Control Triggers
- Repeated error → missing or incomplete post-mortem
- Analysis without action → decorative post-mortem, not operational
- Archived but unconsulted post-mortem → ineffective retrieval system
Technical Note:
- Target analysis time: within 24h of event
- Tool: Markdown template, search tags, connection to dictionary terms
- Warning: same error 3 times = ineffective post-mortem, review protocol
- Connections: plasticity, technical-debt, fermentation (metaphorical)