Lies, Damn Lies, and Business Cases

There’s an old line often attributed to Mark Twain:

“There are three kinds of lies: lies, damn lies, and statistics.”

It applies uncomfortably well to business cases.

Not because people are dishonest.
But because business cases are designed to secure approval.

They are built on assumptions.
They are optimistic by necessity.
And once approved, they are rarely interrogated again.

The problem is not the business case itself.
It’s what happens when assumptions are treated as facts.

‍

The Business Case Is Not the Problem

A business case serves an important purpose.

It forces clarity of intent.
It articulates expected value.
It defines why capital and capacity should be allocated.

But in many organizations, once approved, it becomes an artifact — filed, referenced, and largely forgotten.

Execution moves forward.
Resources are consumed.
Governance tracks schedule, spend, risk, and delivery milestones.

What is rarely asked is:

Are the assumptions still true?
Is the value still achievable?

‍

‍

Static Business Cases Create Static Decisions

Traditional business cases are snapshots in time.

They assume:

• Costs remain stable
• Benefits materialize as forecast
• Risks behave as expected
• Market conditions remain broadly consistent

In reality:

• Interest rates change
• Tariffs shift
• Input costs rise
• Customer demand fluctuates
• Competitive pressure intensifies

Even internal assumptions — such as expected customer adoption, pricing, or cost of production — can erode quickly.

If those assumptions change, so does the value.

Yet governance often continues to focus on:

• Schedule adherence
• Budget variance
• Resource utilization
• Risk logs

All important.
But none answer the most critical question:

Is this initiative still worth the capacity and investment we are allocating to it?

This is not a technology gap.
It is a decision discipline gap.

‍

‍

Transformation 4.0 Requires Living Business Cases

If transformation is continuous — not episodic — then the business case cannot remain static.

It must become a living instrument.

That means three things.

‍

1. Test Assumptions Explicitly

Every major initiative is built on assumptions:

• Cost of capital
• Market growth
• Adoption rates
• Productivity gains
• Pricing stability

Those assumptions should be visible — and reviewed regularly.

Not annually.
Not at post-implementation review.
But during execution.

‍

2. Track Lead Indicators — Not Just Outcomes

Many organizations measure value only at the end.

But by the time benefits fail to materialize, capacity has already been consumed.

Mature organizations identify lead indicators that signal whether value is still on track.

For example:

• Early adoption metrics
• Sales pipeline conversion
• Operational cycle time improvements
• Cost reduction run-rate
• Productivity trend data

Lead indicators provide early warning.

They allow recalibration before value is lost.

‍

3. Review the Business Case During Benefits Realization

Benefits realization is often treated as a retrospective exercise.

Lessons learned.
Variance explained.
Value confirmed — or quietly written down.

Transformation 4.0 treats benefits realization as an active steering mechanism.

The business case becomes the baseline for measurement:

• Are benefits tracking?
• Are assumptions holding?
• Has value increased?
• Has it diminished?

If the answer changes, resource allocation should change.

Not because something failed.
But because reality evolved.

‍

The Hardest Discipline: Reallocating Scarce Capacity

The true test of execution maturity is not how well an organization launches initiatives.

It is how confidently it reallocates capacity when the facts change.

That requires:

• Visibility into real performance
• Transparency of assumptions
• Governance that enables recalibration
• Courage to challenge sunk-cost thinking

In today’s uncertain environment, capital is constrained.
Capacity is limited.
Volatility is constant.

Organizations cannot afford to be wrong for long.

Decision integrity matters.

‍‍

From Artifact to Instrument

The purpose of a business case is to secure funding.
The purpose of execution is to create value.

In immature systems, those two objectives diverge.

In mature systems, they remain tightly linked.

The business case does not disappear.
It evolves.

From artifact.
To instrument.
From justification.
To accountability mechanism.

‍

When Capacity Is Scarce, Assumptions Matter

Every Transformation Office eventually faces the same reality:

If we can only resource one initiative, which should it be?

In theory, the answer is simple: the one that creates the most value.

In practice, decisions are often influenced by:

• Historical momentum
• Political sponsorship
• Prior investment
• Forecasts created under different market conditions

‍

When demand exceeds capacity — and it always does — trade-offs must be made.

The real question is whether those trade-offs are based on:

Current evidence, or outdated assumptions?

‍

The question is not whether your business cases are optimistic.

They almost always are.

The real question is whether your organization is willing to test those assumptions in-flight — and reallocate capacity when the value no longer justifies it.

Transformation maturity is not about approving more initiatives.

It is about resourcing only the ones that continue to earn it.

‍

If you’d like to explore how mature organizations operationalize living business cases and continuous value visibility, speak to our team.

‍