CAPMHard

CAPM Practice: Demonstrate an understanding of product roadmaps

Question 49 of 67 in Demonstrate an understanding of product roadmaps

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

A company has 200 feature requests from customers. How should the product team use this input in roadmap planning?

Show answer & explanation

Correct answer: Analyze patterns and themes across requests, identify the underlying needs, validate with customer research, and use the insights to prioritize themes that address the most common and impactful underlying needs

Explanation

Feature requests represent symptoms of underlying needs. Analyzing patterns reveals which needs are most common — solving the root need may address multiple feature requests with a single, well-designed solution. Frequency alone is a poor proxy for strategic importance.

**Why not A:** Implementing only features from the highest-paying customers creates a biased roadmap that serves a narrow segment. Strategic priorities, underlying need patterns, and the broader customer base should all inform roadmap decisions — not just revenue from individual customers.

**Why not B:** Implementing features based solely on request frequency ignores strategic alignment and underlying needs. Many different feature requests may point to the same root need, and a single well-designed solution could address multiple requests more effectively than building each one individually.

**Why not C:** Adding all 200 requests and expanding the team is impractical and ignores prioritization. Feature requests are raw input that must be analyzed for patterns, validated against strategy, and prioritized by impact. Attempting to build everything wastes resources on low-value items.

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