We scan new podcasts and send you the top 5 insights daily.
Jeff Patton says many teams 'story map' by taking a solution they already have in mind and breaking the product into smaller pieces. That is feature decomposition, not a story map. A real story map starts with what a user does; without that narrative, the map does not help you understand outcomes.
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.
Asking users for solutions yields incremental ideas like "faster horses." Instead, ask them to tell detailed stories about their workflow. This narrative approach uncovers the true context, pain points, and decision journeys that direct questions miss, leading to breakthrough insights about the actual problem to be solved.
Jumping into solutions too early during ideation biases product teams away from understanding the customer's true challenges. Teams should spend deliberate time framing customer problems using structured toolkits before committing to prototypes or technical execution.
When a stakeholder proposes a specific feature (a "form factor"), don't debate it directly. Instead, "ladder up" the conversation by asking a series of "why" questions to uncover the user behavior, desired outcome, and ultimately, the root problem being solved.
Don't present a simple list of features. Instead, group deliverables into a compelling story with clear objectives and initiatives (e.g., a 3x3 grid for "Automation, Integration, Measurement"). This narrative provides crucial context, making it easier for engineering, sales, and leadership to understand the 'why' behind the work.
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.
Product leaders should reframe roadmaps from a list of features to a series of barriers they are removing for customers. This shifts focus to high-leverage outcomes like reducing complexity, enabling zero-handholding onboarding, and accelerating time-to-value.
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.
Teams often waste months iterating on marketing concepts (the 'headline') without a core story. By first developing a full narrative—user problem, root cause, solution, benefit—teams create stronger concepts from the start, consistently achieving higher test scores and saving 12-18 months of development time.
Most journey maps start when a customer discovers your brand. A better approach begins earlier in the "struggle phase," when the prospect is dealing with the problem your solution solves. Understanding this pre-awareness context is critical for creating resonant marketing.