premortem

To run a premortem analysis, provide your plan details, audience, success criteria, and context. The session frames the decision, generates failure reasons with likelihood and impact scores, runs deep-dives, and outputs a synthesized HTML report and markdown transcript.

A premortem is a risk analysis technique where teams reason about a plan as if it has already failed. Use a premortem for launches, hires, pricing changes, or pivots—any decision where the cost of being wrong is high—to surface hidden assumptions and failure modes before committing resources.

To conduct deep-dives into failure causes, the premortem session runs parallel analyses for each generated failure reason. This surfaces underlying assumptions, identifies early warning signs, and develops cheap mitigations, ultimately synthesizing a prioritized plan with a pre-launch checklist.

Yes, you can use a premortem for pricing changes, hires, launches, and pivots. It requires clear plan details and success criteria to set the time horizon, generate failure causes, and deliver a committed action with a specific day to ensure team alignment.

A premortem generates an HTML visual report and a full markdown transcript saved in your workspace. These artifacts include a prioritized plan highlighting the most likely and dangerous failures, a revised plan, a pre-launch checklist, and a committed action tracking refusals for learning.

No, a premortem requires clear plan details, audience, success criteria, and contextual information to function properly. Without these inputs, the session cannot accurately set the time horizon, generate meaningful failure causes, or deliver a synthesized premortem report.