The learner can tell a stated want from the real underlying need, surface implicit and conflicting requirements, and avoid asking leading questions.
The gap between what stakeholders say and what they really need
The gap between what stakeholders say and what they really need
A stated want is the solution a stakeholder proposes: 'I need a new report.' The real need is the underlying business problem they are trying to solve: 'I can't tell which sales reps are underperforming until the end of the quarter.' If the analyst builds the report without understanding the need, they may solve the wrong problem entirely.
The '5 Whys' technique helps uncover the real need: ask 'Why do you need that?' repeatedly until you reach the root business goal. The key is to probe without putting words in the stakeholder's mouth. Compare: 'So you need this report because the current dashboard is broken, right?' (leading — suggests the answer) vs. 'What is making it hard to track sales-rep performance today?' (open probe — lets the stakeholder answer freely).
Implicit requirements are things stakeholders assume without saying — for example, they say 'build a customer portal' but assume it will work on mobile, support Russian and English, and meet the company's security policy. A good analyst surfaces these by asking 'What would a successful outcome look like?' and 'Are there any constraints or standards it must meet?'
Conflicting requirements arise when two stakeholders want incompatible things, or when an explicit requirement contradicts a policy or an implicit assumption. The analyst's job is to flag conflicts — not to decide which stakeholder wins. That decision belongs to the business.
Lesson notes
The gap between what stakeholders say and what they really need
A stated want is the solution a stakeholder proposes: 'I need a new report.' The real need is the underlying business problem they are trying to solve: 'I can't tell which sales reps are underperforming until the end of the quarter.' If the analyst builds the report without understanding the need, they may solve the wrong problem entirely.
The '5 Whys' technique helps uncover the real need: ask 'Why do you need that?' repeatedly until you reach the root business goal. The key is to probe without putting words in the stakeholder's mouth. Compare: 'So you need this report because the current dashboard is broken, right?' (leading — suggests the answer) vs. 'What is making it hard to track sales-rep performance today?' (open probe — lets the stakeholder answer freely).
Implicit requirements are things stakeholders assume without saying — for example, they say 'build a customer portal' but assume it will work on mobile, support Russian and English, and meet the company's security policy. A good analyst surfaces these by asking 'What would a successful outcome look like?' and 'Are there any constraints or standards it must meet?'
Conflicting requirements arise when two stakeholders want incompatible things, or when an explicit requirement contradicts a policy or an implicit assumption. The analyst's job is to flag conflicts — not to decide which stakeholder wins. That decision belongs to the business.