Defining the Business Problem or Opportunity

Before any requirement gets written, a business analyst has to pin down exactly what problem or opportunity is actually driving the work — not the first symptom someone mentions, but the real underlying gap between where the business is and where it needs to be. Problem analysis techniques (root-cause analysis, for instance) and opportunity analysis both exist to get past a vague complaint like "sales are down" and into something specific enough to act on.

That clarified problem or opportunity statement becomes the foundation for two downstream artifacts: a solution scope statement, which bounds what the eventual solution will and won't cover, and input into a business case, which justifies why the organization should invest in solving it at all. Skipping this step tends to surface later as a solution that's technically well-built but doesn't actually address what was wrong.

Study focus: a scenario describing a stakeholder jumping straight to "build us a new reporting dashboard" without ever stating the actual business problem is signaling a missed Needs Assessment step — the correct response is almost always to step back and define the problem first, not to start scoping the dashboard.