5 Valuable Product Management Insights Worth Sharing
The product management insights that most change how practitioners think aren’t usually the ones that confirm existing beliefs. They’re the counterintuitive findings, the challenging observations, and the carefully argued positions that require genuine engagement before their value is visible.
These five insights represent the kind of perspective-shifting thinking that makes PM discourse valuable — the ideas that are worth arguing with, sitting with, and eventually integrating into practice.
Insight 1: Your Users Aren’t Using Your Product the Way You Designed It
User research consistently reveals that users find unexpected creative uses for products, create workarounds for features that don’t quite serve their needs, and completely ignore features that designers invested heavily in. The product as designed and the product as used are different products, and the gap between them is both the most valuable information the PM can have and the most commonly ignored.
The most important research question isn’t “are users using this feature?” — it’s “what are users actually doing with our product, and what does that reveal about what we should build instead?”
Insight 2: The Features Your Users Love Are Not the Features They Requested
There’s a consistent gap between what users request and what they love. Users request incremental improvements to what they know; they love capabilities they couldn’t have imagined. The feature request list is a valuable input to product planning, but it systematically underweights the transformative innovations that create the strongest emotional product attachment.
Insight 3: Your Roadmap Is More of a Communication Tool Than a Plan
The product roadmap’s primary function isn’t planning in the operational sense — it’s communication: creating the shared understanding across the organization that enables coordinated action. The best roadmap isn’t the one with the most accurate future-state prediction; it’s the one that creates the clearest shared understanding of direction and reasoning.
Insight 4: Saying No Well Is More Important Than Saying Yes Well
The products that achieve genuine excellence are almost always products that declined far more opportunities than they accepted. The quality that makes a product excellent isn’t usually the sum of its best features; it’s the coherence that comes from maintaining ruthless focus on the user problems the product is specifically designed to solve.
Insight 5: Your Product Strategy Is Only as Good as Its Most Questionable Assumption
Every product strategy contains assumptions. The quality of the strategy is bounded by the accuracy of its most questionable assumption — the one that, if wrong, would undermine the entire strategic direction. Identifying and testing this assumption before committing significant resources to the strategy consistently produces better outcomes than discovering it’s wrong after the investment is made.
Key Takeaways
The five insights — about the gap between design and use, between requests and delight, between planning and communication, between features and focus, and between strategy and its riskiest assumption — each challenge conventional PM thinking in ways that, if engaged honestly, improve product practice. The value is in the challenge, not just the confirmation.
The Value of Sitting With Discomfort
The most valuable product management insights are often uncomfortable precisely because they challenge practices or beliefs that feel secure. The insight that most of your features will have less impact than expected challenges the feature-shipping metric that many product organizations use. The insight that your roadmap is primarily a communication tool rather than a plan challenges the detailed planning investment that many product organizations make. Sitting with these discomforts long enough to genuinely engage them — rather than retreating to the comfort of familiar practices — is where the most significant professional development happens.
Key Takeaways
The five insights — about the gap between design and use, between requests and delight, between planning and communication, between features and focus, and between strategy and its riskiest assumption — each challenge conventional PM thinking in ways that, if engaged honestly, improve product practice. The book’s most enduring contribution is the reframing it provides: roadmapping isn’t a planning activity that produces a document; it’s a communication activity that produces shared understanding. This reframing, internalized, changes how PMs approach every aspect of roadmap work — from what to include, to how to present it, to how to maintain it over time.