Service design that connects users, teams and systems

Look beyond the individual screen

A customer may experience one service while your organisation sees several departments, suppliers and systems. Problems often emerge between them: information is entered twice, an approval stalls, or a user receives conflicting instructions from different channels.

Service design makes those relationships visible. We work with businesses, non-profits and government agencies to understand how a service operates today and what a workable alternative would require. That includes the staff who deliver it and the policies, data and technology they depend on.

Map the experience and the work behind it

We bring together user research, stakeholder workshops and operational knowledge. Journey maps describe what people are trying to do; service blueprints connect those moments to the teams, processes and systems that support them.

The work identifies where an issue needs a software change and where a clearer responsibility, content change or simpler process may be more useful. We explore proposed changes with the people who would use and run the service before recommending a delivery plan.

Outputs are agreed around your decision. They can include a current service map, a proposed operating model, prototypes and a prioritised set of improvements. Dependencies and unresolved questions stay visible, particularly where several teams must act together.

Connecting digital change with frontline work

For Trussell, we researched how staff, volunteers and referral agencies used the existing foodbank service. The work uncovered needs beyond the original data-gathering brief, including delays in registering agencies and limitations in where vouchers could be redeemed.

The resulting system connected changes to the interface with changes to the referral process. Prototype testing, training materials and a staged rollout supported the move towards digital vouchers. The case illustrates why a useful service improvement considers adoption as well as software.

Does service design always lead to a new system?

No. An existing platform may be capable of supporting a better process. We assess options before recommending a build and explain where a change depends on people, policy or other suppliers. Where the immediate problem is a screen or interaction, UX design may be a more focused starting point.

Who should be involved?

We agree participation around the service: users, frontline staff, product owners, operational leads and relevant technical specialists. If their needs are not yet understood, user research can establish the evidence needed for the design work.