Connecting policy, delivery and user needs to deliver better public services

Our approach has evolved through experience rather than being developed as a formal methodology. And so, we've found ourselves returning to a number of recurring practices. 

Partnering with policy teams early 

One of the biggest lessons we've learned is that user-centred design can add value long before delivery begins. On a recent programme exploring a future national careers offer, we worked across policy, digital, commercial and delivery teams to understand how a manifesto commitment could translate into a viable service proposition. 

Rather than starting with solutions, we focused on understanding the wider system, exploring delivery options, identifying assumptions and creating a shared picture of opportunities and constraints. This helped create stronger alignment between policy ambition, delivery feasibility and user needs, while informing future procurement and delivery decisions. 

Exploring possibilities before committing to solutions 

Policy teams are often required to make decisions in conditions of uncertainty. Traditional policy processes can make it difficult to understand how those decisions might play out in practice. 

Design approaches such as service mapping, speculative concept design and testing and scenario exploration can help teams visualise possible futures before significant commitments are made. 

We've found this particularly useful when dealing with complex services involving multiple organisations, delivery channels or user groups. Rather than debating abstract policy options, teams can explore how different choices might affect people's experiences and operational realities. 

Connecting policy intent to operational reality 

One of the recurring challenges we encounter is that policy decisions often have implications far beyond the digital service itself. Operational teams, support services, compliance functions and third-party organisations all play a role in delivering outcomes. 

On a large-scale government transformation programme, we used programme-level service blueprinting and internal journey mapping to help teams understand how policy decisions would affect customer support, compliance operations and assisted digital services. This work highlighted dependencies, ownership gaps and inclusion risks that might otherwise have remained hidden until much later in delivery. Importantly, it also ensured that non-digital experiences were considered alongside digital ones. 

On another government digital programme, we used ecosystem mapping to visualise all of the systems, stakeholders and users intertwined together, and how they would be affected by policy level decisions. This also allowed us to highlight infrastructure gaps, dependencies and interoperability risks across the entire programme, so that policy, operational and digital interventions can be focused on the areas of highest impact.  

Creating reusable service patterns 

As our work matured, we began noticing that many policy-to-delivery challenges were recurring. Different teams were often trying to solve similar problems in isolation. This led us to explore the role of service patterns as a way of capturing and sharing learning across services. 

On a programme of work, where we were looking at embedding enterprise-wide initiatives to reduce fraud and error, we started by mapping out the building blocks of all of the department’s services and the smallest interactions that end users have with the services. This then helped us map out where and how in these interactions fraud and/or error could occur, therefore enabling us to develop a scaffolding of interventions and design principles at crucial junctures of service-user interaction. 

These building blocks of services, are more commonly referred to as Service Patterns across government. Service patterns help teams move beyond individual user journeys to identify common approaches for delivering policy intent consistently. They create shared understanding between policy, delivery and operational teams while reducing the need to repeatedly solve the same problems. We've found they can be particularly valuable when organisations need to scale delivery across multiple services or programmes. 

Supporting evidence-based investment decisions 

User-focused policy design can also play an important role in shaping business cases and investment decisions. By bringing together user research, service level data, operational insight and service design evidence, teams can make more informed decisions about where investment is likely to create the greatest value. This helps move conversations beyond assumptions and towards a clearer understanding of impact, feasibility and risk. 

In our practice, we’ve fostered user research working closely, not only with designers, policy and operational stakeholders, but also with data performance analysts. Co-designing approaches such as value frameworks enables teams to identify where policy and service changes are likely to deliver the greatest benefit for users, operations and the organisation. By combining qualitative and quantitative evidence, user-focused policy design brings the right people and insights together earlier, helping teams test assumptions, understand the likely impact of policy options, and make more informed investment decisions grounded in user need, operational reality and organisational outcomes.