Business Goal vs Requirement: Why the Order Matters
Distinguish business goals from requirements and learn why outcome-first sequencing prevents premature solution constraints.
Published:
A business goal defines the change and value sought. A requirement defines a capability or condition a solution must satisfy. Starting with the goal makes each requirement explainable.
Outcome before specification
Goals and requirements are both necessary, but belong to different levels.
- 01
Purpose
The goal explains why change matters; the requirement states what must be true.
- 02
Stability
A goal can remain stable while requirements change as evidence emerges.
- 03
Validation
Goals use outcome evidence; requirements use acceptance tests.
- 04
Order
Confirm the goal, derive needs, then specify requirements.
From portal to outcome
‘Buy a supplier portal’ prescribes a category. ‘Reduce incomplete supplier onboarding without weakening verification’ exposes multiple paths and makes later portal requirements traceable.
What this method cannot guarantee
- Evidence and operating conditions can change; revisit the record when a material input changes.
- This method structures evidence and judgement; accountable people still make and own the final decision.