…It’s time you two talked

12 Steps Series – 5 of 12
Executive Summary
One of the most persistent gaps in strategy execution is the disconnect between approved investment and realised value. Most organisations are proficient at securing approval and funding for initiatives, yet far less effective at demonstrating how those investments translate into measurable business performance.
Business cases are written to gain endorsement and budget, then quietly retire once delivery begins. As a result, governance optimises for cost, scope and schedule, while the question that matters most — did this create value, and how do we know? — is deferred or debated after the fact.
Outcome Management resolves this by reframing the business case as a value discipline, not a one-off approval artefact. It distinguishes between three distinct purposes: the Compliance Case to establish strategic relevance, the Funding Case to support capital allocation, and the Value Case to explicitly link investment to operational performance and benefits realisation.
The Value Case is the one most often forgotten. It defines which measures will move, by how much, through which drivers, and who in the business owns those outcomes — creating a testable, enduring connection between delivery and results.
Your Business Case Isn’t Broken.
It’s Just Missing Its Third Act.
Your people aren’t bad at business cases.
What’s usually happening in almost every organisation is that they do business case 1 and 2 – The Compliance Case and Funding Case, forget to do the one that actually connects investment to benefits realisation.
That’s the third one and it’s called is the Value Case.
The three business cases every organisation needs
Once you see the three types, the misalignment suddenly makes sense.
Let’s name them.
1. The Compliance Case (Get me on the radar)
The first type is the Compliance Case.
Its job is simple: get the initiative onto the organisational radar so it can be considered alongside other options. At this point, you are not trying to prove a detailed ROI. You are answering more basic questions:
- Is this aligned to strategy?
- What problem or opportunity does it address?
- Is there a plausible value story?
- Is it broadly feasible?
This case should be light. A sensible template, a clear line of sight to strategy, and a rough order-of-magnitude view of costs and value. If you ask for deep analysis at this stage, you slow everything down and discourage people from surfacing ideas.
The Compliance Case is about visibility and comparability, not precision.
2. The Funding Case (Get me Budget)
The second type is the Funding Case.
Here the question becomes sharper:
“Should we invest scarce capital and people in this initiative, ahead of other things we could do?”
The Funding Case expands on the basics:
- Scope and major activities
- Project development and solution options
- High level roadmap and sequencing
- Potential delivery risks and constraints
- Cost and benefit estimation
This is the material investment and portfolio forums rely on. It supports prioritisation and decision quality. You want enough detail to compare options sensibly, understand trade-offs, and set initial expectations.
So far, this is where most organisations stop. The assumption is that once a Funding Case has been written and approved, “the business case” has been done. This is the Gap.
3. The Value Case – (Here are the Benefits)
The third type, and the one most often missing, is the Value Case.
The Value Case is not about whether the project is a good idea in theory. It is about how value will show up in actual business performance and return on investment:
“Which performance measures will this initiative move, by how much, how will we know and how much value will this create?”
“Which performance measures will this initiative move, by how much, how will we know and how much value will it create?”

To answer that, you need to move beyond generic benefit statements and into specifics:
- Which operational drivers will change (volumes, cycle times, error rates, conversion, utilisation, etc.)?
- Which business KPIs do those drivers feed (revenue, cost, cashflow)?
- What are the current performance baselines and target levels?
- How will these be measured in practice – which systems, which reports, at what frequency?
- Who in the business owns each benefit, not just who runs the project?
This is rarely a quick desktop exercise. It often requires engagement with operational leaders, interrogation of data, and a realistic view of where attribution is possible and where it isn’t.
The point is not to create perfect forecasts. The point is to create a shared, testable view of value that can be used to guide decisions during delivery and after go-live.
Without this, benefits realisation tends to collapse into two unhelpful states: optimistic numbers at the start, and debate at the end.
Why this matters for CFOs and Strategy Leaders
When the Value Case is absent, several patterns tend to appear:
- Benefits are written as generic aspirations (“improve efficiency”, “enhance customer experience”) rather than measurable operational changes.
- Governance focuses on scope, schedule and budget, with benefits as a final slide rather than a central thread.
- Post-implementation reviews struggle to answer a basic question: “Can we measure performance uplift and the value it has created?”
Separating the three cases creates a different dynamic:
- The Compliance Case keeps the funnel open and aligned.
- The Funding Case supports disciplined capital allocation.
- The Value Case links investment to performance and keeps that link visible over time.
For CFOs and Strategy / Transformation leaders, the practical move is:
- Make the three types of case explicit in your process and language.
- Keep the Compliance Case light.
- Use the Funding Case to make choices, not to inflate promises.
- Require a distinct Value Case – with metrics, baselines, targets and owners – before full funding is released.
- Use the Value Case as a living reference in governance and business intelligence reports, not as an attachment that gets filed away.
Your people don’t need to write longer business cases. They need the space and expectation to complete this third piece of work.
This is where the connection between business case and benefits realisation is built – or lost.
