In earlier articles, we established a simple but uncomfortable truth:
Services are the unit of value.
Not projects.
Not teams.
Not systems.
Services.
This article explores what inevitably happens when finance is not organised around that same truth.
Finance in the Fog
The finance committee meets quarterly.
Slides are polished. Business cases are compelling. Everyone is prepared.
Project A promises 20% efficiency gains.
Project B will “transform the customer experience.”
Project C is “critical infrastructure renewal.”
All three sound important. All three need funding.
But when someone asks the simplest questions, the room goes quiet:
- Which services will this actually improve?
- What do those services cost today?
- How will we know whether the investment worked?
Not because the numbers are wrong.
But because the numbers aren’t connected to anything real.
Finance operates in a fog.
The Spreadsheet Temple
Most organisations don’t treat financial planning as sense-making.
They treat it as ritual.
The PMO maintains elaborate cost models:
- CapEx vs OpEx allocations
- Project portfolios
- Resource forecasts
Finance tracks spending with discipline:
- Cost centres
- GL codes
- Purchase orders
- Variance reports
Governance demands business cases that justify every dollar:
- ROI calculations
- NPV projections
- Payback periods
All rigorous.
All defensible.
All structurally detached from the services the business actually delivers.
This is the Spreadsheet Temple - a parallel world where financial truth exists independently of operational reality.
The issue isn’t diligence.
It’s disconnection.
Cost Without Context
Most organisations don’t have a cost problem.
They have a visibility problem.
Ask:
“What does our Customer Onboarding service cost to run?”
No clear answer.
Because the cost lives everywhere except where the service does:
- HR (recruitment)
- IT (provisioning)
- Facilities (workspace)
- Learning & Development (training)
- Finance (billing setup)
Each tracked separately.
None attached to the service outcome.
Just as experience metrics fail when they’re detached from lived reality, cost fails when it’s detached from the service it describes.
Finance can show spending.
It cannot show cost of delivery.
Traditional financial models have quietly shaped organisational behaviour for decades.
Because they were only ever designed to accommodate financial value, organisations learned to translate everything into financial terms - whether it made sense or not.
Risk reduction became “cost avoidance”. Resilience became “efficiency”. Customer trust became “future revenue”.
Not because these translations were true - but because they were the only language the system could hear.
Not all value can be costed. But all value has to be identified.
When we force every benefit into a financial proxy, we don’t create clarity - we create distortion. The service may genuinely improve, but the organisation loses sight of why.
The Structural Disconnects (Not New - Just Exposed)
None of this is new.
It’s the same structural failure showing up in a financial form.
1. Cost Categories vs Services
Finance organises spend by:
- Department
- Category
- Project
- Ledger code
But customers don’t consume departments.
They consume services.
When cost is not anchored to services, every meaningful question requires translation - and translation always loses truth.
2. Run vs Change Is a False Boundary
Every organisation tries to separate:
- Run the business
- Change the business
We’ve already seen how this breaks accountability when projects are treated as the unit of change.
Finance simply inherits that distortion - and amplifies it.
The same work is:
- “Run” to one group
- “Change” to another
The distinction becomes political, not structural.
And almost nobody tracks whether change actually improved the run.
3. Business Cases Without Memory
Business cases are still treated as approval artefacts.
They win funding - then disappear.
Which means:
- Assumptions aren’t tested
- Benefits aren’t validated
- Learning doesn’t compound
This isn’t a finance failure.
It’s a governance failure.
Control without sense-making.
Approval without feedback.
Process without learning.
The Invisible Cost of Change
Here’s a question most organisations still can’t answer:
“What did it cost to change this service last year?”
Not just the project budget - the total cost:
- Design and planning
- Testing and rework
- Operational disruption
- Adoption and training
- Coordination overhead
These costs are real.
They’re just structurally invisible.
Without visibility of cost-of-change:
- Investment decisions rely on narrative
- Fragile services absorb repeated funding
- Finance remains reactive instead of predictive
This Isn’t About Finance Capability
Finance teams aren’t failing.
They’re operating exactly as the model allows.
Finance speaks in:
- Budgets
- Allocations
- Variance
Operations speaks in:
- Services
- Flows
- Capabilities
- Outcomes
Both are rational.
Neither is sufficient on its own.
This is not a people problem.
It’s a model problem.
Cost Is an Overlay, Not a System
Here’s the reframe that resolves the tension:
Cost is not a separate system.
It is an overlay on the service graph.
Services are the unit of:
- Value delivery
- Customer experience
- Operational risk
- Change impact
Cost does not exist independently of these.
It is a property of how services are constructed, operated, and evolved.
Which means finance doesn’t lose rigour - it gains context.
The Structural Anchor: The Service Graph
Every organisation already has an implicit service graph:
- Services consume platforms
- Platforms consume infrastructure
- Teams operate components
- Vendors sit on critical paths
The issue has never been absence.
It’s fragmentation.
Without a shared structural truth:
- Cost floats
- Change disconnects
- Decisions degrade into storytelling competitions
The Service Intelligence Base (SIB)
The Service Intelligence Base is not a reporting layer.
It is the structural spine that allows multiple perspectives - including finance - to coexist coherently.
It establishes:
- Authoritative service entities
- Stable identifiers across finance, PMO, and operations
- Relationship intelligence that shows dependency and impact
It does not replace finance systems.
It connects them to reality.
Common IDs: Where Alignment Actually Starts
The most important capability is also the least glamorous:
Shared service identifiers.
When finance, delivery, and operations all refer to the same service:
- Costs remain visible over time
- Business cases don’t “die”
- Change history accumulates
- Outcomes can be assessed honestly
This is where fog starts to lift.
Run and Change as Views, Not Silos
On the service graph:
- Run is the steady-state cost of delivery
- Change is the episodic cost of altering delivery
Same services.
Same dependencies.
Different questions.
This removes politics and reveals signals:
- Fragile services cost more to change
- Stable services deliver predictable ROI
- Chronic rework becomes visible early
Business Cases That Stay Accountable
When business cases remain structurally linked to services:
- Assumptions stay visible
- Predicted vs actual outcomes can be compared
- Run-cost impact is no longer a surprise
- Organisational learning compounds
The question shifts from:
“Why is this service expensive?”
To:
“What changed - and was it worth it?”
That’s a materially better conversation.
What Changes in Practice
When finance lives on the service graph:
- Budget conversations become concrete
- Portfolios become service bets, not project lists
- Run-the-business becomes honest
- Change-the-business becomes credible
- Governance gains memory
Evidence replaces storytelling.
The Real Test for Finance
The challenge isn’t transparency for its own sake.
It’s relevance.
The old model allows everyone to say:
- “We followed the process.”
- “We allocated correctly.”
- “We tracked spend.”
All true.
All insufficient.
Because the only question that ultimately matters is:
Did the business get value?
And that question can only be answered when cost lives where value lives - on the service graph.
From Fog to Focus
This isn’t about turning finance teams into engineers.
It’s about shared structural truth.
When cost, change, and delivery operate on the same service model:
- Strategy becomes executable
- Investment becomes accountable
- Services become financially legible
Not in spreadsheets.
Not in decks.
But where value actually exists.
The Question That Anchors Everything
Can you connect a dollar spent
to a service delivered
to a value created?
If not, finance hasn’t failed.
It’s simply been asked to operate without structure.
OSM offers a way out of the fog -
not by reducing financial discipline,
but by connecting it to reality.
Cost becomes an overlay, not a temple.
Investment becomes evidence-based, not story-based.
Finance becomes strategic, not just compliant.
And the organisation finally gets credible answers to the questions that matter:
- What does this service cost?
- Is it worth it?
- If we invest again - will it actually improve?