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.

Contrary to 'positive thinking,' this method involves identifying everything that could go wrong for each step required to succeed. By proactively creating solutions for these risks, you significantly increase your overall probability of success and de-risk your goals.

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.

Categorize risks to prioritize action. 'Tigers' are critical threats that will kill the project. 'Paper Tigers' are perceived risks that are actually under control, requiring only reassurance. 'Elephants' are the unspoken, uncomfortable truths that need to be surfaced for discussion.

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.

Instead of waiting for a postmortem after failing, conduct a 'premortem' at the start. Proactively contemplating the specific obstacles that might prevent you from achieving your goals is a critical first step. This pessimistic-sounding exercise allows you to identify barriers like impulsivity or laziness and design solutions for them.

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.

Hormozi's team didn't just plan for success; they systematically identified every potential point of failure ("choke points") from ad platforms to payment processors. By asking "how would we fail?" and creating contingencies for each scenario, they proactively managed risk for a complex, high-stakes event.