CAPM Practice: Demonstrate an understanding of product roadmaps

Outcome-based roadmaps focus on 'what business result we want to achieve' (increase user retention by 15%) rather than 'what feature we'll build' (add notification system). This preserves flexibility — the team can discover the best path to the outcome.

**Why not A:** This choice confuses outcomes with outputs. An outcome-based roadmap looks forward to define desired future results (e.g., "reduce customer churn by 15%"), not backward to catalog completed deliverables. Listing past work products describes a retrospective report, not a strategic roadmap.

**Why not B:** Outcome-based and feature-based roadmaps differ substantively, not just in terminology. Feature-based roadmaps commit to specific solutions, while outcome-based roadmaps define the desired results and allow teams flexibility in determining how to achieve them. This distinction fundamentally changes planning and prioritization.

**Why not D:** Outcome-based roadmaps are applicable across all industries and sectors, not limited to healthcare and government. Any organization that wants to maintain strategic flexibility while pursuing measurable business or user results can benefit from organizing its roadmap around outcomes rather than features.