CAPM Practice: Demonstrate an understanding of product roadmaps

Sharing the roadmap with sales helps them set accurate customer expectations, use planned features as selling points, and avoid over-committing based on outdated product knowledge — aligning sales promises with actual product direction.

**Why not A:** Product roadmaps communicated to sales teams focus on upcoming capabilities and timelines, not detailed technical specifications. Technical specifications are typically shared through product documentation or solution engineering teams. Sales needs to understand what the product will do, not the technical details of how it works.

**Why not C:** The purpose of sharing the roadmap is informational, not to give sales the authority to modify roadmap priorities. Roadmap priorities are set through product management processes that balance input from many sources. Allowing individual sales reps to change priorities based on single customer requests would undermine strategic product planning.

**Why not D:** Sharing a roadmap does not authorize sales to commit to specific delivery dates with customers. Delivery dates depend on many factors including development capacity, dependencies, and changing priorities. Sales should communicate general direction and timeframes while making clear that dates are subject to change.