liveBook · Manning

Postmortem

Also called post-mortem

A postmortem is a retrospective analysis of an event or incident that examines what happened, its causes and effects, and lessons or actions for improvement.

How 5 Manning books explain it

Troubleshooting Java, Second Edition

A postmortem investigation is troubleshooting performed after an application has crashed and stopped running.

How it is used
Deploys troubleshooting after an application crash, particularly when a production service has stopped running.
How deep it goes
Defines the technique and identifies evidence sources, but defers detailed dump analysis and implementation procedures.
Examples
Uses production crashes, memory errors, large log files, and database-lock exceptions as investigative examples.
What you can do after
Diagnose crash causes by correlating logs, heap dumps, thread dumps, and other evidence collected around the failure.

Read how Troubleshooting Java, Second Edition explains postmortem →

Machine Learning System Design

A postmortem is a structured analysis of an incident and its causes, effects, and follow-up actions.

How it is used
Turns production failures into learning, corrective actions, and improved reliability.
How deep it goes
Defines retrospectives, postmortems, and proportional response, but stops short of prescribing a detailed investigation template.
Examples
Uses minor incidents requiring runbook updates and a major outage prompting a company-wide reliability initiative.
What you can do after
Practice proportional postincident learning and convert failures into appropriately sized follow-up actions.

Read how Machine Learning System Design explains postmortem →

The Art of Code

Postmortem analysis is the investigation of a completed incident to determine its causes, effects, and corrective actions.

How it is used
Uses logging to preserve actionable failures for later postmortem investigation.
How deep it goes
Distinguishes actionable failures from noise but does not describe a full investigation workflow.
Examples
Contrasts mistyped email addresses with repeated invalid login attempts that may indicate credential stuffing or password spraying.
What you can do after
Evaluate which caught failures merit logging by asking whether an abnormal event should be investigated.

Read how The Art of Code explains postmortem →

AI Model Evaluation

A postmortem is a blameless retrospective analysis of a production or evaluation incident that records what happened, why detection or validation failed, and what changes will follow.

How it is used
Uses blameless incident analysis to improve evaluation reliability and shorten the time between failure and detection.
How deep it goes
Defines four review questions, adds signal triangulation, and extends recovery through full re-validation and clearer communication.
Examples
Uses stale rubrics, drifted judge models, data-pipeline issues, model regressions, gold-standard datasets, and corrective one-pagers.
What you can do after
Diagnose evaluation incidents, document causes, re-run validation, communicate changes, and strengthen monitoring after recovery.

Read how AI Model Evaluation explains postmortem →

Think Like a CTO

A postmortem is a structured review conducted after an event to examine what happened, what went well, and what should improve.

How it is used
Reviews releases and incidents after completion to recognize successes, learn from failures, and examine preventable problems.
How deep it goes
Distinguishes planning failures from hindsight, checks leadership authorization, and recommends documenting events and addressing recurring issues.
Examples
Uses release completion, security breaches, data loss, payment-related service loss, and hardware failure as review cases.
What you can do after
Apply it by documenting an event, consulting the responsible person, and considering training or role changes when problems recur.

Read how Think Like a CTO explains postmortem →

Also covered in

What to know first

Related concepts

Questions about postmortem

What is postmortem?

A postmortem is a retrospective analysis of an event or incident that examines what happened, its causes and effects, and lessons or actions for improvement.

Which Manning books explain postmortem?

Troubleshooting Java, Second Edition, Machine Learning System Design, The Art of Code, AI Model Evaluation and Think Like a CTO.

What should I know before learning postmortem?

Manning books that teach postmortem usually introduce root cause, artificial intelligence, debugging and language model first.

What is the difference between postmortem and trust?

A postmortem is a retrospective analysis of an event or incident that examines what happened, its causes and effects, and lessons or actions for improvement. Trust is confidence that an entity or source is reliable and appropriate to rely on in a given context.

What kinds of postmortem are there?

Kinds of postmortem include blameless postmortem.

What is postmortem also called?

Postmortem is also called post-mortem.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.