When facing ambiguity, the best strategy is not to wait for perfect information but to engage in "sense-making." This involves taking small, strategic actions, gathering data from them, and progressively building an understanding of the situation, rather than being paralyzed by analysis.

To break the cycle of solving the wrong problems, use the RCD method. First, 'Reflect' on unseen possibilities. Then, 'Connect' with outside advisors for an unbiased perspective. Finally, 'Decide' to act decisively ('Make an F-ing Decision') on the new information without getting stuck in analysis paralysis.

A discovery tree is a map that guides questioning from a simple situation (e.g., using spreadsheets) to operational problems, then to executive problems (e.g., compensation mistakes), and finally to critical business impact (e.g., retention risk). This ensures you uncover problems worth solving.

To start something new, you don't need the full roadmap. You only need to know three things: A (an honest assessment of your current situation), Z (your ultimate destination), and B (your very next step). Forget C through Y; focus on B and gain clarity through action.

When leaders provide unclear direction, use two simple questions to find the strategy. If given a tactic ("build an AI agent"), ask "Why?" to uncover the real goal. If given a goal ("make $10 million"), ask "How?" to reveal the intended approach.

Instead of waiting for a complete picture, courageous leaders take small, experimental actions to 'sense make' their way through ambiguity. This process, observed in emergency responders, involves acting, observing cues, and rapidly iterating. It is about learning by doing, not planning everything perfectly in advance.

In extreme uncertainty like a fire or nuclear incident, waiting for perfect information is impossible. Effective leaders take small, iterative actions to gather data and update their strategy in real-time. This approach of 'acting your way into knowing' is more effective than trying to know everything before acting.

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.

The key differentiator between a PM effectively managing ambiguity and one who is simply unprepared is process. The former may not have an answer, but can articulate their plan to get one (e.g., "here's the hypothesis I'm testing"). The latter is just lost.