
Explore Discover, the Knowledge Hub, playbooks, and the Operator Vault.
Glossary
A premortem is a prospective failure analysis: the team imagines that a project or decision has already failed, then generates plausible reasons why. It uses prospective hindsight to surface risks and flawed assumptions before commitment — unlike a postmortem, which analyzes failure after it has occurred.
Groups under commitment pressure suppress dissent. Premortems legitimize critique by changing the prompt from “will this work?” to “it’s eighteen months later and it failed — why?” That often reveals hidden dependencies, optimistic timelines, and unowned risks.
A premortem improves decision support; it does not guarantee success. Findings should alter the plan, kill weak bets, or create monitoring triggers — not become a ritual that ends in unchanged commitment.
Example (enterprise): Before green-lighting an agent rollout, a team runs a premortem that surfaces data-quality and escalation gaps. They delay launch until human-in-the-loop paths and evaluation metrics are funded — converting imagined failure modes into design requirements.
None linked yet.
No related resources yet.