We scan new podcasts and send you the top 5 insights daily.
Jack Dorsey wrote '140 Reasons Why Square Will Fail' before starting the company. This pre-mortem helped him identify failure modes and design the company to avoid them, similar to Charlie Munger's advice to know where you'll die so you don't go there.
During product discovery, Amazon teams ask, "What would be our worst possible news headline?" This pre-mortem practice forces the team to identify and confront potential weak points, blind spots, and negative outcomes upfront. It's a powerful tool for looking around corners and ensuring all bases are covered before committing to build.
Extend premortems beyond failure scenarios to consider overwhelming success. This reframes success as a potential failure if you're unprepared, helping teams proactively identify and plan for scaling risks and organizational readiness before they become critical issues.
A pre-mortem asks a team to imagine their project has already failed spectacularly. By explaining the hypothetical failure, they uncover potential risks and can build mitigation strategies, effectively using the power of hindsight bias in advance.
Instead of focusing on the happy path, start design by asking, 'What is the absolute worst thing that could happen to a user?' This 'disaster thinking' approach forces you to work backward from the highest stakes, revealing critical failure points and ensuring you build a more resilient and safe service.
Disagreeing with Peter Thiel, Josh Wolf argues that studying people who made willful mistakes is more valuable than studying success stories. Analyzing failures provides a clear catalog of what to avoid, offering a more practical and robust learning framework based on inversion.
A pre-mortem's effectiveness hinges on its framing. Instead of asking "what could go wrong?", you must state definitively, "The plan has failed." This "prospective hindsight" shifts participants from speculative critique to a forensic analysis of causes, revealing risks they wouldn't otherwise voice.
The 'fake press release' is a useful vision-setting tool, but a 'pre-mortem' is more tactical. It involves writing out two scenarios before a project starts: one detailing exactly *why* it succeeded (e.g., team structure, metrics alignment) and another detailing *why* it failed. This forces a proactive discussion of process and risks, not just the desired outcome.
Before embarking on a high-stakes journey, you must be curious about everything that could go wrong. Conduct a 'premortem' by imagining specific failure scenarios in advance ('what if this breaks?'). This allows you to methodically identify potential problems and develop contingency plans before taking the leap.
Before starting a project, ask the team to imagine it has failed and write a story explaining why. This exercise in 'time travel' bypasses optimism bias and surfaces critical operational risks, resource gaps, and flawed assumptions that would otherwise be missed until it's too late.
Instead of only focusing on what to do, effective teams collaboratively create a charter of behaviors and decisions they will actively avoid. This "not-to-do" list, based on previous project roadblocks, serves as a powerful tool to prevent repeating costly mistakes.