Technology Doesn’t Deliver ROI. Your Business Does.
Technology creates capability. The return comes from what you're prepared and able to do with that capability.
I work with clients who are naturally concerned with the return on investment (ROI) of their digital transformation projects, yet the business case often treats ROI as something to prove before approving the investment. A figure is produced (usually dominated by savings, efficiencies or projected revenue) and then inadvertently gets forgotten once delivery begins.
At PHRONESIS, I believe in viewing ROI as a practical chain:
Investment → capability → changed behaviour and processes → measurable business outcomes
Most organisations concentrate on the first two, focusing on the process of buying and implementing the technology, but paying much less attention to the changes needed to convert its capabilities into results. That's why an implementation can be technically successful and still produce a disappointing return.
Let's run through a real-world scenario: you've implemented a new CRM, website or digital platform. The partner has delivered what was contracted, the system broadly works, yet adoption is patchy, data is unreliable, teams retain workarounds, and the expected benefits remain difficult to see. Leaders conclude that the technology has not delivered enough value.
Here's the challenge back:
Is the technology failing to deliver, or has the organisation not made the changes required to use what it bought?
The problem with asking “What's the ROI?”
It's a valid question but one that can be asked too narrowly or at the wrong moment. I frequently see ROI treated as a single financial number - projected savings are counted without establishing whether they can genuinely be realised; benefits are described too vaguely to measure; implementation is mistaken for transformation; responsibility for benefits quietly shifts to the technology or implementation partner, or nobody owns what the business itself must change.
Implementation can enable capability. The business must realise the benefit.
Good partners should help expose dependencies, challenge assumptions, and design for adoption, but they cannot decide priorities, create management discipline, or make people use information differently on the organisation’s behalf.
In reality, digital investment can create value through several lenses: financial performance, productivity and capacity, customer experience, strategic progress, operational effectiveness, and risk or resilience. Not every investment needs to demonstrate a return through every lens. Select the few outcomes that genuinely justify the investment, then define what each would look like in practice.
For every chosen outcome, ask:
What should become measurably better?
How does the technology enable that improvement?
What must the business do differently to realise it?
This creates a focused set of intended returns that can be translated into ownership, action and measurement, not an impressive but unmanageable catalogue of possible benefits.
Follow the benefit backwards
For each intended return, work backwards through the things that will make it achievable.
“The new CRM will improve retention” is not yet a measurable benefit, but it could be. Better data might allow the organisation to identify customers at risk of leaving, but someone must use that insight. The relevant team needs an agreed intervention process, with targeted contact happening early enough to make a difference. The organisation can then track whether renewal rates improve among that group and measure the income retained.
The return does not come directly from the CRM. It comes from the organisation using its capability to take better action.
Put the business on the hook before implementation begins
Before delivery even becomes a reality, the organisation needs to define:
The return: priority outcomes, baselines, measures and realistic timescales.
The business change: the processes, behaviours and ways of working that must change.
The requirements: the technology, data, training and investment needed to enable that change.
The ownership: who is accountable for realising each benefit and ensuring adoption.
Every expected benefit has both a technology dependency and a business dependency. If the business dependency is undefined, the benefit remains an aspiration, not a plan.
Technology changes what is possible. People determine what becomes normal.
The most important business dependency is usually people. A system can introduce new capabilities, but value only emerges when people use them consistently and change how work gets done.
That may require people to trust and use new data, give up familiar spreadsheets and workarounds, collaborate across previous functional boundaries, accept changes to responsibilities or authority, or adopt a process that initially feels less comfortable. These are not purely technology problems. They are clues that the business changes needed to realise value have not yet taken hold.
Training alone does not solve those issues. They involve incentives, confidence, habits, identity, management expectations and the surrounding operating environment. Adoption is not simply a post-implementation communications and training activity. It is part of how ROI is created.
Make measurement proportionate
Benefit measurement should provide useful evidence without becoming a cumbersome administrative exercise. Three principles can keep it proportionate:
Focus on what matters: Select a small number of material benefits and avoid measures that generate work but offer little insight.
Make comparison possible: Establish the baseline before implementation and use existing data wherever it is sufficiently reliable.
Look for progress as well as results: Combine leading indicators such as adoption, data quality and use of new processes with lagging outcomes such as income, retention, service performance or cost.
Give each benefit an owner, a realistic review point and an agreed way of assessing progress. Not every valuable outcome can or should be reduced to a precise financial figure; informed strategic judgement has a legitimate place.
If you wait for the ultimate financial result before checking whether value is emerging, you may discover far too late that the behaviours and processes needed to produce it never changed.
Timing changes the ROI conversation
Many organisations believe they have defined ROI because they have produced a business case.
Naming an expected benefit is not the same as making it executable.
The intended return should influence the transformation from the outset: how the solution is designed and configured, which processes must change, what data is required, what user acceptance testing (UAT) needs to prove, how people are prepared and supported, and who will own the benefit after launch.
There are three connected questions:
Before investment: Is this worth doing, and what must be true for the expected benefits to be realised?
During delivery: Are we building the right capability and making the necessary business changes?
After launch: Are people using it as intended, and are the expected outcomes beginning to emerge?
The benefits must be made executable early. Their assumptions, dependencies and progress must then be tested throughout delivery and after launch.
A business case may secure the investment. It does not, by itself, secure the return.
Now what?
The return on digital transformation isn't hidden somewhere inside the system waiting to be extracted. It's created through the decisions, behaviours, and operating changes that follow.
In the earlier scenario, patchy adoption, unreliable data, and persistent workarounds may indicate that the technology is underperforming, but they can also reveal that the business dependencies needed to realise the return have not been fully addressed.
For leaders embarking on or in the middle of a digital transformation effort, ask yourself these five questions:
What business outcome are we actually buying this technology to enable?
What must people and processes do differently for that outcome to happen?
Who in the business owns making that change real?
What evidence will tell us early whether it is working?
Are we prepared to invest in the organisational change as well as the technology?
If you’re planning a digital investment - or questioning why an existing one isn’t delivering - PHRONESIS can help you understand what is really getting in the way and what needs to happen next.
Comments