Strategic Context and Business Analysis
Business analysis does not begin with a requirements list; it begins with understanding why change is being contemplated. The strategic context domain asks you to situate a piece of work inside the organisation's direction and the wider environment. Core concepts include the business analysis mindset (systems thinking, root-cause focus, value orientation), the distinction between strategy, tactics and operations, and the use of internal and external environmental analysis. Candidates should be comfortable with PESTLE for external forces, Porter's Five Forces for competitive pressure, SWOT for a combined internal/external view, and the VMOST or balanced-scorecard style framing for internal alignment. Also know the difference between efficiency (doing things right) and effectiveness (doing the right things), and between outputs (what is produced) and outcomes (the change in business state).
Traps
Questions often blur technique with purpose: SWOT is a summary tool, not an analysis engine, so an option that says 'SWOT identifies the root cause' is wrong. Another common trap is confusing a goal (broad aim) with an objective (specific, measurable, time-bound). Watch for options that jump straight to solutions before the strategic driver is established.
Rule of thumb
If a question asks where analysis should start, the answer is almost always the business need and strategic drivers, not the current process or the IT system.
Worked example
A retailer's sales are flat. A PESTLE scan shows new online-only competitors (external) while an internal review shows slow fulfilment. The strategic driver is competitive erosion; the objective might be 'reduce order-to-dispatch time by 30% within two quarters'. That framing precedes any process or tooling discussion.