A business case has little governance value if it is written to secure approval and then ignored while the assumptions that justified the investment continue to change.
Most organisations understand why a business case is needed before significant investment. Fewer use it effectively after approval.
Once the project starts, attention shifts to scope, schedule, cost, risk and delivery milestones. The original case can become a historical document stored with initiation records. Yet the reasons for funding the work may be changing at exactly the same time that commitment is increasing.
The supplied study material contains an important tension. It describes the business case as a start-up document used by senior management to assess proposed initiatives, but it also states that the case should be reviewed and revised at decision gates as estimates and information mature.
The second interpretation is strategically stronger.
A business case should not be treated as a permanent truth. It should be treated as the current evidence for why continued investment remains justified.
The Strategic Context
The supplied APM-based notes describe a business case as justification for undertaking a project, programme or portfolio. They frame it around the benefits, costs and risks of alternative options and the rationale for the preferred solution.
The same material identifies five dimensions:
- strategic context;
- economic analysis;
- commercial approach;
- financial case;
- management approach.
Together these dimensions make the business case broader than a financial model.
The case explains why change is needed, why one option is preferred, whether the investment is affordable, how it will be sourced and governed, and how value is expected to emerge.
This is important because a project can remain within budget while the investment case deteriorates. Demand can change. Regulation can shift. Technology can move. Benefits can become less valuable. An alternative solution can become available. Organisational capacity can tighten.
If governance monitors only execution performance, leaders may successfully deliver an investment that no longer deserves to continue.
What Leaders Commonly Misread
The first misreading is that approval validates the assumptions in the business case.
Approval only means the assumptions were considered adequate at that decision point. It does not make them true.
The second is that changing the business case indicates poor planning.
For uncertain work, better information should change estimates. Mature governance expects the evidence base to improve. Refusing to revise the case can be a greater weakness than revising it.
The third is that the sponsor's job is largely complete once the project is authorised.
The supplied notes explicitly state that the sponsor owns the business case. That ownership should mean more than signing the document. It means remaining accountable for the continuing strategic rationale and benefit logic while the project team is accountable for delivery within its delegated authority.
These responsibilities are related but not interchangeable.
Reframing the Issue
The business case should answer two questions throughout the investment lifecycle:
Why did we approve this investment?
and
Given what we know now, should we continue to invest on the same basis?
The first preserves decision history. The second enables adaptive governance.
This reframing turns the business case into a control mechanism for strategic drift.
The Five Cases Leaders Need to Keep Connected
Strategic case: Is the problem still worth solving?
The project should remain connected to the strategic need that justified action.
If priorities change, the project may need to be accelerated, redesigned, deferred or stopped. Strategic alignment is therefore not a one-time scoring exercise.
Economic case: Does the preferred option still create sufficient value?
The source material emphasises option appraisal and return on investment. The economic case should retain the logic of alternatives, including the do-nothing option where appropriate.
As cost and benefit estimates mature, the ranking of alternatives can change.
Commercial case: Can the organisation obtain what it needs on viable terms?
A technically attractive solution may depend on an unrealistic supplier model, procurement strategy or contractual allocation of risk.
Commercial conditions are part of feasibility, not merely purchasing administration.
Financial case: Can the organisation afford the investment over time?
Affordability differs from value. An investment may have strong long-term benefits but still create unacceptable cash-flow pressure or conflict with other commitments.
That distinction is essential in portfolio decisions.
Management case: Is there a credible route from approval to outcomes?
The business case should not end at delivery. Governance, roles, lifecycle choice, transition arrangements and benefit ownership all influence whether the intended value will be realised.
Related article: From Deliverables to Benefits: Closing the Gap Between Project Completion and Enterprise Value
A Business Case Should Contain Conditions, Not Just Conclusions
Weak cases often present a single conclusion: proceed.
Stronger cases explain the conditions under which proceeding remains sensible.
For example:
- demand must remain above a threshold;
- operating cost must remain within a range;
- a critical approval must be obtained by a date;
- the organisation must secure specific capability;
- the implementation must not displace a higher-priority initiative;
- adoption must reach an agreed level before later investment is released.
These conditions create governance triggers.
Instead of asking only whether the project is “green” or “red”, leaders can ask whether the investment thesis remains intact.
The Do-Nothing Option Is a Governance Baseline
The supplied notes observe that a business case normally includes a do-nothing option as a reference. This is more important than it first appears.
Doing nothing is not necessarily cost free. It may leave an operational problem unresolved, allow risk to grow, sacrifice revenue or delay compliance. But it establishes a baseline against which active options can be judged.
Without that baseline, almost any improvement can be made to look attractive because the analysis compares the proposal with an undefined future. A credible do-nothing case forces the organisation to describe what is likely to happen if it chooses not to invest.
The same discipline should continue after approval. If the external environment changes, the cost of doing nothing may increase or decrease. That change can alter the relative attractiveness of the project even when the project's own scope has not moved.
Decision Gates Should Release Commitment, Not Reward Momentum
A decision gate is useful only when leadership is willing to make a decision.
If every gate ends with continuation regardless of evidence, the gate is merely a reporting ritual. A stronger model releases commitment progressively. Early stages may authorise investigation. Later stages may authorise design, procurement, construction or deployment as confidence improves.
This approach is particularly important for irreversible commitments. Once a major contract is signed, an asset is ordered or a public launch date is announced, the practical ability to change course can shrink sharply.
For that reason, gate design should reflect reversibility. Decisions that lock in cost, architecture or market position deserve stronger evidence and clearer escalation than decisions that can be reversed cheaply.
Decision Framework
At each major decision gate, the sponsor and governing body can review six tests.
| Test | Gate question |
|---|---|
| Strategic relevance | Is the original need still important enough to justify investment? |
| Option superiority | Is this still the best available course of action? |
| Benefit sufficiency | Are expected benefits still meaningful and achievable? |
| Affordability | Can the organisation still fund the work without unacceptable trade-offs? |
| Risk exposure | Has uncertainty changed enough to alter the decision? |
| Delivery credibility | Is there still a credible path from current state to operational outcomes? |
A deteriorating answer should trigger explicit reconsideration, not automatic continuation.
This is especially important when sunk costs are high. Money already spent is not evidence that future spending is justified.
From Strategy to Execution
Immediate action: require every material business case to identify its critical assumptions, benefit owners and review triggers.
Medium-term capability: align project gates with business-case reviews. Delivery progress and investment justification should be considered together rather than in separate governance forums.
Long-term positioning: integrate business cases into portfolio management. If one project's case weakens while another opportunity strengthens, the organisation should be able to reallocate capital and capability deliberately.
This is how business cases become part of enterprise decision intelligence rather than isolated documents.
Signals to Monitor
Leadership should intervene when:
- the project team cannot find the current approved business case;
- benefits are described generically rather than owned and measured;
- scope changes are assessed only for cost and schedule effects;
- gate reviews never reconsider the do-nothing or alternative options;
- affordability is treated as equivalent to economic value;
- sponsor attention falls sharply after approval;
- a project is protected because of previous spending rather than future value;
- assumptions that justified approval are no longer tracked.
These are signs that project control has become disconnected from investment control.
Questions for the Leadership Team
- What evidence justified this investment when we approved it?
- Which of those assumptions has changed?
- If the project had not started, would we approve the remaining investment today?
- Is the preferred option still better than the credible alternatives?
- Who owns the benefits after handover, and are they prepared to accept that accountability?
- What conditions would cause us to stop, redesign or defer the work?
- Are our governance gates testing continued value or merely checking delivery compliance?
Closing Perspective
A business case should survive the approval meeting.
Its enduring purpose is to connect strategic need, investment logic, risk, affordability, governance and expected benefits as the organisation learns more.
When leaders revisit that logic at meaningful decision points, they retain the ability to change course before delivery momentum becomes more powerful than strategic judgement.
That is the difference between approving projects and governing investments.