One of the biggest reasons public sector change struggles is surprisingly simple.
Solutions are often decided before the problem is fully understood.
A new programme is announced. A policy commitment is made. Tech is procured. Delivery teams are then asked to implement it.
Only later do the harder questions emerge:
- Will people actually use this?
- Does it fit into how services work day to day?
- What barriers exist for staff?
- What happens across the whole service journey?
- Have we solved the right problem?
By that point, changing direction becomes expensive and politically difficult. We keep investing in something because of the time and effort already put into it.
Premature certainty creates risk
Public services operate in complex environments.
People’s lives are messy. Needs overlap. Systems interact with one another in ways that are often invisible until delivery begins.
But many public sector processes still reward certainty upfront:
- fixed plans
- predetermined requirements
- rigid timelines
- false assumptions
That creates pressure to move quickly towards solutions before enough is understood.
The intention is usually good: Ministers want progress, organisations want clarity, teams want to reduce uncertainty.
But certainty too early in the process often creates more risk, not less. It creates the illusion of progress which we pay for later with services that do not work for the public, missed targets, and expensive workarounds for staff.
Understanding the problem properly saves money
Starting with problems does not slow delivery down.
It helps avoid wasting time and money solving the wrong thing.
This is where user-centred design becomes important. Not as a branding exercise or a layer added at the end, but as a practical way to reduce delivery risk.
Good research helps teams understand:
- where people struggle
- where services break down
- what creates avoidable demand
- where staff experience friction
- which assumptions are wrong
Sometimes the findings are small but powerful.
A clearer letter, a simpler form, better appointment information, fewer steps in a process.
These changes can have a significant operational impact at scale.
When content designers at Digital Health and Care Wales redesigned Covid vaccine letters from two double-sided pages to one, they reduced printing costs while making the information easier to understand. A small change to a single interaction becomes meaningful when repeated across an entire health system. The redesign saves 4p per letter, and if they match the number of letters sent last year, that’s a saving of £41,599.48.
Clearer communication can also reduce follow-up calls, confusion and missed appointments. The value is cumulative.
People experience services as a whole
One challenge in government is that services are often designed organisationally rather than experientially.
Teams focus on their part of the process: their department, their policy area, their system.
But people experience services differently.
They experience the entire journey:
- finding information
- understanding what to do
- proving eligibility
- attending appointments
- repeating information
- moving between organisations
This is where hidden complexity often emerges.
A process that makes sense internally can still feel fragmented and exhausting to the public.
Starting with real experiences helps expose these gaps early.
Frontline staff often know where the problems are
Some of the best operational insight already exists inside public services.
Frontline staff regularly see:
- where people become stuck
- which processes create frustration
- where systems duplicate effort
- what generates avoidable demand
The Bevan Commission’s recent Silly Rules initiative highlighted this clearly. Hundreds of staff identified everyday processes, habits and administrative barriers that waste time and make care harder to deliver. Many of the examples were not major policy failures, but small operational frustrations repeated every day across the system.
But too often, this insight enters the process late, after key decisions have already been made.
Modern delivery approaches bring policy, operational staff, researchers, designers and digital teams together much earlier. That shared understanding helps organisations make better decisions before committing significant time and money.
Wales has an opportunity to make better decisions earlier
One of the most valuable things governments can do is create space to understand problems properly before committing significant time and money to solutions.
That means:
- researching real experiences
- testing the riskiest assumptions early
- understanding operational pressures
- identifying risks before scaling change
- improving services incrementally rather than waiting for large programmes to finish
These approaches help organisations learn faster and reduce expensive mistakes later.
Starting with problems does not reduce ambition. It increases the chances of delivering change that works in practice. Too often, policy is developed at a distance from the people delivering and using services, with operational realities only becoming visible once implementation has begun. By that stage, making fundamental changes is slower, more expensive and politically harder.
A simple place to start: before launching a new initiative, ask what evidence exists that the problem has been properly understood — not just politically, but operationally from the perspective of the people running and using the service. That understanding is often the difference between change that sounds good on paper and change that improves people’s lives.
