The fundamental elements of any compelling story—a character, a conflict, and a resolution—map directly to product management. The user is the character, their problem is the conflict, and your product provides the resolution. This simplifies story creation.

Linear, chronological stories ("this happened, and then this happened") are boring. To create dynamism and energy, structure a narrative around conflict and consequence. Using connecting words like "but" and "therefore" creates an engaging up-and-down path that keeps the listener hooked.

Tailor your message by understanding what motivates your audience. Technical teams are driven to solve problems, while sales and marketing teams are excited by new opportunities. The core idea can be identical, but the framing determines its reception and gets you more engagement.

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.

Technologists often fail to get project approval by focusing on specs and data. A successful pitch requires a "narrative algorithm" that addresses five key drivers: empathy, engagement, alignment, evidence, and impact. This framework translates technical achievements into a compelling business story for leadership.

Instead of a feature-focused presentation, close deals by first articulating the customer's problem, then sharing a relatable story of solving it for a similar company, and only then presenting the proposal. This sequence builds trust and makes the solution self-evident.

Instead of overwhelming people with logical reasons to change, persuade them by helping them envision a new version of themselves. Use stories and framing like "Imagine what it would be like if..." to invite them to try on the identity associated with the desired action.

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.

Every compelling story needs conflict, which requires an enemy. Companies can define their enemy in one of three ways: direct competitors (e.g., other vodkas), competing approaches (e.g., cycling vs. the tube), or beliefs you stand against (e.g., humans are terrible drivers). This ABC framework (Approaches, Beliefs, Competitors) simplifies narrative creation.