CAPM Practice: Validate requirements through product delivery

Customer satisfaction surveys (CSAT, NPS, product reviews) provide aggregate validation data: are customers satisfied with what was delivered? Low satisfaction despite technical correctness suggests requirements failed to capture what truly matters to users — a requirements quality issue.

**Why not B:** Measuring satisfaction with the project team's performance is a team evaluation metric, not requirements validation. Customer satisfaction as a validation metric assesses whether the delivered solution meets customer needs and expectations, not how well the team interacted with stakeholders.

**Why not C:** Customer satisfaction is not too subjective to be useful. Established instruments like CSAT scores, NPS, and structured product reviews provide quantifiable data that can indicate whether requirements correctly captured what users valued. Systematic measurement makes this inherently subjective domain actionable.

**Why not D:** Customer satisfaction metrics directly validate whether requirements were correctly specified. If customers are dissatisfied despite technically correct implementation, it indicates the requirements missed what truly matters to users. This is a core requirements quality signal, not just a marketing metric.