AI Productivity Is Not the Same as AI Value

Written by Athang Kale | Sep 25, 2026, 9:31:53 AM

AI Productivity Is Not the Same as AI Value

One of the more interesting lessons from the NHS England experience with generative AI is not simply how much time the technology can save.

It is what an organisation does with that time once it has been released.

The NHS’s large-scale Microsoft 365 Copilot experience reported average administrative time savings of around 43 minutes per staff member per day.

On the face of it, that is a compelling productivity signal.

But for any organisation considering AI at scale, the more important question is what happens next.

If a clinician gets that time back, does it translate into more time with patients?

If a service team becomes more productive, does it reduce waiting times or increase capacity?

If a manager spends less time on administration, does it create more time for decisions?

Or does the recovered capacity simply get absorbed by the next set of priorities?

That is where AI productivity starts to become an AI ROI conversation.

 

The value is in what happens next

We are getting very good at measuring what AI can save.

Minutes. Tasks. Emails. Documents. Lines of code.

But saving time is only one part of the equation.

The real value comes from what an organisation does with the capacity released.

For a clinician, it could mean more time with a patient. For a customer service team, more cases resolved. For a manager, more time spent on decisions rather than administration.

The productivity number may be the same.

The organisational value can be very different.

 

AI ROI is bigger than the licence costs

An AI business case cannot simply be a comparison between the cost of a licence and the amount of employee time saved.

There is the full cost of making AI work: implementation, integration, training, security, governance, adoption and ongoing support.

Then there is the value side.

Does the additional capacity help an organisation serve more customers? Reduce a backlog? Improve response times? Give specialists more time for complex decisions? Improve the experience of a patient or customer?

These are different outcomes, and they need to be measured differently.

A useful way to think about it is:

Investment → adoption → productivity → capacity → measurable outcome

The final step is often the one that gets lost.

 

Time saved is not automatically money saved

If an employee saves 43 minutes a day, the organisation does not automatically save 43 minutes of salary.

The employee is still employed. The work still exists.

What has potentially changed is capacity.

That capacity has value if the organisation can put it towards something that matters — handling more demand, reducing pressure on existing teams, improving service levels, avoiding future capacity constraints or allowing highly skilled people to spend more time on higher-value work.

That is why productivity and financial savings should not be treated as interchangeable.

 

The baseline matters too

A productivity figure also needs context.

How was the baseline established? Which roles and workflows were measured? Over what period? And did the benefit remain after the initial adoption phase?

A productivity gain demonstrated during a pilot is useful.

A productivity gain that is still visible 12 or 24 months later, and can be connected to a measurable business or service outcome, tells a much more useful story for an executive team making investment decisions.

Durability is part of ROI.

 

Sometimes the return is human

There is another dimension to AI value that can be easy to overlook.

A Swedish study examining an AI medical scribe across healthcare settings analysed more than 236,000 clinical notes and reported around a 29% reduction in estimated documentation time, while also considering clinicians' experience and their ability to remain present with patients.

That matters.

Not every AI benefit needs to appear as a reduction in headcount or operating cost.

Sometimes the return is giving a professional more time to do the work that requires their expertise, judgement and human interaction.

In healthcare, that might mean more time with a patient.

In financial services, it could mean more time understanding a client's needs.

In the public sector, it could mean more time focused on the citizen rather than administration.

The economics still matter. But so does the outcome.

 

An AI shopping list is not a strategy

This is also why I am cautious about AI roadmaps that become little more than shopping lists.

Copilots. Customer 360. AI search. Code migration. Assistants. Automation. Agents.

There is nothing inherently wrong with any of these.

The question is whether they are solving the right problem.

A more disciplined approach starts with the business or service outcome, then the workflow, then the opportunity for AI, followed by the people, safeguards, investment and measurement required to make it work.

Sometimes the answer will be AI.

Sometimes it will be better data.

Sometimes it will be process improvement.

And sometimes the right decision will be not to use AI at all.

That is not resistance to AI.

It is simply disciplined investment.

 

The real challenge begins after the pilot

We are getting much better at proving that AI can work.

The harder part is making it work consistently, safely and economically at scale.

That requires more than deploying a model or buying another enterprise licence. It requires adoption, integration, information protection, governance, cost management and — perhaps most importantly — a way of measuring whether the original business case is actually being realised.

That is the difference between an AI experiment and an AI capability.

 

Where ClairX partners for value

For CIOs, CTOs and CDOs, the challenge is increasingly not “Where can we use AI?”

It is “Where will AI create meaningful enterprise value and how do we make that value real?”

This is where ClairX partners with leadership teams.

We connect business priorities, data, AI, architecture, governance and execution to help organisations move from AI ambition to measurable outcomes.

That can mean identifying and prioritising the right use cases, designing the architecture and data foundations around them, establishing the governance needed to scale safely, and supporting the transition from pilot into real operational environments.

The proposition is simple:

Prioritise what matters. Build what scales. Measure what delivers.

Because the hard part of enterprise AI is rarely the demo.

It is making the economics work, embedding AI into real workflows and being able to demonstrate months later that the value promised was actually delivered.

That is where AI strategy becomes an enterprise capability.

And where pilot to production becomes the beginning, not the destination.

 

AI productivity is easy to measure. AI value is what drives business transformation. The organisations that succeed with AI will be those that focus not just on efficiency gains, but on creating measurable business outcomes. If you're ready to turn AI initiatives into sustainable value, let's start the conversation now.