CAPM Practice: Determine how to gather requirements

When elicitation reveals a solution-problem misalignment, the BA has an obligation to surface it. Continuing with the wrong solution wastes resources and delivers no value. A clear, evidence-based recommendation to the sponsor is the professional response.

**Why not A:** Proceeding with a solution known to be misaligned with the business problem wastes project resources and delivers no business value. Waiting until the close-out report to mention the issue is too late — the BA has a professional obligation to surface the finding while corrective action is still possible.

**Why not B:** Simply documenting the discrepancy in a lessons learned file defers action to future projects rather than addressing the current problem. The finding requires immediate escalation so the current project can be redirected toward the actual business need.

**Why not D:** Continuing to gather requirements for the original solution perpetuates the problem. If elicitation has revealed the solution won't address the real business problem, collecting more requirements for that solution only deepens the investment in the wrong direction.