A product roadmap is a prioritised sequence of product investments — features, improvements, and initiatives — organised by time and communicating the product team's current thinking about where the product should go and when. Product roadmaps are both internal planning tools and external communication instruments, and their design requires balancing the precision of a plan with the flexibility of a directional guide. Roadmaps that are too specific create expectations that become commitments; roadmaps that are too vague provide no useful planning information for anyone who needs to coordinate with the product team. feature discovery ux Outcome-Based vs Feature-Based RoadmapsTraditional product roadmaps list features in sequence: "Q1: Reporting dashboard, Q2: Integration marketplace, Q3: Mobile app." Outcome-based roadmaps list the business or user outcomes to be achieved in each period, with the features that will address those outcomes as secondary detail: "Q1: Improve decision-making speed for analysts (reporting dashboard), Q2: Expand ecosystem reach (integration marketplace)." Outcome-based roadmaps are more flexible — if a better solution to the same outcome emerges, the outcome remains but the feature might change — and they communicate the why of product development rather than just the what.Prioritisation FrameworksPrioritisation — deciding which of many possible investments to make, and in what order — is the core skill of product strategy. Various frameworks attempt to make this decision more systematic: RICE (Reach, Impact, Confidence, Effort), MoSCoW (Must have, Should have, Could have, Won't have), and opportunity scoring are common examples. These frameworks are useful insofar as they force explicit consideration of multiple dimensions of a prioritisation decision, but they are not substitutes for judgment about which dimensions matter most in the specific product and market context. The output of any prioritisation framework should be a starting point for discussion, not a final answer that removes the need for human judgment. saas feature adoption Communicating Roadmap UncertaintyProduct roadmaps are plans, not commitments, and their reliability decreases as they extend further into the future. The near term — the next three months — can typically be planned with reasonable specificity. The medium term — three to six months — should be presented as directional rather than definite. The long term — beyond six months — should be presented as themes and aspirations rather than specific deliverables. Roadmaps that do not communicate this uncertainty gradient create unrealistic expectations in stakeholders who treat later-horizon items as commitments in the same way they treat near-term items, and who are disappointed when those later-horizon items change as the product strategy evolves.