UK public sector productivity has remained below pre-pandemic levels, and the cost of closing the gap continues to rise. The scale of the challenge is well understood.
From Capita’s lived delivery experience, the issue is not a lack of effort. It is that time, cost and expertise are absorbed by how workflows, how decisions are made and how services are organised.Until those conditions are addressed within live service delivery, additional effort will continue to produce limited progress.
For leaders responsible for performance, assurance and outcomes, the challenge is structural. Productivity is not about asking teams to do more. It is about releasing capacity safely, strengthening control and enabling services to perform consistently under pressure.
Many public sector organisations are operating in a permanent state of reaction.
Escalations, manual workarounds and additional approvals become the default response to risk. Each intervention feels necessary. Over time, they combine to create services that are harder to manage. From our knowledge operating complex public services, this pattern is both common and repeatable. Controls are added in response to pressure, but when they sit outside workflow and data, they can reduce flow rather than protect it.
Approvals slow throughput. Additional checks increase exceptions. Workarounds introduce variation.
The result is a system where backlogs grow, delivery becomes less predictable and leadership effort is drawn into firefighting rather than improvement. This reflects a broader structural pattern, where organisations struggle to move beyond short term delivery long enough to address root causes. Without visibility and control embedded within services, reactive delivery becomes the default.
The organisations making credible progress are not starting with larger programmes. They are starting with a different question.
Where is capacity being lost?
This question is simple to ask but difficult to answer without operational visibility. Traditional reporting, budgets and headcount do not provide enough insight. Leaders need to understand how workflows and what activities cost to deliver in practice. This is the question that transformed the Accounts Payable function at the London Borough of Bexley. Before redesigning processes or introducing further automation, a clearer view of activity level cost was established.
Invoice processing time reduced significantly because of that visibility.
This is not an isolated case. Across finance and transactional services supported by Capita, similar proof patterns are visible. When organisations understand cost and effort at activity level, they can target change more precisely, reduce inefficiency and release capacity within existing services.
From our experience embedded in live services, productivity breakdown is consistently driven by three connected factors:
These are not isolated issues. They interact within live service delivery. When viewed together, they provide a clear and actionable picture of where capacity is being lost. This shared view allows operations, finance and transformation to align around evidence that supports decision making in practice.
Most organisations recognise the need for productivity improvement. The challenge is where to start. From Capita’s delivery experience, the most effective approach is structured and sequential, rather than large scale and immediate.
Improvement follows four stages:
This sequence reflects how change can be introduced safely and sustained over time. It ensures that automation and AI are embedded into governed services, where accountability and human judgement are already established. Across services supported by Capita, this sequencing consistently delivers more reliable outcomes than programme led transformation alone.
Each stage matters, but adoption determines whether improvement lasts.
Our experience is that productivity gains are sustained when change is embedded into day-to-day delivery, not delivered alongside it.
This means:
When improvements reduce operational burden, they are maintained. When they increase pressure, they are quietly worked around. This is why embedding change within live services is critical. It allows improvements to be tested, adapted and sustained in practice, rather than applied as separate initiatives.
The hardest part of productivity improvement is not analysis. It is taking the first step. The organisations making credible progress are not waiting for perfect data, new systems or large transformation programmes.
From Capita’s experience, they are:
This work begins within existing services, using available data and practical assumptions. Insight improves over time as delivery continues. Similar patterns are visible across multiple services supported by Capita. When organisations start small, build visibility and act early, they create momentum that can be sustained and scaled.
Productivity improves when organisations move from effort to control. From Capita’s lived delivery experience, this means:
Capita works within public sector organisations to deliver this in practice. By operating inside live services, we bring together operational insight, workflow optimisation and embedded automation to create measurable, repeatable improvements.
This is how structural challenges are turned into controlled, defensible progress.
Read our latest productivity whitepaper to see how organisations supported by Capita are strengthening control, releasing capacity and delivering better outcomes for citizens through practical, embedded change:
We consider how organisations can improve how work flows through services, removing the friction that quietly absorbs capacity.
Read more
Improve public sector productivity with better visibility, simpler workflows, automation and AI to release capacity and strengthen service delivery.
Read more
How AI improves public services through clearer, faster and more consistent citizen experiences, building trust through reliable, joined up support
Read more
Automation can accelerate productivity, but only when it’s embedded within stable, well understood services, not introduced as a standalone initiative.
Read more
Share