Needs Assessment: From Problem to Endorsed Direction
From problem to endorsed direction
Needs Assessment is the business analyst's pre-solution work: defining a situation or problem statement, gathering data on the current state, identifying the desired future state, measuring the gap, and recommending whether and how to close it. Candidates must sequence the work: identify the problem or opportunity, assess the current state (capability and performance), define business goals and measurable objectives, identify and evaluate options, then recommend a solution approach.
Name these concepts confidently: situation statement, problem/opportunity definition, root cause analysis (five whys, fishbone), gap analysis, SWOT and benchmarking, feasibility (technical, financial, operational, schedule, legal), cost-benefit analysis with NPV/ROI/payback, business case, product vision, context diagram, and the standing option to recommend doing nothing.
Traps. First, solution-jumping: answer choices that name a technology when the stem asked for a need. Second, confusing goals (qualitative direction) with objectives (SMART, measurable, time-bound). Third, treating a powerful stakeholder's request as a validated need. Fourth, skipping baseline metrics, which makes benefits impossible to evaluate later.
Rule of thumb: a need describes the gap between current and desired business performance; a requirement describes what a solution must do to close it. If a statement can only be satisfied by one product, it is a solution in disguise.
Worked example: "Loan approvals take too long; buy a workflow tool." Reframed: current approval cycle is nine days; the objective is three days within two quarters. Root cause analysis shows five sequential approvals. Options: do nothing, delegate authority for small loans, automate routing. The recommendation is the policy change plus priority automation, with metrics that Evaluation will later measure.