CAPM Practice: Demonstrate an understanding of product roadmaps

Transparent prioritization rationale builds trust and reduces 'why isn't my request on the roadmap' conflicts. When stakeholders understand the business reasoning behind priorities, they're more likely to accept trade-offs even when their preferences aren't top-ranked.

**Why not A:** Assuming rationale is self-evident from the roadmap is a common communication failure. Without explicit documentation of the business case, stakeholders fill the vacuum with assumptions — often assuming their pet project was deprioritized unfairly, leading to unnecessary conflict and political friction.

**Why not B:** Restricting prioritization rationale to the development team leaves business stakeholders without the context needed to support, defend, or intelligently challenge roadmap decisions. Transparent communication of trade-offs to all relevant stakeholders is a core BA responsibility.

**Why not C:** Withholding rationale to avoid debate is counterproductive and erodes trust. When stakeholders do not understand why decisions were made, they are more likely to escalate, lobby for changes through back channels, and disengage from the requirements process entirely.