CAPM Practice: Validate requirements through product delivery

Onboarding struggles reveal requirements failures: users who can't figure out the system indicate missing requirements for guidance, intuitive design, or workflow support. Support tickets generated during onboarding are a direct signal of requirements gaps — features that should have been specified but weren't.

**Why not B:** Requirements validation through onboarding is not exclusively a training team responsibility. While training teams manage onboarding logistics, the BA should analyze onboarding friction to identify gaps in the original requirements. Delegating this entirely to training teams means valuable requirements feedback never reaches the people who can act on it for future releases.

**Why not C:** Dismissing onboarding as merely a training activity ignores its diagnostic value for requirements quality. When users struggle during onboarding, it often signals that requirements for usability, error handling, or workflow intuitiveness were incomplete. The onboarding experience is a direct reflection of whether the delivered product meets real user needs.

**Why not D:** User onboarding applies to all software products, not just consumer applications. Enterprise software users also go through onboarding and frequently encounter the same types of usability challenges. Excluding enterprise software from onboarding-based validation ignores a significant source of requirements feedback in the business environment where BAs most commonly operate.