Role play (service role-playing)
Act the service out in a room, and the gaps you could not see on paper start to show.
- Time
- 40 min
- People
- 4–6
- Kind of work
- Test
In short
Service role play is a quick way to test a service idea by acting it out. You assign roles such as customer, front-line employee and back-office officer, run one realistic scenario, and watch for moments where the service stalls or confuses. Observers record those breakdowns, not how well people act. A session takes about 40 minutes.
What it is
Many service problems sit between people: in a handover, a phone transfer, a question nobody can answer. These are hard to see on a process chart. When you put real bodies in a room and ask them to play the parts, the gaps become obvious. The customer waits too long. The employee does not have the information. Two people both think the other one will call back.
Role play is cheap and fast. You need a scenario, a few props and people willing to act for ten minutes. It works well after a storyboard, because the storyboard gives you the sequence and role play shows how it feels to live through it. It is a test of the service, never of the people playing it, and the facilitator should say this clearly at the start.
When to use it
Use it when
- You are designing a new counter, phone or home-visit service and want to check the flow before training staff.
- A service involves handovers between people or teams.
- You want front-line employees to shape the design with their own experience.
- You need to test wording for a difficult conversation, such as refusing a request or delivering bad news.
Skip it when
- The service is fully digital with no human contact. Use a paper prototype.
- The scenario involves real trauma or sensitive personal situations that could distress participants. Use a written walkthrough instead.
- People feel unsafe in front of their managers. Fix that first, or run it without managers in the room.
You need
- Time
- 40 minutes for one scenario played twice, plus debrief
- People
- 3 to 4 actors, 1 to 2 observers and a facilitator
- Materials
- A written scenario card for each role, simple props (a desk, a phone, a form, a ticket), name labels for each role, an observation sheet
How to run it
Step 1: Write one realistic scenario
Base it on research or real cases. Include who the customer is, what they want, what they bring, and one complication, for example a missing document. Keep it to a few lines. One scenario played well teaches more than four played quickly.
Step 2: Assign the service roles
Give each actor a role card: customer, front-desk employee, back-office officer, supervisor on the phone. Each card says what that role knows and what they are allowed to do. Mix it up: ask an employee to play the customer, and someone from policy to play the front desk.
Step 3: Set up the space
Arrange the room roughly like the real setting: a desk, a chair for waiting, a phone at the back. Give the observers an observation sheet with four columns: role, situation, action, observation. Tell everyone that you are testing the service, not the actors.
Step 4: Run the scenario once
Start the clock and let the actors play it through without interruption, usually 5 to 10 minutes. Actors should stay in role and respond as that person would. Observers write down every moment where someone hesitates, lacks information, repeats a question or waits.
Step 5: Pause and debrief the breakdowns
Ask each actor: 'Where did you feel stuck?' Then ask the observers for what they saw. Focus on the service: missing information, unclear rules, handovers. Do not comment on acting. List the breakdowns on a board.
Step 6: Change one thing and replay
Pick the most serious breakdown and try a fix, such as giving the front desk a checklist or changing who calls back. Run the scenario again with the fix and see whether the problem disappears or moves somewhere else.
Step 7: Record what you learned
Complete the worksheet: role, situation, action, observation for each breakdown. Note which fixes worked. Agree what to change in the design, and what to test next with real customers.
Worked example
A telecom company is redesigning how it handles customers who visit a store to dispute a bill. Today the store employee must phone the billing team, and customers often wait 20 minutes or are told to call themselves. Five people take part: two store employees, a billing officer, a customer-experience designer and a team lead.
The scenario: a customer arrives with a printed bill showing a roaming charge she did not expect. She travelled for three days. She has her passport stamps but no booking receipts.
One store employee plays the customer, the other plays the front desk. The billing officer sits behind a screen with a phone. The designer and team lead observe.
In the first run, the front-desk employee calls billing and is put on hold for four minutes. Billing asks for the travel dates, which the front desk did not record. The customer is asked to come back tomorrow. Observers note three breakdowns: no intake checklist, no direct line to billing, and no way to tell the customer when she will hear back.
In the second run, the front desk uses a short intake card with dates, destination and amount, and books a billing callback slot on the spot. The handover takes under a minute and the customer leaves with a time. The team adds the intake card and callback booking to the new design and plans a trial in two stores.
IllustrativeTips and mistakes
Tips
- Swap roles between runs. People learn the most when they play the side they do not usually see.
- Keep props simple but real. A real form shows wording problems that a blank sheet hides.
- Have observers write exact quotes. 'I don't know who handles that' is a powerful finding.
- Time the waits with a phone. Minutes are more convincing than impressions.
Common mistakes
- Commenting on how well someone acted. It makes people defensive and wastes the session.
- Writing a scenario so simple that nothing can go wrong.
- Letting the facilitator jump in to rescue the actors when they get stuck. Being stuck is the finding.
- Running only one version and never testing a fix.
What you walk away with
You walk away with a list of specific breakdowns in the service, a set of tested fixes, and a clearer picture of what each role needs in order to help the customer. Feed the changes back into your storyboard or experience map, and build any new forms or screens as a paper prototype to test with real customers.
Questions people ask
What if people are shy about acting?
Start with a short, low-stakes warm-up and keep the group small. Remind everyone that nobody is being judged and that awkward moments are useful data. Some people prefer to observe first and act in the second run.
Can we role play with real customers?
Yes, with care. Ask a few customers to play themselves while staff play their own roles. Explain the purpose, get consent, keep the scenario away from their private details, and thank them for their time.
Role play or storyboard?
A storyboard shows the sequence on paper and is good for spotting assumptions. Role play brings the sequence to life and is better for finding problems in handovers, timing and wording. Many teams draw a storyboard first and then act out its riskiest frames.
Tool card
The worksheet your team fills in, one box per field.
- Role
- Situation
- Action
- Observation