Designing Beyond The Screen: Why Service Thinking Matters

We might not go by the title of a service design studio, but the thinking that underpins it has long been woven into our approach to digital products.

It’s important to recognise that a successful product is rarely just a screen or an interface, it’s part of a wider experience. One that needs to work across departments, channels and real world conditions. That’s where service design thinking plays a role in what we do.

When we map out user journeys, create wireframes or run usability testing, we’re doing what many people think of as UX design. But our work rarely stops at the interface. Every product we design exists in a broader context: how people discover it, access it, use it, get support and how businesses deliver it behind the scenes.

Take a new onboarding flow for example. It might start with designing a clear, intuitive sign-up screen. But we’ll also look at and understand how people get to that screen in the first place. Is the process consistent across channels? Does it integrate with the CRM? What happens if someone drops off midway, do they get a nudge via email or is that a dead end? These questions go beyond UI. They touch systems, marketing, operations and the service as a whole.

That’s why we often find ourselves thinking about the whole ecosystem a product operates within. How teams interact with tools, how systems pass data between one another and how the experience holds up across touchpoints, even the ones that don’t have a screen.

And we don’t just stop at mapping out a better experience, we support clients in shaping the internal mechanics needed to deliver it. That might mean redefining handovers between teams, designing internal dashboards to manage a service or setting up processes to handle edge cases that the digital product alone can’t solve. We’ve worked with businesses where the success of a new feature hinged less on the feature itself and more on training and how internal teams positioned it.

This kind of thinking doesn’t always have a shiny UI attached to it, but it’s just as important. If you’re going to improve the user experience, you need to make sure the organisation behind it can deliver.

So while we might not produce service blueprints every week, or call ourselves service designers, our approach reflects many of the same principles. We think beyond features. We design across journeys and digital ecosystems. We consider the internal mechanics as much as the outward experience.

Digital products don’t live in isolation but sit within services, systems and human realities. And designing for all of that is what makes a product work.

‍