Is this useful? Effective Service Delivery in the UK

By Lina Jahidi

At Oxford Insights, our delivery work is built around one question that sounds simple but is surprisingly easy to lose sight of: Is this actually useful?

That’s the question our User Research team asks at every stage of a project. As part of our multidisciplinary UK delivery teams, our researchers work alongside business analysts and service designers to make sure that the people who will actually use a service are never an afterthought.

We sat down with the team to talk about what good user research looks like in practice.

A fresh pair of eyes

One of the quiet strengths of our team is how much value comes from bringing in researchers who don’t yet have entrenched assumptions about a given domain. As one of our user researchers puts it:

“As a Junior UR, you don’t have a pre-conceived idea of what the problems or challenges could potentially be, so you might actually spot more things than someone who’s been in the system for years.”

This outside perspective matters. When people have worked within a system for a long time, certain pain points can start to feel fixed and unchangeable, just part of how things are. A fresh set of eyes, combined with genuine curiosity and direct conversations with users, can help overcome obstacles that have been quietly accepted for years. It helps teams rediscover what’s actually possible.

Keeping the human in the room

Of course, any project eventually runs into the realities of budgets and technical constraints. When those conversations start to dominate, it’s the User Research team’s job to bring things back to the people the service is being built for.

There’s a practical case for this too, not just a moral one:

“Keeping user needs at the forefront of your design and planning is essential for meeting GDS standards and passing Alpha and Beta service assessments. You need to demonstrate that you’ve meaningfully engaged with users and made changes based on their feedback.”

Beyond compliance, there’s a straightforward business argument: building the right thing the first time saves significant time and resources down the line. A quick fix that users don’t engage with will always cost more in the long run.

Being realistic about research

Putting users at the heart of the service is the end goal, but good user research also means being honest about the constraints. Client time and goodwill are finite resources, and an effective User Research team knows how to deliver insights without asking for more than is reasonable. It sometimes means being pragmatic: reusing existing research when valid, making considered decisions with limited data, or knowing when a quick round of targeted testing will answer the question just as well as a full research cycle. 

Bringing the team with you

User research is only valuable if it shapes what gets built. To make sure findings don’t just become interesting stories that gather dust, our team involves developers and designers directly in research sessions.

“I like to make sure that everyone on the project, including the build and design team, sits in on user research sessions. It lets them observe how users engage with a process first hand, and gives essential context to the rationale behind what’s being delivered.”

Shared observation builds shared understanding. When the whole team has heard a user struggle with the same thing three times in a row, prioritisation becomes a much easier conversation.

Hearing it work

The most rewarding moments in user research are when users tell you, in their own words, that something has landed. On one recent project, feedback included users saying that a service like this had long been needed, and that they knew exactly where in their day-to-day work they’d rely on it. Others flagged that it was more accessible than tools they had used before.

Most meaningfully:

“Users reported that they felt like they had been kept involved at all stages of the design process, and that their feedback had played a part in contributing to the overall design.”

In other words, users felt that this wasn’t just a service that works technically, but one that they felt ownership of; in a real sense, they had helped build it.

Building for the long term

Good user research doesn’t stop when the delivery team hands over a service. Part of the work is making sure that what’s been built can be maintained, adapted, and improved without the original team in the room.

Handover documents should capture unmet user needs alongside the decisions that were made: the pain points that were identified but couldn’t be addressed within the current scope or the feedback that came in too late to act on. This gives whoever picks the service up next a genuine head start,  a record of where the gaps are and where the next phase of work should focus, rather than having to rediscover it all from scratch.

It may cost more upfront, but it’s what keeps a product alive and genuinely useful long after launch.

Final thoughts

Only by considering users from the very start can we create a service that fits seamlessly into their lives. By asking the question ‘Is it useful?’, our team ensures that user needs inform every decision. Ultimately, the best outcome for a User Research team is that the user doesn’t notice the research at all, but feels intuitively that a service was built around and for them – because it was.

Find out more about the Delivery Services we offer at Oxford Insights, including user research.

Photo by David Travis on Unsplash