Are Organisations Measuring Whether Their Transformation Investments Are Actually Working?

Technology investment by Australian firms has increased by almost 80% over the past decade, according to the Reserve Bank of Australia. Software alone has grown from around 6% of private business investment in 2014–15 to 10.5% in 2024–25. The pressure to demonstrate value is increasing with the investment.

Gartner found that 94% of Australian and New Zealand CIOs identified improving operating margins as the most critical outcome from digital technology investment in 2025, up from 48% the previous year. Demonstrating the business value of IT was also identified as a priority by 52% of CIOs.

The latest Australian Bureau of Statistics data adds another dimension. 74% of innovating Australian businesses reported benefits from their innovation activity in 2024–25, including increased revenue, improved customer service and increased productivity. That's encouraging. But 14% reported that no benefits had been achieved, while another 11% said it was too early to measure the benefits.

For executives sponsoring transformation, that's the uncomfortable part of the conversation. A business case can make a compelling promise. A program can be delivered successfully. A new platform can go live. None of those things, on their own, prove that the investment created value.

The gap between delivery and value

Transformation programs are very good at producing evidence of activity. There are roadmaps, milestones, dashboards, steering committees, risk registers and status reports. By the time a program reaches implementation, an organisation can usually tell you exactly how much work has been completed.

Ask what value has actually been created, and the answer can be less clear. We've seen this happen repeatedly. The program is under control. The implementation is progressing. The steering committee is comfortable with the status. But somewhere along the way, the original reason for making the investment has become less visible. Nobody has decided that the benefits no longer matter. Delivery simply becomes the dominant conversation.

And once that happens, the organisation can end up optimising for completion rather than value.

A completed program isn't necessarily a successful transformation

This distinction sounds obvious. It has significant implications in practice.

A technology implementation can be delivered on time without improving business performance. A redesigned process can be implemented without changing how people actually work. A transformation can achieve its milestones while delivering substantially less value than the business case anticipated.

That doesn't mean the program failed. It means delivery and value need to be managed as two connected, but different, disciplines. The first asks: are we delivering what we said we would? The second asks: is what we're delivering creating the outcome we invested in? Executives need visibility of both.

Benefits need an owner

One of the most persistent problems with benefits is that everyone supports them, but nobody quite owns them. The program team can deliver the capability. Technology can implement the platform. The transformation office can coordinate the work. But the business outcome often depends on decisions outside the program itself.

If a new platform is expected to reduce operating costs, who is responsible for actually removing the cost? If a transformation is expected to improve productivity, who changes the way the organisation manages performance? If new technology creates additional capacity, who decides how that capacity will be used?

Those aren't project management questions. They're business questions. And they need an owner.

Start with the outcome

A benefits register isn't the answer. A long list of aspirational benefits, each with a green status, doesn't create accountability. The useful questions are much simpler.

• What are we actually trying to change?
• What does success look like?
• Where are we starting from?
• Who is accountable for the outcome?
• What needs to happen for the benefit to be realised?
• How will we know when it has happened?

The discipline is in making those answers specific enough to influence decisions. That becomes particularly important when the transformation doesn't go according to plan — because it rarely does.

Keep value in the conversation when things change

Scope changes. Budgets move. Priorities shift. A program that looked compelling eighteen months ago can look very different when the market, organisation or technology landscape changes. This is where benefits management becomes more than reporting.

• If an initiative is delayed, what happens to the expected value?
• If investment increases, does the business case still stack up?
• If scope is reduced, which benefits disappear with it?
• If adoption is lower than expected, what does that mean for the original return?

Without a clear view of benefits, these decisions are often made based on delivery pressure alone. With one, executives can make decisions based on the value the organisation is trying to protect or create.

The investment doesn't end at go-live

This is where many transformation programs become vulnerable. The project finishes. The team moves on. The organisation celebrates implementation. But the benefits may still be months or years away.

A new system may require behaviour to change before productivity improves. A new operating model may take time to embed. Technology may create capacity that the organisation hasn't yet learned how to use. Go-live is an important milestone. It isn't the finish line.

The RBA's research into technology investment makes this point particularly well. Its interviews with 105 medium and large Australian firms found that the productivity effects of technology can take time to materialise, with firms highlighting the importance of successfully embedding new technology.

That has a practical implication for transformation leaders: the period after implementation deserves as much attention as the period leading up to it.

Value is ultimately a leadership issue

Benefits realisation is sometimes handed to a PMO or treated as a reporting requirement. That misses the point.

The executive team made the investment. The executive team needs to be able to see whether the investment is delivering. That doesn't mean executives need another dashboard. It means they need a clear line of sight between strategy, investment, delivery, adoption and business outcome.

When that connection remains visible, transformation becomes easier to manage. Leaders can challenge assumptions. Reallocate investment. Intervene when benefits are at risk. Stop initiatives that no longer make sense. Most importantly, they can distinguish between a program that is busy and a transformation that is actually working.

The real test comes afterwards

The measure of transformation isn't the quality of the business case. It isn't the number of milestones achieved. It isn't even whether the technology went live successfully. The real test is what changed afterwards.

• Did performance improve?
• Did customers notice a difference?
• Did people work differently?
• Did the organisation build new capability?
• Did the investment deliver the return that justified it?

Australian organisations are continuing to increase their investment in technology and innovation. The expectation from boards and executives is increasingly clear: those investments need to translate into business performance.

At MethodWerx, we help organisations keep that connection intact — defining the value transformation is intended to create, establishing accountability, tracking progress and helping ensure the benefits don't disappear once delivery begins.

Because transformation isn't successful when the project is finished. It's successful when the organisation gets the value it invested for.