Week 17: The ROI Conversation CFOs Actually Need to Hear
The ROI Conversation CFOs Actually Need to Hear
I've had the ROI conversation with more CFOs than I can count.
And I've watched, every single time, as the conversation goes sideways the moment someone opens a spreadsheet and starts projecting savings from lean implementation like they're forecasting next quarter's revenue.
Here's the problem. Most ROI models for continuous improvement are built on a lie. The lie is that ROI is a function of methodology. Pick the right framework, train the right people, run the right projects, and the return follows predictably. Like compound interest. Like a machine.
It doesn't work that way. It has never worked that way. And after twenty years, forty-plus organisations, and more than a billion dollars in documented savings, I can tell you exactly why.
The formula is not ROI = methodology.
The formula is ROI = methodology x leadership commitment squared.
Squared. Not multiplied. Squared. Because leadership commitment doesn't just add to results. It amplifies them exponentially. And its absence doesn't just reduce results. It destroys them entirely.
If leadership commitment is zero, it doesn't matter how good your methodology is. Zero squared is zero. Multiply that by the finest lean six sigma deployment money can buy, and you still get zero.
Let me tell you about two organisations. Same methodology. Same consultant. Same tools, same governance framework, same training content. Completely different outcomes.
The first was Shell.
I spent thirteen years at Shell. Deployed continuous improvement across Malaysia, Aberdeen, the UK, and globally. Trained more than three hundred practitioners. Touched twelve thousand FTEs. The documented savings exceeded one billion dollars.
But here's what most people don't understand about Shell's CI success. It wasn't the methodology that produced those numbers. The methodology was good. We used a rigorous, structured approach. Belt system. A3 thinking. Value stream mapping. Statistical tools where they mattered. All professionally deployed, all properly governed.
What made it work was the operating cadence that leadership maintained.
Every week, there was a review. Every month, there was a steering session. Every quarter, there was a strategic assessment. And leadership showed up. Not symbolically. Not as names on an invite list who sent delegates. They showed up personally, consistently, and with genuine attention.
I worked with operations directors who could walk you through the current state of every active project. Not because they'd been briefed five minutes before the meeting, but because they'd been to the Gemba. They'd spoken with the teams. They'd seen the data on the boards, not in a PowerPoint two levels removed from reality.
The result was a 10:1 ROI. For every dollar invested in the CI programme, Shell got ten back. Documented. Audited. Verified by finance.
Ten to one.
The second organisation was a manufacturing business in northern Europe. I was brought in as an external consultant. The company had just invested heavily in a CI deployment. They'd hired a CI director. They'd trained forty Green Belts and six Black Belts. They'd purchased software, set up governance structures, built project trackers, and launched with a town hall that featured all the right words from the CEO.
The methodology was essentially the same framework we'd used at Shell. Structured problem-solving. Belt-based capability building. Clear governance. Project selection based on strategic priorities. All the elements were there.
Six months in, I was asked to assess progress.
I walked the floor. I spoke with the Green Belts. I reviewed the project tracker. I sat in on a steering meeting.
Here's what I found.
The CEO who'd given the town hall speech had not attended a single CI review since the launch. Not one. He'd delegated oversight to the CI director, who reported to the VP of operations, who reported to the COO. The CI programme was four levels removed from the person whose visible commitment mattered most.
The steering meetings had devolved into status updates where project leads presented to other project leads while senior leadership sent apologies. The word "too busy" appeared in decline emails so frequently that the CI director had started scheduling meetings around leadership availability, which meant reviews happened every six to eight weeks instead of weekly.
The Green Belts were struggling. Not because they lacked skills. Because they couldn't get people released for project work. Because sponsors had lost interest. Because the signal from the top was unmistakable: this is not a priority.
The ROI at twelve months? Effectively zero. The programme had generated a handful of small improvements that were already reverting because nobody was holding the standard. The training investment alone — belts, software, consultant fees — was north of four hundred thousand euros.
Zero to one. Same methodology. Same tools. Same governance design. Same type of training. Same type of projects.
The only difference was leadership commitment. And that difference was the difference between ten-to-one and zero-to-one.
I presented this analysis to the board.
I remember the room. Long table. Eight people. The CEO at the head. The CFO across from me. The CI director next to me, looking like he was attending his own funeral.
I didn't soften the message. I've learned the hard way that softening the message in these situations does everyone a disservice. The money is already spent. The people are already frustrated. The only thing that helps is the truth.
I told them the methodology was sound. I told them the Green Belts were competent. I told them the project selection was reasonable. And then I told them the programme was failing because leadership had been absent.
I showed them the attendance data. Steering meetings: CEO attendance zero percent. COO attendance seventeen percent. VP Operations attendance thirty-three percent. I showed them the correlation between sponsor engagement and project completion. Projects with engaged sponsors: eighty-two percent completion rate. Projects without: eleven percent.
Then I showed them the Shell comparison. Same methodology. Different leadership behaviour. Different result by a factor of ten.
The CFO asked the question I was waiting for: "So what's the actual ROI of CI?"
I said: "That depends entirely on you. The methodology is the multiplier. But the base is your commitment. If your commitment is zero, the ROI is zero. If your commitment is real — genuinely real, measured in your time and attention, not your approval of a budget — then the return is ten to one. Maybe higher."
The room was quiet for about ten seconds. Which doesn't sound long until you're the one standing at the front of a boardroom having just told a CEO that he's the problem.
Here's what I want every CFO to understand about the ROI of continuous improvement.
You cannot model it in a spreadsheet the way you model capital investment. You cannot project it based on industry benchmarks. You cannot calculate it based on the number of belts trained or projects launched.
Because the single largest variable in the equation is not in your spreadsheet. It's in your calendar.
How much time does your CEO spend on the floor? How often does your leadership team attend CI reviews? When was the last time a board member asked a team about their improvement work and genuinely listened to the answer?
Those questions predict your ROI more accurately than any financial model ever will.
I have watched organisations with modest budgets and excellent leadership commitment generate extraordinary returns. At Shell Malaysia, some of the highest-impact improvements came from frontline teams with minimal formal training but massive leadership support. The investment was small. The return was disproportionate. Because leadership created the conditions where good ideas could surface, get supported, and get sustained.
And I have watched organisations spend millions on world-class CI infrastructure and get nothing. Not because the infrastructure was wrong. Because the leadership behaviour was wrong. Because the CEO treated CI as something that happened below them. Because the board approved the budget and then walked away.
The ROI conversation most organisations are having is backwards.
They ask: "If we invest X in CI, what return can we expect?"
The right question is: "If we commit Y hours of senior leadership time per week to visible CI engagement, what return can we expect?"
The answer to the first question is unknowable without knowing the answer to the second.
At Shell, leadership committed. The cadence was non-negotiable. Reviews happened weekly regardless of what else was going on. Operations directors went to the Gemba. Project sponsors were accountable for outcomes, not just approvals. And the result was a billion dollars in savings across thirteen years.
At the manufacturing company, leadership approved the investment and then disappeared. The cadence collapsed. The programme atrophied. The return was zero.
Same tools. Same training. Same governance design.
Different commitment. Different result by a factor of infinity.
If you're a CFO or a CEO reading this, I'm not asking you to take my word for it. I'm asking you to be honest about one thing.
When was the last time you personally attended a CI review? Not had someone brief you afterwards. Attended. Sat in the room. Listened to the teams. Asked questions. Followed up.
If the answer is "I can't remember" or "I don't have time," then you already know what your ROI is going to be. And no methodology in the world is going to change it.
The ROI of continuous improvement is not a function of what you buy. It's a function of what you do. Personally. Visibly. Consistently.
Methodology times leadership commitment squared. That's the formula. And you can't outsource the second variable.
So here's the question that separates leaders who build improvement cultures from leaders who just fund them:
Are you willing to put your own time on the line? Or are you just willing to put your budget on the line?
Because your people already know the answer. And they're acting accordingly.
If you want an honest assessment of where your CI programme actually stands, and what leadership shifts would move the needle, book a Discovery Call: Strategic CI Assessment at stormholt.org/products/architecture-session.
No pitch. No sales deck. Just a direct conversation about what's working, what isn't, and what it would take to get the ROI your programme should be delivering.
New to Stormholt? Start here — it locates your stage in minutes.
Building capability? Stage III — Skill — the tools, the courses, the simulations.