Book summary “Product Roadmaps Relaunched”: summary

Introduction

A product roadmap must be a strategic communication tool centered on customer outcomes rather than a rigid schedule of unvalidated features.

You likely struggle with traditional roadmaps that rely on fixed dates and long lists of features. These artifacts quickly become obsolete in agile environments, leaving you with broken promises and frustrated stakeholders.

C. Todd Lombardo shows you how to relaunch your roadmap so it communicates intent and direction. The book guides you through gathering inputs, defining a clear strategy, and uncovering real customer needs. You will learn how to prioritize initiatives scientifically and secure cross-functional buy-in.

How do you transition from a feature release plan to an outcome-driven strategy? How do you say no to stakeholders without losing their support? How do you keep your roadmap flexible yet actionable?

1. Relaunching Roadmaps and Components

Traditional roadmaps fail in agile environments because they rely on rigid feature lists and dates that quickly become obsolete. A relaunch turns the roadmap into a strategic communication tool that outlines how you intend to achieve your product vision.

A product roadmap is not a fixed project plan or release schedule, but a strategic communication tool that outlines how a team intends to achieve its product vision and deliver value.

Matt Poepsel from The Predictive Index notes that treating roadmaps as rigid commitments rather than intentions leads to failure when business circumstances change. You must shift away from waterfall release plans that commit to unvalidated features far in advance.

Focusing on Value

Product teams should commit to delivering outcomes that solve customer problems rather than mere output like feature delivery dates. John Mansour notes that software programs often present feature release schedules as roadmaps, whereas a roadmap should communicate what customers will accomplish and why those goals matter.

To build a resilient roadmapping process, you should:

• put the organization's plans in a strategic context;
• focus on delivering value to customers and the organization;
• embrace learning as part of a successful product development process;
• rally the organization around a single set of priorities;
• get customers excited about the product's direction.

Roadmap Components

An effective product roadmap requires specific primary components to tell a cohesive story of vision, progress measurement, and sequencing without relying on rigid dates. The hypothetical Wombat Garden Hose Co. roadmap illustrates how company vision leads to customer problem themes, which are then organized into broad timeframes.

Secondary roadmap components and complementary information should be used selectively to satisfy specific stakeholder concerns without cluttering the strategic message.

2. Gathering Inputs

Failing to study the business landscape leaves you operating on faulty assumptions. An explorer using an incomplete map starts a journey with missing information and high risk of failure.

You must study your business ecosystem, understand product life-cycle phases, and build deep customer empathy before constructing a roadmap.

Products move through distinct phases that dictate the focus of the roadmap. New Product Phase involves high uncertainty and rapid prototyping. Growth Phase focuses on scaling and getting the product to as many users as possible. Product Expansion Phase introduces fresh functionality linked to core products. Harvesting Phase maintains cash cow products with continuous improvements. End-of-Life Phase uses strategic planning to sunset a product.

Google generated 75 billion dollars in 2015 largely driven by Google AdWords, exemplifying the harvesting life-cycle stage. When R. Colin Kennedy worked as a Product Manager at Sonos, the yearly objective focused purely on maximizing speaker installations rather than revenue or lifetime value.

Tools like Alexander Osterwalder's Business Model Canvas for existing businesses and Ash Maurya's Lean Canvas for startups help you strategically evaluate pillars like customer segments and revenue models.

To build these foundational business frameworks, you must:

• identify the Problem and solution;
• define the Value proposition;
• determine the Unfair advantage;
• list Key metrics;
• segment Customer segments;
• establish Distribution channels;
• calculate Costs;
• outline the Revenue model;
• identify Key partners;
• determine Key resources.

Customer Empathy and Stakeholder Collaboration

Every roadmap item must address a verified customer need. You must differentiate between user roles, user types, and buyer roles while using personas to capture softer characteristics. Steve Blank's Customer Development Model emphasizes customer discovery and validation to ensure products solve real problems.

On Lynda.com, a student acts as both end user and buyer, while professional or social personas help uncover nuanced educational needs.

A product core consisting of product managers, designers, and engineers must collaborate with a wider ring of stakeholders including executives, sales, marketing, support, and finance. Involving these groups early ensures that various internal perspectives are merged into a unified Voice of the Customer and secures organizational buy-in. Jackie Bavaro at Asana describes how customer-facing teams create top-ten lists that are merged into an overall prioritized Voice of the Customer list.

To gather proper inputs before roadmapping, you should:

• identify who your customers are and understand their jobs, wants, and needs;
• differentiate between user roles, user types, and buyer roles;
• utilize personas to capture softer characteristics and build empathy;
• get out of the building to interact directly with customers;
• identify all key stakeholders and the roles they play;
• gather top-10 lists from customer-facing teams to form a unified Voice of the Customer;
• engage stakeholders early before roadmap items become concrete to gather input.

3. Establishing Product Vision and Strategy

A mission statement defines an organization's current intent and purpose, serving as the driving force behind realizing its vision. A well-written mission statement balances realism and optimism. It clarifies business intentions and reflects what the organization does for others, typically customers rather than shareholders.

Connecting your organizational mission, product vision, values, and objectives and key results ensures that every roadmap item ties back to measurable outcomes.

Coca-Cola's mission is to refresh the world, inspire moments of optimism and happiness, and create value and make a difference. Starbucks's mission is to inspire and nurture the human spirit one person, one cup, and one neighborhood at a time.

When formulating your mission, evaluate these aspects:

• Value: What value does your mission bring to the world?
• Inspiration: How does your mission inspire your team to make the vision a reality?
• Plausibility: Is your mission realistic and achievable?
• Specificity: Is your mission specific to your business, industry, and/or sector?

Vision and Horizons

A product vision paints a picture of a future outcome and clarifies why a product exists and what its success means to the world and the organization. The vision acts as the destination of the roadmap. You can formulate it using structured value proposition templates or elevator pitch templates.

Capella University developed a product vision of delivering the entire university experience successfully over the web, which included academic spaces, administrative functionality, support resources, and a private network. This initiative was initially conceived in 2008, leading to the launch of Capella's first release of the online experience in June of 2009.

You can construct a vision using these components:

• For: [target customer]
• Who: [target customer's needs]
• The: [product name]
• Is a: [product category]
• That: [product benefit/reason to buy]
• Unlike: [competitors]
• Our product: [differentiation]
• Supports our: [objective(s)]

Organizational values act as a compass to guide behaviors, shape company culture, and help determine what is right or wrong for the business. While a vision provides the ultimate destination and a mission indicates the direction, values govern how people behave and make decisions when no one was watching. InVision App lists values such as Question Assumptions, Think Deeply, Iterate as a Lifestyle, Details, Details, Design is Everywhere, and Integrity.

Objectives and Key Results connect high-level vision to the roadmap by pairing qualitative goals with quantitative measures of progress. The OKR framework directs product development efforts toward measurable outcomes rather than specific outputs, keeping the number of objectives manageable to maintain focus. Contactually defined business objectives for increasing sales leads, average sale price, trial conversion, and customer retention to ensure financial viability.

Roadmaps must prioritize outcomes over outputs to ensure delivered features tie back to the actual reasons and desired results. Outputs are the physical or virtual items produced, whereas outcomes represent the difference those items make. Focusing purely on output risks creating a feature factory that releases features without verifying whether they achieved the desired results.

SpaceX illustrated strategy using spacecraft designs and Mars landing videos to show intended deliverables while maintaining focus on the core outcome of colonizing Mars. Elon Musk announced his roadmap to colonize Mars in September 2016, noting the previous estimated cost per person to go to Mars was $10 billion and establishing a target cost equivalent to a US house of $200,000 to make emigration market-viable.

A roadmap is a sequence of stakeholder priorities rather than a rigid release plan with strict delivery dates. Jim Garretson of Candescent Health notes that a roadmap must tell the product story without needing to get the days right.

To apply these strategy principles effectively, you should:

• tie everything on the roadmap to at least one objective;
• stick to a manageable number of objectives, keeping fewer than five most effective;
• focus on outcomes, not output;
• use loose timeframes like Now, Next, and Later instead of specific calendar dates on the roadmap;
• reserve rigorous scope definition, capacity planning, and specific deadlines for release and project plans.

4. Uncovering Customer Needs Through Themes

Traditional roadmaps often list rigid features before anyone understands the underlying problem. Organizing your roadmap around high-level customer problems using themes, user journey maps, and job stories prevents premature commitment to specific solutions.

Organizing your roadmap around high-level customer problems using themes, user journey maps, and job stories prevents premature commitment to specific solutions.

Themes and Journey Maps

A theme represents a high-level customer need or problem, while a subtheme provides more granularity. You can break a software theme of addressing key usability issues into subthemes like pagination, menu navigation, and save status.

User journey maps and experience maps track every step a user takes to solve a problem. This mapping uncovers pain points that form the basis for roadmap themes. Journey mapping helps you understand the sequence of actions a user performs, providing context to evaluate whether incoming feature requests solve critical paths or are merely nice to have.

Lyft addressed urban transportation problems by understanding incremental steps in an urban traveler's experience, starting with the need to go from point A to point B.

To manage this discovery work effectively, you should:

• map out the exact steps a user takes from realizing a problem exists to solving it;
• cross-reference incoming feature requests against the user journey map to test their relevance;
• regularly revisit journey maps to keep them up-to-date as human behaviors evolve.

Opportunity-Solution Trees and Job Stories

Opportunity-Solution Trees separate problems and needs from proposed solutions while maintaining a logical hierarchy tied to desired business outcomes. This framework prevents you from becoming overwhelmed by organizing objectives at the top, customer opportunities or themes in the middle, and solutions at the bottom. Teresa Torres developed opportunity-solution trees to help teams structure decisions and narrow testing efforts to one problem at a time.

User stories, job stories, and theme statement formulas help tease out the underlying motivations and context behind customer needs. Slack structures its public platform roadmap around major themes like app discovery, interactivity, and developer experience, tagging items to communicate priorities.

By framing needs around situations, motivations, and desired results using the jobs-to-be-done framework, you avoid building solutions that do not match real customer requirements.

5. Deepening Your Roadmap

Secondary components add detail and clarity to a theme-based roadmap, helping stakeholders understand context and increasing execution speed. While a roadmap remains valuable without them, features, stage of development, confidence scores, target customers, and product areas help stakeholders comprehend details quickly. This approach fosters buy-in and alignment while reducing time spent explaining the roadmap.

Secondary components such as features, stages of development, and explicit confidence scores add clarity and increase execution speed without cluttering the strategic message.

Buffer published its public product roadmap on Trello, displaying specific feature-level deliverables such as Pause Button and allowing customer voting.

You must examine your initiatives to determine what supporting information is required:

• Ask if you understand the need and possible solutions well enough to feel confident in a particular solution.
• Check for validated solutions from previous release plans that were not completed and need to be carried over.
• Identify any validated infrastructure needs.
• Identify mandates from decision-making stakeholders that must be addressed.
• Assess the likelihood that the solution will be changed, postponed, or dropped from the schedule.

Secondary Components and Stages

Tagging roadmap items with their stage of development clarifies status and distinguishes between broad themes and concrete features. Using recognizable development stages helps teams and stakeholders understand the maturity of each initiative. Items still being explored act as themes, whereas items chosen and heading to release act as features.

Evan and C. Todd worked with Spotify's product team in early 2017, where a lead product manager tagged roadmap items as think it, ship it, or tweak it.

Communicating Confidence

Adding explicit confidence percentages or visual indicators to roadmap timeframes and items reflects the inherent uncertainty of long-term planning. Because no one can predict the future, you should avoid claiming 100 percent confidence. Adding confidence scores to columns or individual items manages stakeholder expectations, and separation lines can segregate committed work from aspirational items.

Predictive Index uses a decreasing gradient bar on its roadmap to demonstrate that certainty drops as timeframes become more distant.

6. Prioritizing with Science

You must avoid gut-feeling prioritization and apply rigorous frameworks like the critical path, Kano model, desirability-feasibility-viability, and ROI scorecards to manage opportunity cost.

Resources are limited, and working on unstrategic, parallel tasks creates hidden carrying costs across retesting, documentation, training, and support. Furthermore, software regression testing matrices grow exponentially with each added feature, severely degrading team focus. For 5 features, the test matrix size is 31, while 10 features produce a size of 1,023, and 11 features jump to 2,047.

Bruce McCarthy convinced a colleague named Brenda to drop a cheap free-demo marketing idea that conflicted with the company's new strategy to move up-market, which eventually doubled revenue.

Opportunity Cost and Anti-Patterns

Relying on executive gut feelings, analyst trends, customer popularity requests, short-term sales demands, or competitor feature wars leads to unfocused products. Outsourcing product strategy to external parties or single departments strips the product of a unified vision. Customer requests often reflect symptoms rather than underlying needs, and sales-driven roadmaps turn the company into a custom development shop.

Carol Meyers, CMO of Rapid7, noted that companies can lock themselves into creating something only one company needs by failing to define their target customer set. Monitors that sold for over $1,000 a few years prior can cost $200 today.

Prioritization Frameworks

The critical path framework focuses product teams on solving the most severe user pain points during their journey to secure adoption. By evaluating a user's emotional state and friction points across their journey map, teams identify hot-button aggravations that drive users to seek alternatives. Solving these critical pain points is a mandatory prerequisite for user acquisition and retention.

In mid-2016, Evan Ryan's team was approached by startup BarnManager to relaunch its product by discovering that horse management teams desperately needed a secure digital repository for records instead of whiteboards and manila envelopes.

You should apply concrete practices to find and score what matters:

• Analyze the user journey map to tease out emotions and state of mind at each step.
• Pinpoint negative emotion states and key pain points causing the most distress.
• Determine the single thing or set of things the solution needs to get right.

The Kano model classifies customer expectations into expected, normal, and exciting needs to help prioritize features based on perceived value. Expected needs are absolute minimum dissatisfiers. Normal needs are satisfiers that customers explicitly ask for. Exciting needs are delighters that go beyond expectations to establish category leadership, though over time, expectations naturally rise.

Intermittent windshield wipers were once exciting features in the 1970s, but they became normal expectations, prompting luxury brands to invent rain-sensing wipers.

You can continue with these steps:

• Classify potential product features into expected needs, normal needs, and exciting needs.
• Ensure expected critical path needs are fully satisfied before allocating resources to delighters.

Scoring initiatives across desirability, feasibility, and viability helps teams evaluate customer value, execution ease, and organizational profitability. Using a simple numerical scale allows teams to multiply or add scores along each axis to calculate a composite priority score, separating well-rounded ideas from options that only look good on a single dimension. A low score scale value is 1, a medium score scale value is 2, and a high score scale value is 3.

When a car maker evaluated adding custom colors versus a hybrid drivetrain, custom colors scored low on manufacturing feasibility and viability, whereas the hybrid drivetrain scored a maximum 9 out of 9, compared to 4 for custom colors and 6 for a leather interior.

Follow these evaluation steps:

• Score each initiative on customer desirability using a simple scale.
• Score each initiative on organizational feasibility of building it.
• Score each initiative on commercial viability and contribution to revenue or profit.

An ROI scorecard divides customer and organizational value by company-wide effort to quantify and rank large lists of potential product initiatives. Value combines customer needs and organizational goals, while effort accounts for engineering, marketing, sales, and cross-functional costs. Using T-shirt sizing and deliberate imprecision keeps teams from getting bogged down in false mathematical precision while enabling objective trade-off discussions. T-shirt sizing scale values mapped to sizes range from 1 to 5, while revenue opportunity debates can range from a lower end of $500K to an upper end of $600K.

Bruce McCarthy used relative ROI scorecards to prioritize features, projects, lean experiments, acquisitions, and even which car to buy with his wife.

Complete the analysis with these scorecard guidelines:

• Define customer needs and organizational goals to represent total value.
• Estimate cross-functional effort using abstract T-shirt sizing like extra small to extra large.
• Apply a confidence risk factor multiplier to discount uncertain investments.

MoSCoW categorizes prioritized requirements into unambiguous release buckets to prevent scope creep and align stakeholders on launch criteria. MoSCoW does not set priorities itself, but clearly communicates what must-haves, should-haves, could-haves, and won't-haves mean in terms of minimum-to-ship features versus items to be cut under budget or deadline pressures. Product teams use MoSCoW buckets to separate critical path dissatisfiers from optional delighters so that scope discussions do not derail mid-project.

Structure your scope using these specific allocations:

• Group requirements that must be met to launch into the Must have bucket.
• Place important but non-critical items into the Should have bucket.
• Assign desired items that can be cut easily into the Could have bucket.
• Designate out-of-scope items for the current release as Won't have.

7. Achieving Alignment and Buy-in

Alignment and collaboration through shuttle diplomacy and co-creation workshops are essential to secure organizational buy-in without relying on consensus.

Alignment versus Consensus

Alignment is a concerted effort to understand roles and issues through listening and feedback. It allows people with differing opinions to agree on intentions. Consensus often leads to endless discussions resulting in decisions where no individual can be held accountable. You need collaboration and alignment rather than consensus, which creates friction and diffuses responsibility.

Shuttle Diplomacy and Workshops

Shuttle diplomacy involves meeting stakeholders individually to negotiate trade-offs and build support before bringing the group together. By meeting with each stakeholder one-on-one, you can eliminate office politics, discover hidden agendas, build rapport, and foster a sense of shared authorship in the plan.

Bruce McCarthy used shuttle diplomacy by taking a scorecard with goals and ideas to individual executives to score what they cared about before sitting the whole group down for a one-and-a-half-hour meeting that successfully established a roadmap. Target outcomes during these discussions included 15% y/y growth in profit for CEO Joan and $24MM in revenue in Q1 2017 for Sales lead Mark. Use these GROW questions to guide your individual meetings:

• Goals: What are they trying to accomplish in the next X months?
• Reality: What's on their plate now? What's recent?
• Options: What do they think will help them achieve those goals? What options have you already discussed that need to be revisited?
• Way forward: Which of the options helps them achieve the goals they described earlier in the conversation? Which options are at the top of their list and why?

Co-creation workshops bring cross-functional stakeholders together after shuttle diplomacy to finalize prioritization and build final buy-in through structured exercises. These workshops rely on a culture of constructive disagreement and agreement on overall strategy, moving away from a top-down mandate to a collaborative roadmap creation process. Follow this exact agenda during your workshop:

• Intro and rules (5 min)
• Hopes and fears (10 min)
• Vision and goals (10 min)
• Back-plan (15 min)
• Sizing and prioritizing (40 min)
• Wrap-up (10 min)

8. Presenting and Sharing Your Roadmap

Tailoring your roadmap presentation by audience and sharing it internally leverages the IKEA effect, while external sharing requires careful risk management.

Sharing the roadmap broadly across internal departments provides inspiration, cross-functional alignment, and leverages the IKEA effect to secure buy-in. Involving people from every department in developing and refining the roadmap increases their investment in the plan, akin to why people love furniture they built themselves. In 1996, the year Open Market went public, Jeff Bussgang described how they used their product roadmap during a major platform re-architecture to articulate long-term value to customers and sell through a difficult period without new features, driving revenue growth from zero to close to a hundred million dollars.

Internal Sharing and External Risks

Sharing roadmaps externally carries risks such as overpromising, triggering the Osborne Effect, and exposing plans to competitors. Announcing future plans too early can stall current sales if customers wait for unreleased versions or if competitors intercept strategic direction. In 1983, sales of the Osborne 1 computer fell sharply leading to bankruptcy after Adam Osborne pre-announced new computer models that outperformed existing ones, causing dealers to cancel orders.

Different stakeholders require different levels of detail and specific complementary information added to the core roadmap foundation. Development teams need feature lists, scalability, and technical debt. Sales and marketing need stages of development and target customers. Executives need high-level vision, P&L, and market opportunity. Special feature requests from sales or partners must be thoroughly vetted by questioning their underlying problem and alignment with strategic objectives. When stakeholders attempt to slip in special requests, you should avoid taking feature requests at face value.

Presentation Flow and Tailoring

An effective roadmap presentation follows a specific sequence that starts with the why, incorporates emotion and stories, and outlines near-term and long-term horizons. In 2013, Chef.io CEO Jesse Robbins presented a top-down roadmap that struggled to meet expectations. The company later shifted to a theme-based product roadmap using ProdPad and a slide deck divided into Considering, In development, and Released cycles.

• Start the presentation with the why and ensure alignment on product vision.
• Cover recent progress including emotion, quotes, or customer anecdotes.
• Show near-term items and clarify critical needs that drove prioritization.
• Propose longer-term initiatives while reinforcing company objectives.

When evaluating incoming demands, you must ask these questions:

• What problem is this request trying to solve?
• Does solving that need align with our objectives?
• Is it more important than what's on the roadmap now?

10 Key Ideas

1. A product roadmap must function as a strategic communication tool that outlines how a team intends to achieve its vision rather than serving as a rigid project plan or release schedule of unvalidated features.
2. Product teams must commit to delivering outcomes that solve customer problems and provide organizational value rather than focusing purely on output like feature delivery dates.
3. An effective product roadmap requires primary components that tell a cohesive story of vision, progress measurement, and sequencing without relying on rigid dates.
4. You must study your business ecosystem, product life-cycle phases, and customer needs by differentiating between user roles and utilizing personas to build deep empathy.
5. Connecting your organizational mission, product vision, values, and objectives and key results ensures that every roadmap item ties directly back to measurable outcomes.
6. Organizing your roadmap around high-level customer problems using themes, user journey maps, and job stories prevents premature commitment to specific solutions.
7. Secondary components such as features, stages of development, and explicit confidence scores add clarity and increase execution speed without cluttering the strategic message.
8. You must avoid gut-feeling prioritization and apply rigorous frameworks like the critical path, Kano model, desirability-feasibility-viability, and ROI scorecards to manage opportunity cost.
9. Alignment and collaboration through shuttle diplomacy and co-creation workshops are essential to secure organizational buy-in without relying on consensus.
10. Tailoring your roadmap presentation by audience and sharing it internally leverages the IKEA effect, while external sharing requires careful risk management to avoid the Osborne Effect.