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.

A simple diagnostic for a missing strategy is to ask "why" multiple times about a task. If asking "why" about an objective (the first answer) results in a blank stare, it's a strong signal the strategic connection is missing. This "laddering" technique exposes gaps in the decision stack.

The common advice to ask 'why' five times can reinforce an incorrect initial framing of a problem, leading you to optimize the wrong thing. A more powerful approach is to first question the frame itself by asking, 'Is this the right thing to focus on?' before diving into causes.

Structure discovery calls by mapping problems across four levels: Situation (what they do), Operational Problem (champion's complaint), Executive Problem (VP's concern), and Business Impact (C-level metric). This framework provides a logical path for your questions, moving from tactical to strategic issues.

Teams often get stuck listing obstacles. To break this cycle, ask, "What would need to be true for this to happen?" This imaginative prompt bypasses the immediate "no" and shifts the group's focus from roadblocks to possibilities, unlocking creative solutions they would have otherwise dismissed.

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.

At the end of an expert call, ask the expert to consider a scenario where your agreed-upon conclusions are incorrect. This prompts them to reveal second and third-order risks and blind spots that may not have surfaced during the main discussion.

Instead of accepting the first answer to a problem, this framework from Toyota's founder involves asking 'why' five consecutive times. This process drills down past surface-level symptoms to uncover the fundamental issue, a crucial skill in a world of information overload.

Teams often waste time trying to find a single "hero" solution for a complex system failure. A more effective strategy is to first isolate *where* in the system the problem exists. This narrowing approach is a faster path to a root cause than jumping between different global hypotheses.