01 / UNDERSTAND
What is a service safari?
A service safari is an exploratory activity in which a designer uses a service and records the experience as it unfolds. It helps make touchpoints, transitions and practical conditions visible before deciding what to investigate further. Your experience is one situated account. It cannot stand in for the experiences of people with different knowledge, circumstances or access needs.
Why use Service Safari?
A team may discuss a service without having followed its ordinary path from start to finish. A safari makes details such as unclear arrival instructions, repeated information requests or useful reassurance available for discussion. Its value lies in specific records and better questions. A memorable encounter alone is not enough to diagnose a service or rate the people delivering it.
When to use it
USE IT WHEN
You are becoming familiar with a service or a context before planning deeper research.
The experience crosses physical and digital touchpoints that the team has not examined together.
You want to investigate how an analogous service handles a particular transition.
When to choose another method
Use User Interviews to learn how people describe their actual experiences and constraints.
Use Customer Journey Map when you need to synthesise evidence about a defined person's journey.
Use Service Blueprint when the question concerns hidden work, ownership or delivery dependencies.
What you’ll need
Choose a legitimate task, an accessible service and a start and end. Prepare prompts for actions, messages, waiting, handoffs and questions. Record context such as time, channel and prior familiarity. Respect service rules and ask permission before photographing or recording people. Avoid collecting personal information or creating unnecessary work for staff. If a route is unavailable to you, record that limit rather than pretending to have experienced it.
What a service safari records
Keep the elements that help answer your question and support a decision.
What you are trying to accomplish and where the exploration stops.
Time, channel, conditions and your prior knowledge.
Messages, spaces, objects and people encountered.
What you did and what happened next.
Your explanation or reaction, kept separate from the record.
What needs investigation with other people or evidence.
02 / PUT IT INTO PRACTICE
How to conduct a service safari
Keep evidence and assumptions distinct. Revisit your work when new information changes your understanding.
01
Frame the exploration
Choose a narrow task and the uncertainty behind it.
Explore collecting a reserved book from a library, from the collection email to leaving with the book.
02
Prepare a recording guide
Agree what to note and how to handle images and personal information.
Record instructions, decisions, handoffs and moments when you need help.
03
Use the service
Follow the ordinary route while keeping brief notes that do not disrupt the interaction.
Read the email, locate the collection area and follow the process for borrowing the book.
04
Separate the record
After the visit, distinguish events, personal reactions and possible explanations.
The email names a collection desk; no desk with that label was visible on the route you took.
05
Compare with context
Discuss differences between team accounts without averaging away conditions.
Another visit used a different entrance. Treat the route difference as relevant context.
06
Choose follow up research
Turn the most consequential uncertainty into an answerable question.
Investigate whether first time visitors can connect the email wording to the signs, and which routes they use.
Example: collecting a reserved library book
Illustrative scenario, not research findings. A designer receives a collection email for a reserved library book. The email refers to a collection desk, while the signs visible from the entrance refer to reservations. The designer asks a staff member where to go and then completes the collection.
The record identifies the wording difference and the request for help. The interpretation is that the connection between the message and the signs may be unclear. The team does not conclude that all visitors struggle. They plan to examine the route with people collecting for the first time, including those using another entrance, before choosing a change to the instructions.

03 / BELOW THE SURFACE
Below the surface: one visit is a starting point
Personal familiarity can make a service look easier than it is, while an unusual visit can make it look worse. Both effects matter when deciding what to investigate.
01 / RECORD
What actually happened?
Keep the action, wording and context together.
02 / PERSPECTIVE
What shaped your experience?
Record familiarity, route and available support.
03 / FOLLOW UP
Whose experience is missing?
Choose the next research question and participants.
Keep the conditions attached to the observation. In the library example, the record needs the entrance used, the wording seen and the designer's prior knowledge. Without those details, the team may turn a local mismatch into a claim about the whole service.
When comparing visits, ask which difference could plausibly explain the result: route, timing, available help or familiarity. A comparison with an analogous service should also identify which conditions would have to exist for its approach to transfer. This is a practical interpretation of the example, not a validated service score. Use the safari to shape subsequent research, and revise the initial account when new evidence conflicts with it.
Service Safari working canvas
Use page one to record the task, context and three moments in the service. Use page two to separate observations from interpretations, compare conditions and plan follow up research. The two page PDF contains 12 editable fields. Save a working copy in a PDF reader that supports forms.


Practical tips
Capture specific wording rather than a general impression of clarity.
Note helpful moments as well as friction.
Debrief soon enough to distinguish contemporaneous notes from later recollection.
Common mistakes
Treating the designer's reaction as a representative customer finding.
Copying an attractive touchpoint without checking the conditions behind it.
Inferring staff motives from a single encounter.
What you’ll get
A contextual record of the service, a set of provisional interpretations and focused questions for further research. Keep the original notes and the limits of the visit attached when sharing the findings.