CAPM Practice: Validate requirements through product delivery

Customer success metrics measure whether customers achieve their desired outcomes using the product. Declining NPS after a release may indicate that delivered requirements didn't improve the experience as intended; high feature adoption validates that the requirement addressed a genuine need.

**Why not A:** Customer success metrics encompass far more than sales revenue. Metrics like Net Promoter Score, feature adoption rates, and customer health scores directly measure whether the product meets user needs. These metrics provide critical validation feedback on whether requirements were correctly specified and implemented.

**Why not C:** Requirements validation does not end at deployment. Post-deployment validation through customer success metrics is essential for confirming that delivered functionality achieves intended business outcomes. BAs play a key role in connecting these outcome measurements back to the requirements that drove the work.

**Why not D:** While customer success may be managed by a dedicated team, the metrics it produces are directly relevant to product requirements. Feature adoption data and customer satisfaction scores inform whether requirements accurately captured real needs, making this feedback loop essential for BAs doing continuous improvement.