Delivering the Business Case
Delivering the Business Case — to the Bottom Line
A transformation programme can have a compelling business case.
Millions of pounds of savings.
Higher productivity.
Improved customer service.
Reduced headcount.
Better working capital.
New revenue opportunities.
The numbers can look excellent.
But there is one fundamental question that every leadership team should keep asking:
Are the benefits actually being realised?
Too often, the business case is approved at the beginning of a transformation programme and then becomes a static document — rarely revisited and even less frequently challenged.
That is a mistake.
A transformation is only successful when the promised improvements are translated into measurable changes in business performance.
The business case is a hypothesis
At the beginning of a transformation, many of the expected benefits are estimates.
They are based on assumptions about:
Productivity
Technology adoption
Headcount
Volumes
Pricing
Process performance
Customer behaviour
Systems capability
Those assumptions may be entirely reasonable when the business case is developed.
But once the transformation starts, they need to be tested against reality.
The business case should therefore become a management tool, not a document sitting in a programme folder.
As new information becomes available, leadership teams should be asking:
What has changed?
Which assumptions remain valid?
Which benefits are now more or less achievable?
What do we need to do differently to realise them?
Measure benefits — not activity
A transformation programme can be:
On time
On budget
Green on the RAG report
Delivering its milestones
…and still fail to deliver the expected value.
Why?
Because activity isn't value.
A new system being implemented isn't a benefit.
A process being redesigned isn't a benefit.
Training being completed isn't a benefit.
These are outputs of the transformation.
The benefit comes when the organisation actually performs differently.
Implementation is an output.
Value realisation is the outcome.
This distinction is critical.
Some transformation partners are very good at demonstrating the value they have helped create. Others are less rigorous.
Leadership teams should insist on seeing evidence that the benefits have actually flowed through into operational and financial performance.
Make the benefits real
Consider some simple examples.
New systems
Implementing a new system does not automatically create a saving.
If the business case includes the removal of legacy technology costs, the legacy systems need to be switched off.
Otherwise, the organisation may simply end up paying for two systems instead of one.
Released capacity
A transformation may create significant additional capacity.
But capacity isn't automatically a cost saving.
If five roles become unnecessary, the cost reduction only appears when those costs are actually removed.
Alternatively, management may deliberately decide to redeploy the capacity into a new growth initiative.
Either can be the right decision.
What matters is that the decision is explicit and reflected in the business case.
Training and productivity
Training completion is not the same as capability.
If a transformation assumes productivity improvements, those improvements need to be demonstrated.
For example:
Is output per FTE increasing?
Are processes being performed consistently?
Are cycle times reducing?
Is right-first-time performance improving?
Are employees actually using the new processes and systems?
The objective is not to demonstrate that training happened.
The objective is to demonstrate that performance improved.
Give every material benefit an owner
Every significant benefit should have a named executive owner.
Not the PMO.
Not the transformation programme.
Not "the business".
A named individual who is accountable for delivering the outcome.
They should be able to answer:
What was the original benefit?
What has actually been delivered?
When will the benefit appear in the P&L or cash flow?
What is preventing it from being realised?
What action is required to close the gap?
If nobody owns the benefit, there is a significant risk that nobody owns the value.
The Aludum mantra: control the inputs and monitor the outputs
Financial benefits often appear relatively late.
By the time the impact becomes visible in EBITDA, cash flow or revenue, it may be too late to correct the underlying problem.
That is why transformation leaders should monitor the leading indicators that drive the financial outcomes.
For example:
Transformation objective Leading indicator
Productivity Output per FTE
Working capital DSO / inventory / payment performance
Customer experience Service levels / complaints / retention
Process improvement Cycle time / right-first-time
Technology adoption % of transactions using the new process
Cost reduction Run-rate cost versus baseline
These measures provide an early indication of whether the expected financial benefits are actually on their way.
This is the essence of the Aludum approach:
Control the inputs and monitor the outputs.
Understand what drives performance, actively manage those drivers and then measure whether the expected business outcomes are being delivered.
Don't be afraid to change the business case
Sometimes the original assumptions will prove to be wrong.
That is not necessarily failure.
What matters is recognising it early and responding appropriately.
Leadership teams should be prepared to ask:
What has changed?
What benefits are still achievable?
What should we stop?
Where should we invest more?
What assumptions need to change?
What is the highest-value route from here?
A good transformation leader doesn't protect the original business case at all costs.
They protect the value opportunity.
That means communicating the current position honestly, explaining the reasons for any change and presenting the options available to management.
A business case that evolves in response to evidence is far more valuable than one that remains unchanged simply because it was approved at the beginning of the programme.
Transformation is not successful because the programme finished
One of the easiest traps in transformation is measuring success by programme completion.
The system went live.
The new process was implemented.
The training was delivered.
The project was closed.
The consultants left.
The programme was declared successful.
But did the business actually improve?
Did productivity increase?
Did costs fall?
Did working capital improve?
Did customer service get better?
Did revenue increase?
Did the organisation become easier to manage?
Did enterprise value increase?
That is the real test of transformation.
Technology enables transformation.
Processes support transformation.
People deliver transformation.
But value realisation is the reason for doing it.
From transformation plan to measurable value
At Aludum, we believe transformation should ultimately be measured in terms of business performance.
We help management teams turn transformation plans into measurable operational and financial results.
That includes supporting programmes that are:
Still being designed
Already in delivery
Failing to realise their expected benefits
Becoming more complex than originally anticipated
Off track and in need of recovery
Requiring additional senior operational leadership
The objective isn't simply to get a programme back to green.
It is to ensure that the transformation delivers the value the business needs.
The question for leadership teams
Is your transformation programme measuring activity — or proving value?
Transformation Insights is Aludum's series exploring the practical realities of business transformation, operational excellence and value creation.
Aludum works with management teams to turn transformation ambition into measurable business performance.