CAPM Practice: Demonstrate an understanding of product roadmaps

Early-stage roadmaps are highly exploratory — many hypotheses to test, few validated bets. Mature product roadmaps balance maintaining the existing product (reliability, performance), improving known pain points, and innovating for the next growth phase — all informed by rich user and market data.

**Why not A:** Stating that the roadmap becomes "more detailed and specific over time" reverses the typical pattern. While near-term items on a roadmap may be detailed, the overall roadmap as a product matures tends to become more high-level and vision-oriented as the product's direction stabilizes. Early-stage roadmaps are often more fluid and experimental, not less detailed.

**Why not B:** Claiming the roadmap is "replaced entirely by a project schedule" misunderstands the relationship between these artifacts. A roadmap and a project schedule serve different purposes—the roadmap provides strategic direction and vision, while the schedule manages tactical execution. Mature products still benefit from roadmaps to guide future evolution.

**Why not C:** "Fewer items with declining innovation" presents an overly pessimistic view of product maturity. While a mature product may shift focus from rapid feature development to optimization and sustainability, this does not mean innovation declines. Mature roadmaps often emphasize different types of value such as efficiency improvements, integrations, and market expansion.