CAPM Practice: Demonstrate an understanding of product roadmaps

A hypothesis-driven roadmap treats planned work as experiments: 'We believe that [feature] will [outcome] for [customer], and we'll measure it by [metric].' This integrates learning into the roadmap and enables pivoting when hypotheses are disconfirmed.

**Why not A:** A hypothesis-driven roadmap does not require executive review of each hypothesis before inclusion. Instead, it empowers teams to formulate hypotheses about customer value and design experiments to validate them. The emphasis is on learning through experimentation, not on adding a governance approval layer.

**Why not B:** A hypothesis-driven roadmap looks forward with uncertainty, not backward with certainty. It explicitly acknowledges that customer preferences are unknown and proposes experiments to test assumptions. Building a roadmap on historical proof of success describes a data-driven approach, which lacks the experimental, innovation-focused nature of hypothesis-driven planning.

**Why not D:** Including only features already validated by market research eliminates the experimental nature that defines hypothesis-driven roadmaps. The whole point is to test unproven ideas through small experiments. A roadmap restricted to pre-validated features is risk-averse and does not support the innovation that hypothesis-driven approaches are designed to enable.