A business case should not prove that a sponsor’s preferred project deserves approval; it should make the investment logic testable enough that leaders can approve, reshape or reject it.
In many organisations, the business case has become a ceremonial document. A proposal gathers momentum, the preferred solution is already socially accepted, and the business case is produced to secure the remaining approval. Once funding is granted, the document is archived while delivery teams manage scope, schedule and budget.
That treatment removes most of the business case’s strategic value.
The supplied project-feasibility notes describe the business case as justification for a project, programme or portfolio, evaluating benefits, costs and risks across alternative options and providing the rationale for a preferred solution. The same material also states that the business case should be reviewed and revised at decision gates as estimates and information mature.
Those two ideas together produce a stronger concept: the business case is the organisation’s continuing investment thesis.
The Strategic Context
An enterprise does not invest because a project exists. A project exists because leaders believe a change is worth investing in.
The business case should capture that belief in a form that can be challenged. It should explain the problem or opportunity, why it matters now, what alternatives were considered, what value is expected, what it will cost, what assumptions must hold and how the organisation intends to govern delivery and benefits.
That is broader than a return-on-investment calculation.
The supplied material attributes five elements to the APM Body of Knowledge, 7th Edition: strategic context, economic analysis, commercial approach, financial case and management approach. These dimensions are useful because they prevent the decision from collapsing into a single financial ratio.
A project may have an attractive economic return but be unaffordable in the required period. It may be affordable but commercially dependent on an immature supplier. It may be strategically compelling but lack a management model capable of delivering the benefits.
What Leaders Commonly Misread
The first error is solution-first reasoning. The sponsor begins with “we need system X” rather than “we have problem Y”. Alternatives are then constructed around defending the chosen solution.
The second error is confusing benefits with outputs. “Implement a new platform” is not a benefit. “Reduce quotation lead time” may be. “Increase conversion while reducing engineering rework” is stronger because it identifies an outcome and a potential enterprise mechanism.
The third error is treating forecast precision as evidence quality. A spreadsheet containing a five-year cash flow to the nearest dollar may still be based on weak assumptions.
The fourth is assuming approval is permanent. If a business case is valid only at the decision date, governance loses the ability to respond rationally when assumptions change.
Reframing the Issue
A strong business case answers five executive questions.
Why change?
What problem, opportunity, obligation or strategic objective creates the need for action? What is the cost or consequence of maintaining the current state?
What are the real options?
At minimum, leaders should understand the do-nothing or do-minimum case, the proposed solution and credible alternatives. The purpose is not to manufacture options for presentation. It is to test whether the preferred approach is genuinely superior.
What value can be created?
Benefits should connect to measurable outcomes and eventually to enterprise or public value. They should distinguish direct benefits, enabling benefits and benefits that depend on further organisational change.
What must be invested and endured?
This includes capital cost, operating cost, transition cost, capability effort, disruption, risk exposure and opportunity cost.
What must be true?
Every business case contains assumptions about demand, productivity, adoption, price, schedule, technology, regulation and organisational behaviour. Governance improves when these assumptions become explicit conditions rather than invisible optimism.
The Business Case as a Decision Record
The source material notes that the approved business case records governance decisions about how the required return is expected to be achieved and that it should document options considered.
This matters later.
When a project encounters a material change, leaders need more than the original budget. They need to know why the investment was approved. If the original case depended on a three-year payback, a particular customer commitment or a certain production volume, a change to those assumptions may be more important than a modest schedule variance.
The business case therefore gives governance a baseline for rational reassessment.
Without it, continuation decisions can become dominated by sunk cost and political commitment.
A Business Case Should Include the Cost of Doing Nothing
The do-nothing option is often treated as a weak comparator. It should be taken seriously.
Doing nothing may create rising maintenance cost, safety risk, lost market share, compliance exposure or capacity constraints. But doing nothing may also be the rational choice if the proposed solution is premature or if the organisation can tolerate the problem until better technology, data or funding becomes available.
A credible do-nothing case prevents inflated urgency.
It also exposes the difference between “there is a problem” and “this project is the best response”.
Decision Framework
A decision-grade business case can be tested through seven evidence blocks.
| Evidence block | What leaders need to know |
|---|---|
| Strategic case | Why the issue matters and how it relates to enterprise direction |
| Options case | What alternatives exist, including do-nothing or do-minimum |
| Benefits case | What measurable outcomes will change and who owns them |
| Economic case | Whether expected benefits justify whole-life costs and risks |
| Affordability case | Whether the organisation can fund and absorb the commitment |
| Commercial case | How markets, suppliers, contracting and procurement affect viability |
| Governance case | Who decides, who delivers, who owns benefits and when the case is reviewed |
The precise labels can vary. The discipline should not.
From Strategy to Execution
Immediately, organisations should stop treating business-case approval as the end of investment analysis. Every material project should identify the assumptions and benefit measures that will trigger reassessment.
In the medium term, decision gates should distinguish between delivery confidence and investment confidence. A project can be well managed yet no longer worth continuing. Conversely, a strategically important investment may deserve intervention even when delivery performance is weak.
Over the longer term, organisations should compare forecast business cases with realised outcomes. This creates an evidence base about where optimism repeatedly enters the system. Perhaps demand forecasts are strong but implementation costs are routinely understated. Perhaps productivity benefits are realistic but adoption takes twice as long as assumed. That learning should change future approvals.
Signals to Monitor
Monitor benefit assumptions before benefits themselves. If the business case depends on transaction volume, customer adoption, staffing reductions, technology availability or regulatory approval, track those conditions early.
Other warning signs include business cases with only one serious option, benefits without named owners, costs that stop at project closure rather than whole-life operation, and decision gates that review delivery metrics without reviewing investment logic.
Questions for the Leadership Team
- What evidence would cause us to reject this business case even if the project can be delivered?
- Which assumptions create most of the expected value?
- Who owns each material benefit after the project team leaves?
- What is the credible do-nothing or do-minimum alternative?
- At what thresholds should the investment be redesigned, paused or terminated?
- How often do we compare realised benefits with the forecasts used to secure approval?
Closing Perspective
A business case is useful only when it can support a real decision.
That includes the uncomfortable decisions: choosing a different option, delaying commitment, reducing scope, changing the commercial model or stopping an investment that no longer deserves resources.
Used this way, the business case stops being paperwork around a project and becomes part of enterprise governance—the documented logic connecting strategy, capital and accountable outcomes.