Service Design

Technology that doesn't fit how people work doesn't get used

Most products are designed from the inside out. Our Service design works the other way. We start with the people who'll use it, map what they actually need and work back to what should be built. The result is something that earns adoption rather than demanding it.

Book a consultation
Problem
CEO Image
CEOs/CTOs

Why does this matter and what strategic job does it do for me?

Every organisation has a version of how its products and services work. Users have a different one. That gap is where adoption fails, where support costs accumulate and where good ideas quietly die. Most technology projects never close it because they start with a solution and work backwards to the user.

Solution

When you design around your users, everything that follows is easier

We put users at the centre of every decision so what gets built is something people can actually use, understand and trust. The result is higher adoption, fewer post-launch changes and a product that delivers what it was meant to.

The Service Design challenges we help organisations solve

The Service Design challenges we help organisations solve

Service design is most valuable when technical delivery alone won't resolve what's going wrong:

  • A product that isn't being adopted despite working as intended

  • User journeys that create friction, drop-off or workarounds teams have learned to live with

  • Stakeholder disagreement about what to build or who it's for

  • Assumptions about user needs that haven't been tested against reality

  • A service that touches multiple teams, systems or touchpoints and lacks a coherent end-to-end experience

  • Pressure to deliver quickly without a shared understanding of what success looks like

  • Business objectives that quietly undermine the user experience, where what the organisation wants from an interaction and what makes it easy for the user are pulling in different directions, such as capturing customer data during a purchase journey in a way that increases friction and reduces conversion

What we deliver

Service design at The Curve is a focused, practical engagement built around a specific product, service or user journey. It's distinct from our broader Discovery process in that it centres on the end user rather than the wider technology landscape.

Journey mapping

We map the end-to-end experience from the user's perspective, across every touchpoint and interaction. This surfaces where the journey works, where it breaks down and where the greatest opportunity for improvement sits. Journey maps become a shared reference point for the whole team.

Service blueprinting

Alongside the user-facing journey, we map the processes, systems and teams that support it. This connects the experience users see with the operations that deliver it, making it possible to identify where friction originates and where changes will have the most impact.

Concept development and prototyping

e translate research and mapping into early concepts and prototypes tested with real users before any significant development investment is made. This reduces the risk of building the wrong thing and gives stakeholders a tangible view of what the solution could look like.

Design principles and service standards

We establish the principles that should guide design decisions throughout delivery. These give product and engineering teams a consistent framework and help ensure that as the product evolves, the user experience stays coherent.

Handover to delivery

Service design feeds directly into product backlog definition, technical scoping and engineering. The outputs are practical and delivery-ready. We work with your teams to ensure the insight translates into what gets built.

What sets The Curve apart

We start on the outside and work in. That means understanding the people who'll use a product before considering how it should be built, so the insight we generate is grounded in what's technically feasible and commercially realistic from the start. Our designers work alongside engineers, product leads and data specialists, not separately from them.

We identified friction in the Schools Plus booking flow early, before significant development investment was made. The changes that followed improved conversion and avoided costly rework.

On Swaya, the design challenge wasn't just building an app students would use. It was balancing the need for meaningful feedback with the risk of making it feel like another chore. Two tensions shaped the design. First, how to avoid survey burnout. Second, how to prevent bias, whether from peer pressure or timing, like students rating homework poorly on a day a big assignment lands. The solution was to randomise and distribute questions across the student population over time. Each student gets different questions, removing the influence of peer pressure, and responses build up gradually rather than reflecting a single shared moment.

In each case, the design work didn't slow delivery. It made it more focused, more efficient and more likely to produce something that actually worked.

Our case studies

Frequently Asked Questions

Let's build together

We're always eager to connect and explore how we can contribute to your journey. Reach out to us and let us know how we can assist you.

Call us Mon-Fri 9-4:30pm

+44 (0) 114 303 4070
Get in touch

We would like to contact you about our products and services. If you consent to us contacting you for this purpose, please tick below.

Review our Privacy Policy.