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.

The impulse to "add AI" is common, but workshops exploring it must first ask "where do we have good, clean data?". Without a solid data foundation, AI ideation is futile. The first innovation step might be improving data collection, not implementing machine learning.

The impulse to make all historical data "AI-ready" is a trap that can take years and millions of dollars for little immediate return. A more effective approach is to identify key strategic business goals, determine the specific data needed, and focus data preparation efforts there to achieve faster impact and quick wins.

When pipeline slips, leaders default to launching more experiments and adopting new tools. This isn't strategic; it's a panicked reaction stemming from an outdated data model that can't diagnose the real problem. Leaders are taught that the solution is to 'do more,' which adds noise to an already chaotic system.

Prevent endless cycles of analysis by defining decision-making boundaries upfront. Before work begins, the leadership team must agree on what specific data or inputs are necessary to make a call. This avoids the "fetch another rock" scenario where analysis is requested with no clear endpoint.

To avoid getting lost in data, PMs should first define the decision they need to make (e.g., improve ROI, increase usability). This goal then dictates which data to gather and from whom. Patterns should be grouped by desired user outcomes, not feature requests, creating a more strategic path to delivery.

The most critical action isn't technical; it's an act of vulnerability. Leaders must stop pretending and tell their CEO/CRO they lack the data architecture to be a responsible leader, framing it as a business-critical problem. This candor is the true catalyst for change.

Focus on the root cause (the "first-order issue") rather than symptoms or a long to-do list. Solving this core problem, like fixing website technology instead of cutting content, often resolves multiple downstream issues simultaneously.

While research is vital, there's a point of diminishing returns. Over-researching can lead to 'analysis paralysis' by revealing too many edge cases and divergent needs, ultimately stalling the momentum required to build and launch a new product.