CAPM Practice: Demonstrate an understanding of product roadmaps

Customer-centricity requires systematic customer input mechanisms: user research findings, support data, NPS feedback, customer advisory boards. BAs help ensure this evidence is represented in roadmap discussions alongside internal strategic priorities and technical constraints.

**Why not A:** Allowing the development team to select roadmap items based solely on technical preference undermines customer-centricity. While technical considerations matter for sequencing and feasibility, prioritization should be driven by customer value and business outcomes. A technically preferred approach that does not address customer needs fails to deliver meaningful value.

**Why not C:** Limiting executive input does not make a roadmap more customer-centric. Executives often bring strategic market insights, competitive intelligence, and organizational vision that inform customer-focused decisions. The goal is to ensure all inputs—including executive perspectives—are filtered through the lens of customer value rather than excluding stakeholder voices entirely.

**Why not D:** Requiring exactly three customer requests before adding an item to the roadmap is an arbitrary threshold that can delay critical improvements. Some high-impact customer needs may be expressed by a single key account, while frequently requested features may not align with strategic goals. Customer-centricity requires qualitative analysis of needs, not rigid numerical quotas.