CAPMHard

CAPM Practice: Demonstrate an understanding of product roadmaps

Question 66 of 67 in Demonstrate an understanding of product roadmaps

Pick an answer below — you'll get the explanation instantly, no signup.

How does a product team avoid 'output-focused' roadmaps and create 'outcome-focused' ones?

Show answer & explanation

Correct answer: For each planned item, define the customer outcome it's intended to create and the metric that will measure achievement — shifting the conversation from 'what we'll build' to 'what will change for users'

Explanation

Output-focused roadmaps list features to build. Outcome-focused roadmaps add context: what customer behavior should change, and how will we measure it? This shifts team conversations from delivery execution to value creation, enabling smarter decisions about how to achieve outcomes.

**Why not A:** Outcome-focused roadmaps are applicable to all product types, not just consumer-facing ones. Internal tools, enterprise software, and platform products all benefit from defining intended outcomes and success metrics. Every product should articulate the change it aims to create for its users.

**Why not B:** Removing all specific features and replacing them with vague themes makes the roadmap too abstract to be actionable. Outcome-focused roadmaps still include specific initiatives, but each one is linked to a customer outcome and measurable metric, providing both direction and accountability.

**Why not D:** Replacing all feature descriptions with financial projections shifts the roadmap from a product planning tool to a financial forecast. While financial impact matters, outcome-focused roadmaps center on customer behavior changes and experience improvements, which ultimately drive the financial results.

Key Concept

This question covers Demonstrate an understanding of product roadmaps under Demonstrate an understanding of product roadmaps (Business Analysis Frameworks).

All 1,500+ CAPM questions are free