pre-mortem-kill-criteria
Pre-Mortems with Kill Criteria
Overview
An enhancement to the standard pre-mortem that moves beyond simply imagining failure to establishing pre-committed actions based on specific negative signals.
Core principle: Thinking about failure isn't enough; you must commit to actions BEFORE you see the signals.
The Process
┌─────────────────────────────────────────────────────────────────┐
│ 1. MENTAL TIME TRAVEL │
│ Fast forward: Imagine the project has FAILED │
├─────────────────────────────────────────────────────────────────┤
│ 2. SIGNAL IDENTIFICATION │
│ "What early clues indicated the failure?" │
│ List specific, observable signals │
├─────────────────────────────────────────────────────────────────┤
│ 3. DEFINE KILL CRITERIA │
│ Convert clues into measurable thresholds │
│ Example: "CPA > $50" or "Customer won't demo" │
├─────────────────────────────────────────────────────────────────┤
│ 4. PRE-COMMITMENT │
│ Establish rule: "If [Criteria] occurs, we [Kill/Pivot]" │
│ Write it down and share with team │
├─────────────────────────────────────────────────────────────────┤
│ 5. ACTIVE MONITORING │
│ Scan for criteria during execution │
│ Act immediately when triggered │
└─────────────────────────────────────────────────────────────────┘
Key Principles
| Principle | Description |
|---|---|
| Pre-commit | Lock in actions before rationalization kicks in |
| Signal focus | Identify correlates of failure, not just the failure itself |
| Prospective waste | Think about future waste, not sunk cost |
| Automatic triggers | When criteria hit, action is mandatory |
Common Mistakes
- Doing a pre-mortem but not changing the plan
- Identifying risks without setting a specific stop trigger
- Rationalizing signals when they appear ("it's different this time")
Source: Annie Duke (First Round Capital, WSOP Champion) via Lenny's Podcast
More from coowoolf/insighthunt-skills
gardening-mindset
Use when dealing with ecosystems, network effects, or high-uncertainty environments where the right answer cannot be known in advance, when rigid planning consumes more value than it creates
45gamification-triad
Use when designing retention mechanisms, habit loops, or auditing why users drop off despite engaging with core features, to structure gamification beyond superficial badges
44three-layer-agent-stack
Use when building AI-powered products or agents, when raw model intelligence isn't enough to solve user problems, or when designing the architecture for agentic workflows
15minimum lovable product (mlp)
In an era where AI lowers the cost of building software, viability is obsolete. The differentiator is joy and emotional connection. Prioritize "Wow" over "Aha"—brand is product interaction.
14curiosity-loops
Use when facing a significant decision (career pivot, product direction, technical choice) and feeling stuck or indecisive, when seeking contextual advice rather than generic recommendations
13strategic-narrative
Use when traditional problem/solution pitches fail to differentiate, when teams are misaligned around messaging, or when entering Series B/scaling phases where founder-led sales no longer scale
12