This is a practical guide to service design for UK charities. It is written for people who need to improve a service under real constraints: limited capacity, complex need, safeguarding requirements, and funder expectations.
A guide to charity service design
When a charity service is under pressure, the symptoms are usually obvious. Waiting lists grow. Staff and volunteers feel stretched. Quality becomes inconsistent. People drop out. Complaints rise. Outcomes become harder to evidence.
The hard part is identifying what is driving those symptoms, and what to change without breaking what still works.
Service design helps you do that. It gives you a practical way to understand how your service works day to day, where people get stuck, and what needs to change to improve outcomes. It’s not a glossy workshop. It is structured problem-solving that starts with the reality of people’s lives and the reality of delivery.
This guide sets out a straightforward approach you can adapt for one service, a whole programme, or a portfolio of services.
Quick start (if you only have two weeks)
If you only do one cycle, do this:
- Map the real service journey end to end (including waiting, handovers, and drop-outs).
- Choose one failure point to fix.
- Prototype one change in a small, low-risk way.
- Track what happened, decide what to keep, and iterate.
What we mean by service design
Service design is a set of methods for designing and improving services by:
- understanding people’s needs and behaviour in context
- mapping the end-to-end service, including handovers and constraints
- co-designing improvements with the people who use and deliver the service
- testing changes in small, low-risk ways before scaling
In the charity context, service design is most useful when it helps you make decisions about:
- who the service is for, and what you will not do
- what the service promise is (the experience and the outcomes you can realistically deliver)
- how the delivery model works (roles, capacity, process, information, safeguarding, partnerships)
- how you will learn and improve after launch
When you need charity service design (and when you do not)
Some issues can be fixed with small operational changes. Others need deeper redesign.
Charity service design is usually worth doing when you are seeing:
- repeated failure points (drop-outs, delays, complaints, safeguarding incidents, missed follow-ups)
- significant changes in demand or need (new referral routes, cost-of-living impacts, policy changes)
- a new funding model or contract (new outcomes, new reporting, new eligibility rules)
- quality concerns or inconsistent delivery across sites
- a delivery model that no longer matches how people actually use the service
If the service is basically working and you only need a clearer rota, a better referral form, or stronger handovers, you may not need a full redesign. You may need targeted service improvement.
A simple structure: the Double Diamond
A useful way to structure service design work is the Design Council’s Double Diamond. It describes four phases:
- Discover: understand the situation rather than assume the problem
- Define: decide what problem you are solving, for whom, and why
- Develop: explore and co-design possible solutions
- Deliver: test, iterate, and embed what works
The first “diamond” is about understanding the right problem. The second “diamond” is about developing and delivering solutions. The Design Council emphasises spending time with people affected by the issue, re-framing the challenge based on what you learn, and testing solutions at small scale before rolling out. (See more: Design Council: The Double Diamond)
Charity translation: If you skip Discover and Define, you will end up redesigning a service around what is easiest for the organisation, not what helps people. If you skip Develop and Deliver, you will end up with a report that does not change delivery.
A practical charity service design process
Step 1. Start with the service you actually deliver
Most charities can describe their service as they intend it to work. Fewer can describe how it works in real life.
Start by mapping what happens from the perspective of the person using the service, and from the perspective of the team delivering it. Notice where the real service differs from the intended service. That gap is often where quality and outcomes leak.
Do:
- run one mapping session with delivery staff and volunteers
- run one mapping session with a small number of service users (if appropriate)
- compare the “intended journey” to the “actual journey”
Output: a single end-to-end map that includes waiting, drop-outs, and handovers.
Step 2. Understand demand, need, and who the service is for
Clarity on who the service is for is one of the fastest ways to reduce pressure on the design and delivery of your services – and the charity and its workforce.
Look at:
- who is trying to access the service
- who is not accessing it, and why
- who is being turned away
- how needs present at different points in the journey
- where safeguarding or risk escalations happen
Be explicit about eligibility, pathways, and what happens when needs are outside your remit. This helps you avoid running a service that tries to be everything to everyone.
Output: a clear “service promise” statement, including boundaries and referral routes.
Step 3. Diagnose the constraints that shape day-to-day delivery
Service issues are often caused by constraints, not effort.
Common constraints include capacity, unclear roles, weak referral information, inconsistent assessment, lack of feedback loops, and processes that create delay. Identify the small number of constraints that cause repeated failure points, rather than trying to fix everything at once.
Charity-specific constraints to check:
- volunteer availability and training
- safeguarding responsibilities and escalation routes
- data collection and reporting burden (especially for funders or contracts)
- partner dependencies (e.g. statutory services, schools, prisons, housing providers)
- physical access (travel, opening times, digital exclusion)
Output: a short list of “design constraints” that any new service model must respect.
Step 4. Co-design improvements with the right people
Co-design does not have to be a big programme. It does need to be real.
Bring together:
- service users where appropriate, with the right support and safeguarding
- delivery staff and volunteers
- operational leads
- the people who hold constraints, such as finance, safeguarding, data, or partnerships
Research on co-design in the voluntary sector suggests awareness and understanding vary widely. It also flags a common gap: iterative prototyping, a central feature of design approaches, was rarely applied by voluntary organisations when designing services. Lam and Dearden (2015): Enhancing service development and service delivery through co-design
Output: a short list of prioritised ideas that have been shaped by users and delivery reality.
Step 5. Design the delivery model, not just the experience
A good service experience is supported by a delivery model that can be run consistently.
Describe what happens, when, and by whom. Define quality standards and decision points. Make handovers and information flows explicit.
If you expect partners to play a role, be clear what you need from them and what you will provide.
Output: a draft service blueprint or operating model, including roles, capacity assumptions, and key workflows.
Step 6. Prototype and test before you scale
Delivery involves testing out different solutions at small scale, rejecting those that will not work, and improving the ones that will. Design Council: The Double Diamond
Prototyping in charities can be lightweight:
- a one-day “new intake” pilot
- a new script for triage calls
- a revised referral form tested with three partners
- a different timetable for group sessions
- a new handover template for volunteers
The aim is to learn quickly and cheaply before you commit.
Output: evidence from small tests that shows what improves outcomes, experience, or delivery effort.
Step 7. Embed the change and build a learning loop
Redesign is only half the job. Embedding is where impact is won.
Support teams with simple tools, training, and routines. Build a light feedback loop so you can see what is working, what is not, and what needs adjustment.
This is often the hardest step in public and third sector contexts. Research on service design in public services highlights that tools often support customer understanding and concept design, but do not always support rooting and launching new services. Interviews also point to organisational decision-making and maintaining change as a major challenge. Vuontisjärvi (2015): Service design in the public sector
Output: a simple quality and learning loop that fits your capacity.
Tools you can use without turning service design into a ‘big project’
1) A one-page service snapshot
Answer these questions in one page:
- Who is it for?
- What need does it meet?
- What change do we expect for people?
- What do people do, and what do we do?
- What is the minimum viable service promise?
- What are the guardrails (safeguarding, eligibility, capacity, referral routes)?
2) A service user journey map
Map the journey from the person’s point of view:
- how they find you
- first contact and waiting
- assessment and onboarding
- delivery
- follow-up and exit
- what happens when needs change or risk escalates
Add pain points, drop-outs, and emotional highs and lows.
3) A simple service blueprint
Under the journey, capture:
- front-stage actions (what the person experiences)
- back-stage actions (what staff and volunteers do)
- support processes (data, finance, safeguarding, partnerships)
- handovers and decision points
4) A prototype log
Keep a running list of:
- what you changed
- what you expected to happen
- what actually happened
- what you learned
- what you will do next
Common pitfalls with charity service design
Designing the service without delivery reality
If the design is created without the people who deliver it, it will not stick. Include delivery staff early and treat operational constraints as design inputs, not inconveniences.
Treating co-design as consultation
A survey is not co-design. Co-design means service users and delivery teams shape the solution, not only comment on a draft.
Improving one part of the service while breaking another
Changes affect the whole system. If you improve assessment but do not improve handovers, you may simply move the bottleneck. Use a whole-journey view to avoid shifting problems around.
No quality or safeguarding lens
Many service failures are quality failures. Build in standards, safeguarding, and escalation processes. Make sure people know what to do when things go wrong.
Skipping prototyping
Co-design research in the voluntary sector has highlighted that iterative prototyping is not commonly used. Make it normal to test small changes before scaling. Lam and Dearden (2015)
What this can look like in practice
Northumbria University’s impact work describes how service design methods were used with charities, including work with Mind networks and local organisations. Examples include a co-designed service that helped people connect to their local community through volunteering, and embedding service design capability inside an organisation so teams could use design methods in day-to-day work. (See Northumbria University: Using service design to enhance the impact of charities)
A practical lesson from this type of work is that service design is not only a set of workshops. It is a capability. It becomes more valuable when an organisation can repeat it without external support.
Building service design capability in charities
If you want charity service design to stick, you need to support the people doing it.
A useful piece from the UK government’s design community highlights a simple pattern: find out what someone needs, offer support in formats that fit reality (not always meetings), and share resources when you do not have capacity for deeper mentoring. (See Design in government: How can you support people interested in service design?)
In charities, that translates to:
- a named sponsor who can unblock decisions
- protected time, even if small
- a “good enough” standard for artefacts
- a habit of testing and learning, not only planning
Sources
- Design Council: The Double Diamond
- Lam and Dearden (2015): Enhancing service development and service delivery through co-design
- Vuontisjärvi (2015): Service Design in the Public Sector: Role, Challenge and Good Practice
- Northumbria University: Using service design to enhance the impact of charities
- Design in government (2020): How can you support people interested in service design?
Next steps in charity service design
If you want support to improve a charity service or redesign a programme, find out more about our Charity Consultancy Services, including the types of programmes and services support we provide and common starting points.
For a sector reference on service improvement and quality, you may find SCIE’s resources helpful: Social Care Institute for Excellence
For most teams, the best starting point is simple:
- map the real service
- pick one or two failure points
- prototype one change in two weeks
- measure what happened, and decide what to do next