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.
Related Insights
To de-risk innovation, teams must avoid the trap of building easy foundational parts (the "pedestal") first. Drawing on Alphabet X's model, they should instead tackle the hardest, most uncertain challenge (the "monkey"). If the core problem is unsolvable, the pedestal is worthless.
Instead of defaulting to skepticism and looking for reasons why something won't work, the most productive starting point is to imagine how big and impactful a new idea could become. After exploring the optimistic case, you can then systematically address and mitigate the risks.
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.
Effective product development starts with internal alignment. Using exercises like Instagram's "Stories Mad Libs" creates a shared, candid understanding of the product's current state. This "organizational therapy" is a prerequisite for overcoming team biases and conducting successful user research.
To get buy-in from skeptical, business-focused stakeholders, avoid jargon about user needs. Instead, frame discovery as a method to protect the company's investment in the product team, ensuring you don't build things nobody uses and burn money. This aligns product work with financial prudence.
When handed a specific solution to build, don't just execute. Reverse-engineer the intended customer behavior and outcome. This creates an opportunity to define better success metrics, pressure-test the underlying problem, and potentially propose more effective solutions in the future.
AI models tend to be overly optimistic. To get a balanced market analysis, explicitly instruct AI research tools like Perplexity to act as a "devil's advocate." This helps uncover risks, challenge assumptions, and makes it easier for product managers to say "no" to weak ideas quickly.
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 immediately building, engage AI in a Socratic dialogue. Set rules like "ask one question at a time" and "probe assumptions." This structured conversation clarifies the problem and user scenarios, essentially replacing initial team brainstorming sessions and creating a better final prompt for prototyping tools.
The misconception that discovery slows down delivery is dangerous. Like stretching before a race prevents injury, proper, time-boxed discovery prevents building the wrong thing. This avoids costly code rewrites and iterative launches that miss the mark, ultimately speeding up the delivery of a successful product.