Decision Quality Comes from Decision Quantity: Why business cases succeed or fail long before the final recommendation
Most business cases are framed around a single, defining question:
Should we proceed with this investment?
It is treated as a moment of judgement — a point where decision-makers weigh evidence, consider risks, and arrive at a clear answer.
But in practice, the quality of that decision is not determined at the end of the process.
It is determined much earlier — through the accumulation of many smaller decisions.
Business cases are systems of decisions
A business case is often presented as a document — a structured argument supported by analysis.
In reality, it is something else entirely:
A business case is a system of decisions.
These decisions are rarely framed explicitly. They appear as assumptions, inputs, or technical positions:
What level of demand is forecast?
What standard are we designing to?
What risks are accepted, and which are mitigated?
What constitutes “fit for purpose”?
Which benefits are real, and which are contingent?
Each of these is a decision. And each decision shapes the next.
By the time a final recommendation is reached, much of the outcome has already been determined.
Decision quantity drives decision quality
There is a common instinct in complex projects to “focus on the big decision” — to preserve flexibility, avoid premature commitments, and ensure that the final recommendation is robust.
In practice, this often leads to the opposite outcome.
When smaller decisions are delayed or avoided:
Assumptions multiply
Caveats expand
Options remain artificially open
Analysis becomes defensive rather than decisive
The result is familiar:
Recommendations qualified “on balance”
Requests for further work
Delays presented as diligence
Avoiding small decisions does not reduce risk — it places it into the final decision, where it is hardest to manage.
Decision quality at the end of the process is not improved by holding decisions back.
It is improved by making more decisions — earlier, and more clearly.
Decisions compound, not just accumulate
In complex infrastructure and regulatory environments, decisions do not sit in isolation. They interact.
A demand forecast influences option sizing.
Option sizing influences cost.
Cost influences economic viability.
Viability influences perceived risk.
Weakness in one area propagates through the system.
Low decision quantity does not just leave gaps — it distorts the entire structure of the business case.
By contrast, numerous well-made decisions — even if imperfect — create a coherent base from which subsequent decisions can be made.
The real constraint: authority and risk
If decision quantity drives decision quality, the obvious question follows:
Why aren’t more decisions made?
The answer is rarely capability. It is almost always structure.
Complex decisions require judgement to be exercised at multiple levels — across disciplines, teams, and advisors. But many organisations concentrate authority, reserving decisions for senior levels while expecting detailed analysis to progress below.
This creates a tension:
Decisions need to be made locally, with partial information
But authority — and accountability for risk — is centralised
Without clear delegation, teams respond predictably:
Decisions are deferred or escalated
Positions are hedged
Optionality is preserved beyond the point where it adds value
The system slows — and the quality of the final decision degrades.
Decision quality depends on how decisions are distributed
The implication is straightforward:
You cannot centralise a complex decision.
The number and nature of decisions required make this impractical.
Instead, decision-making must be distributed — deliberately.
This requires two conditions to be met.
Clear delegation
Teams must understand:
What they are expected to decide
What sits within their authority
What must be escalated
Without this, decisions either stall or are made implicitly without ownership.
Explicit risk tolerance
Delegation alone is not sufficient.
People will not make decisions unless they understand the level of uncertainty they are expected to carry.
This includes:
Acceptable ranges of variation
Tolerance for incomplete information
Boundaries between “good enough” and “not yet ready”
Delegation without defined risk tolerance creates hesitation.
Risk tolerance without delegation creates bottlenecks.
Both are required for a decision system to function effectively.
What good looks like in practice
High-performing business case processes tend to share common features:
Decisions are made early, even where information is imperfect
Decisions are explicit, rather than embedded in analysis
Decision rights are clear, across project, program, and executive levels
Rationale is recorded, allowing decisions to be revisited deliberately
Revisit points are structured, rather than continuous
Progress is not measured by how much has been written.
Progress is measured by how much has been decided.
A simple test
A practical way to assess the quality of a business case is to ask:
What decisions have actually been made?
What decisions remain open?
Are we choosing not to decide — or simply avoiding it?
If these questions cannot be answered clearly, the issue is not the analysis.
It is the decision system itself.
Closing
Complex investment decisions are not made in a single moment of clarity.
They are assembled — piece by piece — through a sequence of smaller decisions made under uncertainty.
Decision quality does not emerge at the point of approval.
It emerges from the quantity — and quality — of decisions made along the way.
Where those decisions are avoided, delayed, or left unresolved, the consequences do not disappear.
They accumulate.
And they arrive, in full, at the point where the organisation is asked to decide.