CAPM Practice: Demonstrate an understanding of business analysis (BA) roles and responsibilities

When stakeholders say 'I need a report' (solution), the BA asks 'What decision will you make with that report?' (underlying need). The underlying need might be better served by a dashboard, alert, or process change rather than the proposed report — preserving solution design flexibility.

**Why not A:** Accepting solution bias as actual requirements would undermine the integrity of the requirements process. When stakeholders express preferences for specific solutions rather than stating their actual needs, a business analyst must probe deeper to uncover the underlying business need. Treating biased statements as requirements leads to solutions that may not address the real problem.

**Why not C:** Encouraging solution bias is counterproductive to effective business analysis. While stakeholder input is valuable, allowing unchecked solution bias can constrain the solution space and prevent the team from discovering better alternatives. The BA's role is to guide stakeholders toward expressing needs rather than prescribing solutions.

**Why not D:** Countering stakeholder bias with the analyst's own solution preferences introduces additional bias rather than resolving the issue. The business analyst should remain neutral and objective, using techniques like root cause analysis and "why" questioning to move beyond any individual's preconceived solutions toward the true business need.