Key Takeaways from Product Roadmaps Relaunched
Product Roadmaps Relaunched, by C. Todd Lombardo, Bruce McCarthy, Evan Ryan, and Michael Connors, is arguably the most comprehensive examination of product roadmapping as a discipline that currently exists. It challenges many of the conventional assumptions about what roadmaps are for, how they should be built, and how they should be used — and the challenges are well-supported by the authors’ collective experience with how roadmaps actually function in real product organizations.
The Book’s Central Argument
The authors’ core claim is that most product roadmaps fail their intended audiences because they’re built for the wrong purpose: they’re built as execution plans rather than as strategic communication tools. The roadmap that specifies exactly what will be built in each quarter is answering a question that stakeholders don’t need answered at the roadmap level; the roadmap that communicates why specific outcomes are being pursued and how investments connect to strategic objectives is answering the questions that actually matter for organizational alignment.
This reframing — from roadmap as execution plan to roadmap as strategic communication — changes every subsequent decision about what the roadmap should contain, how it should be organized, and how it should be maintained.
The Most Actionable Recommendations
Organize around outcomes, not features: The authors argue extensively for outcome-based roadmaps that describe what the product will achieve for users rather than what it will do. This recommendation is both more philosophically correct (outcomes are what users actually want) and more practically useful (outcomes are more stable than implementations, so outcome-based roadmaps require less revision when specific implementation details change).
Use different roadmaps for different audiences: The authors provide specific guidance on creating multiple roadmap views — strategic, sales-oriented, engineering-oriented, customer-facing — from the same underlying strategic direction. The multi-view approach addresses one of the most common roadmapping failures: trying to serve all audiences with a single document that serves none of them adequately.
Build roadmaps collaboratively, not in isolation: The book makes a compelling case for collaborative roadmap development — collecting input before rather than feedback after — and provides practical guidance on how to structure collaborative roadmapping sessions.
Where the Book Challenges Conventional Thinking
The authors are explicit critics of date-based roadmap commitments, feature-list organization, and the practice of building roadmaps without explicit connection to product strategy. Each critique is well-supported and practically important — these are the specific practices that most consistently undermine roadmap effectiveness.
Key Takeaways
Product Roadmaps Relaunched is most valuable for PMs who are dissatisfied with their current roadmapping practice and want a comprehensive framework for rebuilding it. Its central arguments — outcome orientation, multi-view design, and collaborative development — each address specific ways that conventional roadmapping fails to serve its intended purposes.
The Ongoing Relevance of the Book’s Arguments
The arguments in Product Roadmaps Relaunched have if anything gained relevance since publication — as more product organizations have adopted the feature-list roadmap practices the book critiques and experienced their limitations. The product managers who encounter the book’s arguments as validation of instincts they’ve already developed find confirmation; those who encounter them before developing those instincts find the head start that would otherwise have required years of experience to produce.
Key Takeaways
Product Roadmaps Relaunched is most valuable for PMs dissatisfied with their current roadmapping practice and wanting a comprehensive framework for rebuilding it. Its central arguments — outcome orientation, multi-view design, and collaborative development — each address specific ways that conventional roadmapping fails to serve its intended purposes. The path back to enthusiasm often requires structural changes rather than attitude adjustments. The PM who finds their work engaging when they have genuine user contact and strategic ownership but disengaging when they’re reduced to feature coordination needs organizational changes — not personal motivation strategies — to restore genuine engagement.