Overview and Quick Answer
The tea room game is a structured role-play activity used in service design and UX research to simulate front-desk, reception, or hospitality interactions in a safe, low-stakes space. In its classic form, participants take on predefined roles—guest, host, phone operator, or observer—using props, scripts, and boundary rules to mimic realistic scenarios such as making reservations, handling complaints, or navigating check-in. The exercise emphasizes observable behaviors, moment-by-moment decision points, and service blueprints rather than scripted storytelling, making it a repeatable diagnostic tool for onboarding, queuing, accessibility, and cross-channel coherence. Below is an evergreen breakdown of formats, steps, and practical guidance you can apply in workshops, interviews, and service audits.
Definition and Core Mechanics
At its simplest, the tea room game is a role-play simulation framed as a small, bounded service encounter often set in a literal or metaphorical tea room, front desk, or reception area. It typically involves at least two participants playing predefined roles, supported by props, cue cards, and optional observers who track behaviors and emotions. Timeboxing (for example, 5 to 10 minutes per scenario) keeps sessions focused, while clear success criteria—such as completing a booking or resolving a concern—create measurable outcomes. The format favors concrete, observable interactions over abstract discussion, revealing pain points in sequencing, information flow, and etiquette that people might not report in interviews alone.
Key Components of a Tea Room Game Session
- Roles: guest, host, phone operator, observer
- Scenario: reservation, complaint, orientation, or onboarding task
- Props: notepad, bell, mock menus, access badges
- Rules: timebox, boundaries (e.g., no breaking character), data capture method
- Outputs: raw observations, quotes, timeline of steps, emotions, and pain points
Historical Context and Origins
The tea room game emerged from service design workshops in Europe during the late 1990s and early 2000s, where practitioners sought quick, tangible ways to rehearse and critique frontline interactions. Earlier influences include role-play methods in theater and service blueprinting developed by Lynn Shostack and later popularized by service design thinkers such as Andy Polaine and Ben Reason. While the exact originator is not documented in a single paper, the name reflects the simple, accessible mise-en-scène—tables, chairs, a teapot, and a clear stage—making it easy to set up in co-design rooms with minimal investment. Over time, it became a staple in service design studios, innovation labs, and customer research teams seeking rapid, human-centered diagnostics.
Step-by-Step Guide to Running a Tea Room Game
Effective sessions start with clear objectives and modest scope, then iterate based on participant feedback.
Preparation (15–30 minutes)
- Define a narrow scenario: for example, "a guest calls to change a reservation" or "a visitor checks in during a busy conference."
- Create concise role briefs with goals, constraints, and background (one paragraph per role).
- Prepare props: name tags, scripts with key information, mock interfaces, and a way to record (notes or audio).
- Set boundaries: timebox (5–10 minutes), no breaking character, and a stop signal for discomfort.
Execution (10–20 minutes)
- Introduce roles, rules, and scenario in one sentence each.
- Run the scenario while observers note sequences, wait times, emotional shifts, and system touchpoints.
- Keep roles intact; avoid improviser drift that obscures the target behaviors.
Synthesis (15–30 minutes)
- Debrief by separating observable events from interpretation.
- Map key steps on a service blueprint, highlighting failures, surprises, and delightful moments.
- Extract concrete recommendations tied to policies, scripts, signage, or interface changes.
When and Why to Use the Tea Room Game
Use the tea room game when you need fast, embodied insights into service touchpoints, especially for reception, hospitality, onboarding, or multi-channel handoffs. It works well in co-design workshops, stakeholder alignment sessions, and rapid user research sprints where live observation matters more than large-sample statistics. It is less suited for deeply personal or highly confidential topics, and it should be complemented with real-world interviews and contextual inquiry for full context. The method shines when teams need to align on shared language around customer journeys and when tangible artifacts (journeys, blueprints, pain-point maps) will be reused across roadmaps.
Variations and Practical Formats
Teams adapt the tea room game to context without losing its diagnostic core.
Solo Remote Variant
One participant plays both guest and host by switching hats, narrating internal decisions aloud. Useful for quick self-tests but limited in uncovering blind spots.
Panel Format
Multiple guests interact with one host while observers rotate roles. Good for stress-testing policies and comparing experiences across segments.
Digital Tea Room
Replace physical props with screen sharing and chat; run simulated website or app check-ins with timed tasks. Retains same structure while supporting remote and hybrid teams.
Accessibility Lens
Incorporate specific goals such as testing clarity for neurodiverse guests, legibility for low-vision visitors, or approachability for people with mobility needs. Observations feed inclusive service standards.
Comparison with Similar Methods
| Method | Setup Time | Observational Depth | Ideal Use Case |
|---|---|---|---|
| Tea Room Game | Low | High (behavioral, moment-by-moment) | Front-desk and reception scenarios |
| Ethnographic Shadowing | High | Very high (real context) | Complex journeys in live environments |
| Usability Testing | Medium | Medium (task completion and usability) | Digital interfaces and prototypes |
| In-Context Interviews | Low to Medium | Medium (reported feelings + behavior) | Exploratory needs-finding |
Practical Tips and Common Pitfalls
- Keep scenarios narrow and concrete; avoid broad "visit a tea room" prompts.
- Clarify boundaries up front to prevent participants feeling trapped or embarrassed.
- Observers should focus on actions and timestamps, not interpreting intent.
- Rotate roles across sessions to reduce bias and surface systemic issues.
- Archive anonymized playbacks and blueprints for longitudinal service audits.
- Combine findings with customer interviews to distinguish role-play artifacts from real-world behavior.