Menu

UX

Service Safaris

A practical UX and service design method for experiencing a service first-hand so teams can spot friction, gaps, and inconsistencies from the outside in.

How to use service safaris to experience a service directly, build empathy within teams, and uncover practical issues across channels and touchpoints.

4 min read

What it is

safaris are a UX and method where teams experience a product or service first-hand by going through it as a user.

This can involve using the directly, interacting with support, visiting physical locations, or testing different .

The aim is to observe and experience the journey in a real-world , rather than relying only on or assumptions.

It helps teams uncover issues, inconsistencies, and that may not be visible from the inside.

The goal is to empathy and identify opportunities for improvement through direct experience.

Service safaris are most useful when teams need to stop imagining the experience and start feeling what it is actually like from the user side.

When to use it

Use this method when you want to understand the experience from the outside in.

It is most useful when:

You are reviewing an existing service
You want to build empathy within teams
You are identifying issues across touchpoints
You are working on multi-channel experiences
You need quick, practical insight

It is less useful when:

You need deep behavioural or cognitive insight
The service cannot be easily accessed
You require structured or validated research
Service safaris are often used alongside journey mapping and usability testing.

Key takeaway

Use service safaris when direct experience will help the team spot issues faster and build a more grounded understanding of what users actually go through.

How to run it

Set up properly

Be clear on the you are experiencing, the to use, and what you are looking for. A safari without a question is a shopping trip.

Go as a real customer, paying real money where relevant. Staff behave differently when they know they are being assessed.

Run the method

A safari means experiencing a service end to end as a customer does. It is the cheapest way to first-hand understanding and works on competitors as well as your own service.

  1. Go through the end to end, including the parts that are inconvenient.
  2. Use multiple where they exist (web, app, phone, in person) and note where they contradict each other.
  3. Interact with real and real support rather than test accounts, which behave differently.
  4. Capture , issues and reactions as they happen, including how you felt at each point.
  5. Document the experience in the moment. Written up afterwards, it becomes a tidy narrative and loses the .

Record your emotional reaction as well as the facts. The irritation you felt waiting on hold is the finding, and it will have faded by the time you get back to your desk.

Capture and make sense of it

The value comes from direct experience. After the safari, document:

  • The experience as it happened, with timings
  • points and where they occurred
  • Inconsistencies between
  • Comparison with competitors, if you ran the same safari on theirs

Use this to empathy quickly and to find obvious failures. It is not representative, and it does not need to be to be useful.

What to look for

Focus on:

Experience: how it feels to use the service
Friction: where things don’t work smoothly
Consistency: across channels and touchpoints
Gaps: missing or broken parts of the journey
Expectations: where reality doesn’t match what’s expected

Where it goes wrong

Most issues come from:

It’s useful, but it’s not the full picture.

Using a test account, which behaves nothing like a real one
Announcing yourself, at which point staff behave differently
Writing it up afterwards, once the friction has faded
Treating one person's experience as representative
Skipping the inconvenient parts, which is where the finding is

What you get from it

Done properly, this method gives you:

First-hand experience of what you are asking people to do
Friction recorded with timings, as it happened
Contradictions between channels
Empathy that a report does not produce

Key takeaway

It helps you see your service as users actually experience it.

Get in touch

If this sounds like something you need, we can help you run service safaris and uncover what your users are really experiencing.

No guesswork. No assumptions. Just real insight from real interactions.

FAQ

Common questions

A few practical answers to the questions that usually come up around this method.

What are service safaris in UX?

They are a method where teams experience a service first-hand as users.

When should you use service safaris?

Use them when reviewing or exploring a service.

What is the benefit of service safaris?

They provide direct insight and build empathy.

Are service safaris enough on their own?

No. They should be combined with user research.

Do service safaris improve UX?

Yes. They help uncover real-world issues quickly.

Quick take

If you want to experience your service the way users do, go through it yourself.

LET'S WORK TOGETHER

Ready to improve your product?

UX, research and product leadership for teams tackling complex digital services.

Previous feedback

I had a fantastic experience working with Andy. One of his most impressive achievements during our time at NHS HEE was masterminding a deeply complex information architecture for a new platform that brought together a large number of legacy websites.

Will Parkhouse

Senior Content Designer