When pitching new marketing initiatives, supplement ROI projections with research demonstrating a clear audience need for the content. Framing the project as a valuable service to the customer, rather than just another marketing tactic, is a more powerful way to gain internal support.

Unlike traditional product management that relies on existing user data, building next-generation AI products often lacks historical data. In this ambiguous environment, the ability to craft a compelling narrative becomes more critical for gaining buy-in and momentum than purely data-driven analysis.

Many leaders mistake a chronological summary or a problem-solution statement for a story. True storytelling, like that used by Alibaba's Jack Ma, requires a narrative with characters, conflict, and resolution. This structure is what truly engages stakeholders and persuades them to join a cause.

Tailor your innovation story to your company's risk culture. For risk-averse organizations, proactively acknowledging potential problems, barriers, and what could go wrong is more persuasive. For risk-tolerant cultures like Amazon's, leading with opportunity and the potential for learning is more effective.

Instead of waiting for features to build a story, develop the compelling narrative the market needs to hear first. This story then guides the launch strategy and influences the roadmap, with product functionality serving as supporting proof points, not the centerpiece.

Structure your final presentation by calling out specific problems you learned from individual contributors by name. Then, immediately pivot to show how solving their problem directly contributes to the high-level business objective owned by the executive decision-maker. This makes every stakeholder feel heard and demonstrates their strategic value.

Creating products customers love is only half the battle. Product leaders must also demonstrate and clearly communicate the product's business impact. This ability to speak to financial outcomes is crucial for getting project approval and necessary budget.

At Alphabet's X, the primary role of storytelling isn't marketing but creating an 'architecture of understanding.' A compelling narrative must lay out a plausible, step-by-step path to the goal. This provides a clear hypothesis and a set of milestones that the team can then systematically test and disprove.

To keep non-technical stakeholders engaged, don't show code or API responses. Instead, have team members role-play a customer scenario (e.g., a customer service call) to demonstrate the 'before' and 'after' impact of a new platform service. This makes abstract technical progress tangible and exciting.