product-roadmapping-and-portfolio
Product Roadmapping and Portfolio Management
Build roadmaps that communicate strategic intent without pretending to predict the future. This skill covers outcome-based sequencing, strategic-bet management, and portfolio-level choices — not feature-level prioritization or project scheduling.
Core Principles
-
Roadmaps are not project schedules. A roadmap communicates strategic direction and sequencing intent. It does not commit to dates by default. The default view is Now/Next/Later; dates appear only when explicitly labeled as commitments.
-
Distinguish four categories in every artifact. Every roadmap output separates evidence (observed data), assumptions (beliefs not yet validated), commitments (decisions with consequences for reversal), and options (alternatives under consideration).
-
Bets, not plans. Each roadmap item is a strategic bet — an investment with an expected outcome, a confidence level, explicit dependencies, and pre-defined continue/pause/kill/revisit criteria. A roadmap is a portfolio of bets, not a to-do list.
-
Portfolio thinking scales up and down. The same bet-record and roadmap structure works for a single product and for a portfolio of products.