CAPM Practice: Demonstrate an understanding of product roadmaps

Overloaded roadmaps force constant trade-offs between delivery speed and quality. Teams take shortcuts to hit all commitments, accumulating technical and requirements debt. A focused roadmap with fewer, better-executed items consistently delivers more real value than an ambitious list that can't be fully realized.

**Why not A:** An overloaded roadmap is not a staffing signal — it is a planning problem. Simply growing the team does not solve the fundamental issue of overcommitment. Adding more people introduces coordination overhead and does not address the root cause of trying to deliver too many things simultaneously.

**Why not B:** More roadmap items do not automatically equal more value. In fact, spreading effort across too many initiatives often dilutes focus and reduces the quality of each delivery. Prioritization and focus typically deliver more customer value than attempting to do everything at once.

**Why not C:** Characterizing an overloaded roadmap as "impressive ambition" normalizes a harmful planning antipattern. Ambitious goals are valuable, but committing to an unrealistic number of items is not ambition — it is poor prioritization that sets the team up for failure, burnout, and stakeholder disappointment.