The business case is the most under-invested document in any project
Most projects do not begin with a bad plan. They begin with a business case that is more confident than the organisation has earned.
The document may look perfectly respectable. It has the right headings, a sensible commercial narrative, a benefits table, some risk language, an options section and a financial model that suggests the investment should proceed. It has been through review, probably several times. By the time it reaches the approval forum, it no longer feels like a question. It feels like the paperwork required to confirm a decision that momentum has already made.
That is where trouble often starts.
A business case should be the organisation’s best attempt to understand whether an investment is worth making, what conditions must be true for it to succeed, and how value will be realised once money, time and attention are committed. Too often, it becomes something else: a permission document. It is written to secure approval rather than to improve the quality of the decision.
At Arqvera, we would describe this as a readiness problem as much as a planning problem. The business case is where ambition should meet evidence. If that meeting is shallow, rushed or politically managed, delivery inherits the weakness. The project may not fail immediately. It may even report well for a while. But the conditions for later value leakage have already been built into the baseline.
The business case is not the admin before the work
The UK Government’s business case guidance describes the Five Case Model as a step-by-step approach for developing project and programme business cases, covering the strategic, economic, commercial, financial and management cases. It is intended for people involved in developing, reviewing and approving business cases, and is designed to support better appraisal and decision-making before commitment. (gov.uk)
That structure is useful because it reminds us that a good business case is not just a financial argument. It should test whether the investment is strategically necessary, whether options have been properly considered, whether the preferred route creates value for money, whether it is commercially viable, whether it is affordable, and whether the organisation can actually deliver and manage the change.
In plain language, it should answer five leadership questions:
- Does this matter?
- Is this the best way to achieve it?
- Can we buy or build it sensibly?
- Can we afford it?
- Can we deliver it and realise the value?
Many business cases answer the first four more confidently than the fifth. That is dangerous because the management case is where the investment stops being an idea and becomes an organisational commitment. It should test governance, delivery capability, readiness, adoption, benefits ownership, risk, dependency management and post-implementation value tracking. These are not secondary details. They are the route by which the promised value either appears or does not.
When the business case is treated as an approval hurdle, these questions are often underdeveloped. Everyone wants the decision. Fewer people want the discomfort of finding out that the organisation is not yet ready for the decision.
Poor planning is not a technicality. It is value destruction.
The evidence on major project performance is not exactly soothing bedtime reading.
Bent Flyvbjerg and Dan Gardner’s work on major projects draws on a database of more than 16,000 projects and has been widely cited for the finding that only 8.5% of projects are delivered on time and on budget, while only 0.5% are delivered on time, on budget and with the promised benefits. The exact result should not be used as a casual slogan, but the direction of travel is clear: major projects are systematically exposed to overrun, delay and benefit shortfall. (independent.org)
The National Audit Office has reached similar conclusions from the public sector side. Its work on over-optimism in government projects warns that initiating projects on unrealistic assumptions undermines value for money and can lead to unviable projects. The NAO is particularly clear that optimism bias must be tackled rather than accepted as a harmless planning feature. (nao.org.uk)
HM Treasury’s supplementary Green Book guidance on optimism bias also recognises that business cases need explicit adjustment for the tendency to underestimate costs and duration while overestimating benefits. The guidance notes that high optimism bias may be tolerable at an early strategic outline stage, but would not normally be acceptable at full business case stage. (gov.uk)
The pattern is not limited to infrastructure or government. Private sector transformations suffer the same pathology, even if the language is different. Costs are understated. Benefits are over-claimed. Internal capacity is assumed. Adoption is simplified. Supplier dependency is softened. Data quality is treated as a manageable detail. Governance is described rather than designed. The business case becomes less a test of reality and more a negotiation with optimism.
That may feel efficient at approval stage. It becomes expensive during delivery.
Optimism bias is human. Strategic misrepresentation is organisational.
There are two uncomfortable forces at work in weak business cases.
The first is optimism bias. This is the human tendency to believe that our project will go better than comparable projects, that our team will manage the risks, that our assumptions are more robust and that our benefits are more realistic. It is not always dishonest. In fact, it often comes from commitment, energy and belief. People want the initiative to succeed, so they unconsciously adjust the world until success looks more likely.
The second force is strategic misrepresentation. That is a more political behaviour. Costs are softened because a realistic number might not get approved. Benefits are amplified because the investment needs a stronger story. Risks are described gently because nobody wants to slow momentum. Internal constraints are parked because “we will work that out in mobilisation”. It is not necessarily villainous, but it is corrosive.
Flyvbjerg’s academic work distinguishes between optimism bias and strategic misrepresentation as central causes of misinformation in major project planning, arguing that poor front-end information creates risk for decision-makers and increases the likelihood that the wrong projects proceed, or the right projects proceed on the wrong basis. (arxiv.org)
Philip’s voice in this conversation matters because it is tempting to make this sound like a spreadsheet discipline. It is not. Weak business cases are often produced by human systems under pressure. Sponsors want progress. Teams want investment. Suppliers want commitment. Finance wants numbers. Boards want confidence. Nobody wants to be the person who says the case is not ready.
But trust is a system. A business case either strengthens that system by creating clarity and candour, or it weakens it by laundering uncertainty into certainty.
The problem with “good enough to approve”
Many organisations operate with an unspoken business case standard: good enough to approve.
That standard is too low.
A business case should be good enough to govern from. It should be good enough to hold leaders accountable. It should be good enough to guide supplier selection, implementation sequencing, benefits tracking, operating model design and post-go-live management. If the case cannot do those things, it is not a business case in any meaningful sense. It is a funding request with a narrative attached.
The “good enough to approve” mindset creates predictable problems. Options appraisal becomes thin because the preferred answer is already known. Benefits are described at a level of abstraction that makes them difficult to measure later. Risk is treated as a list rather than a set of conditions requiring action. Delivery confidence is inferred from supplier capability rather than internal readiness. Adoption is assumed because communication and training have been mentioned. The operating model impact is underplayed because it may complicate the decision.
This is how projects are made fragile before they begin.
A better business case is not necessarily longer. In fact, some very long business cases are simply uncertainty buried under volume. The better test is whether the document improves decision quality. Does it show what has been assumed? Does it explain what has been tested? Does it expose what is still unknown? Does it separate committed benefits from possible benefits? Does it identify the organisational changes required to realise value? Does it give leaders enough evidence to say yes, no, not yet or only if?
Those last two options matter. “Not yet” and “only if” are underused leadership decisions.
The management case is where value often hides
The least glamorous part of the business case may be the most important: the management case.
This is where leaders should understand how the project will be governed, delivered, assured, adopted and measured. It should explain who owns the outcome, who owns the benefits, how decisions will be made, how risks will be escalated, how suppliers will be managed, what internal capability is required and how the business will sustain the change after delivery.
In many organisations, this section is weaker than it should be because the energy goes into the strategic and financial argument. That is understandable. Leaders need to know why the investment matters and what return it might generate. But if the management case is thin, the financial case is less reliable than it looks because the benefits depend on an execution model that has not been properly tested.
This is where Arqvera’sTrust Arq is relevant. Trust Arq is designed to create delivery assurance before “go” gets expensive, helping leadership teams test governance, delivery confidence, partner selection, readiness and value risk before major commitments harden. The purpose is not to slow progress. It is to prevent organisations from committing to a plan whose weakest assumptions are still hidden.
Benefits need owners before approval, not after go-live
Another common weakness is the treatment of benefits as financial outcomes rather than operational changes.
A business case may say that the investment will reduce cost, improve productivity, increase revenue, strengthen compliance, improve customer experience or create capacity for growth. These may be legitimate benefits, but they are not yet manageable. A manageable benefit needs a baseline, an owner, a measure, a timeframe and a credible link to specific changes in behaviour, process, capability or decision-making.
If a benefit does not have an owner before approval, it is unlikely to acquire one magically after go-live. If an operational leader is not willing to be accountable for the change required to realise the benefit, the business case is not ready. The project may deliver outputs, but value will remain someone else’s problem.
This is the point behind Arqvera’s Value Compass. Benefits realisation is not a register maintained by the PMO. It is a leadership discipline that connects investment to operational outcomes and keeps those outcomes visible after delivery activity has finished.
Organisations do not realise value from software. They realise value from changed behaviour. The business case should make that behaviour explicit.
Readiness is part of the business case
A strong business case should test organisational readiness as part of investment appraisal. This is often the missing link.
Is the leadership team aligned on the consequences of the change, not just the ambition? Does the sponsor have enough authority and time? Does the business have capacity to participate? Are subject matter experts genuinely available, or have they been volunteered without relief from day jobs? Is the data good enough to support the new operating model? Are there unresolved process variations that will become expensive during design? Does the organisation have a history of absorbing change well, or is trust already low?
These questions may feel uncomfortable because they shift attention from the attractiveness of the investment to the capability of the organisation. That is exactly why they need to be asked.
Arqvera’sChange Studio andTransformation Readiness Self-Assessment are built around this principle. Readiness should be tested before the organisation commits heavily, not diagnosed later as “resistance” when people struggle to adopt a change they were never properly prepared to absorb.
Readiness before investment is not caution for its own sake. It is the discipline of making better early decisions so later delivery has a fair chance.
What a better business case process looks like
A better business case process starts with curiosity rather than advocacy. It asks what problem the organisation is solving, what outcomes matter, what options genuinely exist and what evidence would change the recommendation. This matters because many business cases are written after the answer has already been chosen. The document then becomes a defence of the preferred route rather than an exploration of the best route.
The options appraisal should be meaningful. “Do nothing”, “do minimum” and “do preferred option” may be useful, but only if they are genuinely assessed. If the preferred option wins because the alternatives have been designed to look weak, the process has not created much confidence.
The economic and financial cases should separate hard benefits, soft benefits and strategic value clearly. Not everything important is easy to quantify, but that is not an excuse for vague claims. Strategic benefits should be described honestly, while financial benefits should be supported by baselines and ownership.
The commercial case should test supplier incentives and market reality. Can the organisation buy what it thinks it is buying? Are supplier assumptions realistic? Are responsibilities clear? Does the contract encourage the right behaviour? Has the organisation assessed its own ability to be a good client?
The management case should be treated as central. Governance, delivery capability, change adoption, data readiness, assurance, dependency management and benefits ownership should be part of the investment decision, not operational details left for later.
Finally, the business case should remain live. As scope, risks, assumptions and operating conditions change, the case should be updated. A business case that is never revisited after approval is not a management tool. It is an archaeological artefact.
The leadership test
The most useful question for leaders is not “Can we approve this business case?” It is “Would we be comfortable governing from it?”
If the answer is no, the case is not ready.
A business case should help leaders make a better decision, not just a faster one. It should create confidence before commitment, expose uncertainty before it becomes expensive and connect investment to the operational change required to realise value.
This requires courage because sometimes a better business case will slow the wrong decision, reshape the preferred option or reveal that the organisation needs to build readiness before it commits. That may be inconvenient. It is also leadership.
The cost of improving the business case is usually small compared with the cost of recovering a project that was approved on weak assumptions. Once suppliers are contracted, teams are mobilised, budgets are committed and expectations are set, candour becomes harder and correction becomes more expensive.
Most transformation problems arrive disguised as technology problems. Many began life as business case problems.
The document at the front of the project is not admin. It is the first real test of whether the organisation is prepared to turn ambition into outcomes.
About Arqvera
Is an AI and technology transformation consultancy and advisory.
We help organisations shape business cases, projects, deliver excellence, and realise change and outcomes that stick. We support organisations before, during, and after projects with an end-to-end service where our domain specialization comes to life.
Before (Inception): We work with you to clearly define the idea, vision, strategy, and business case for change, as well as help select the right partners, and establish governance
During (Execution): We help deliver project and change objectives while keeping implementation under control through structured governance and assurance to realise intended outcomes.
After (Value Realisation): We ensure outcomes deliver measurable value and embed continuous improvement from successes and learnings.
Arqvera is led by industry veterans in the UK and USA with 100+ years of technology delivery intelligence across global consulting, digital transformation, and mission-critical projects and programmes.