The Telephone Game Retrospective

Reveal how messages get distorted across your team.

Use this template in TeamRetro

The Original Message

What was clearly and effectively communicated from the start?

The sprint goals were crystal clear because the PO walked us through them with examples.
Our written decision log meant nobody had to guess what was agreed.
Daily standups kept everyone aligned on priorities for the week.
Lost in Translation

Where did the message get distorted, lost, or misunderstood?

A verbal agreement in a hallway chat never made it into the ticket.
The client's request was paraphrased three times and lost its original intent.
Important context lived in someone's head and never got documented.
The Source of the Static

What caused the breakdowns in how information traveled?

We have too many communication channels and no single source of truth.
Decisions made async don't always get captured anywhere central.
Unclear ownership meant updates fell through the cracks.
Clearing the Line

How can we make our communication clearer and more reliable?

Establish a single source of truth for all key decisions.
Confirm understanding by repeating back requirements in our own words.
Document verbal agreements in the relevant ticket immediately.

What is the Telephone Game Retrospective?

Inspired by the classic children's game where a whispered phrase morphs into something unrecognizable by the time it reaches the last person, The Telephone Game Retrospective turns that playful idea into a powerful lens for examining how information travels through your team. Communication breakdowns are at the heart of many project hiccups, and this format helps surface where messages get distorted, lost, or reinterpreted between people, teams, and tools. During the session, your team explores the journey of information across a sprint or project. You'll trace how requirements, decisions, and updates were originally communicated, how they were received and understood, and where the gaps appeared along the way. By mapping these moments, you'll uncover the systemic causes of miscommunication rather than placing blame on individuals. The real value lies in turning fuzzy frustrations into concrete improvements. Teams walk away with a clearer picture of their communication channels, agreed-upon practices for sharing information more reliably, and a renewed appreciation for clarity. It's an engaging, lighthearted way to tackle a serious topic, making it ideal for distributed and cross-functional teams who depend on accurate handoffs every day.

The Telephone Game retrospective format

The Original Message

What was clearly and effectively communicated from the start?

This topic captures the moments where information was shared accurately and understood as intended. Encourage your team to recognise the channels, formats, and habits that helped messages stay intact. Highlighting these successes reinforces the practices worth keeping and sets a positive tone before exploring the breakdowns.

Lost in Translation

Where did the message get distorted, lost, or misunderstood?

Here the team identifies the points where information changed shape or disappeared as it passed between people and tools. Frame this around systems and handoffs rather than individuals to keep it blame-free. Ask probing questions about where assumptions crept in and which channels tend to garble the message.

The Source of the Static

What caused the breakdowns in how information traveled?

This topic digs into the root causes behind the miscommunications surfaced earlier. Guide the team to look for recurring patterns such as unclear ownership, too many channels, or missing documentation. The goal is to understand the why so that fixes target the system rather than the symptom.

Clearing the Line

How can we make our communication clearer and more reliable?

Use this final topic to turn insights into concrete, actionable commitments. Encourage specific, ownable improvements rather than vague intentions. Prioritise a few high-impact changes the team can realistically adopt and revisit in the next retrospective.

When to use this retrospective

  • When recurring misunderstandings or rework suggest communication is breaking down across the team.
  • After a project with multiple handoffs between people, teams, or tools, to trace where clarity was lost.
  • For distributed or cross-functional teams who rely heavily on async and written communication.
  • When onboarding new team members highlights gaps in how knowledge is shared and documented.
  • To lighten the mood while tackling a serious topic, using a playful format to spark honest reflection.

Suggested icebreaker questions

  • What's the funniest miscommunication you've ever been part of, at work or in life?
  • If your team's communication were a phone signal, how many bars would it have today?

Ideas and tips for your retrospective meeting

  • Keep the conversation focused on systems and handoffs rather than individuals to avoid blame.
  • Trace a real example of a message that got distorted to ground the discussion in a concrete story.
  • Invite people from different roles and teams so you capture every point along the information chain.
  • Timebox each topic to keep momentum, especially when surfacing the source of breakdowns.
  • Prioritise just two or three high-impact improvements so commitments are realistic and trackable.
  • Revisit the agreed actions at the next retrospective to confirm communication has actually improved.

Frequently asked questions

What is the Telephone Game retrospective?
It's a communication-focused retrospective inspired by the children's game where a whispered message gets distorted as it passes from person to person. Teams use it to trace how information travels and where it breaks down across people, teams, and tools. Similar to Gartic phone and telestrations, the goal is for the team to indentiy areas along the communication chain that distorts the original message.
When should I use the Telephone Game retrospective?
Use it when you notice recurring misunderstandings, rework, or missed information, especially after projects with many handoffs or for distributed and cross-functional teams that rely on async communication.
How long does the Telephone Game retrospective take?
A typical session runs 45 to 60 minutes, allowing time to surface what was clear, where messages got lost, the root causes, and a few concrete improvements.
How is it different from a standard sprint retrospective?
Rather than reviewing the whole sprint, it zooms in specifically on communication and information flow, making it ideal when miscommunication is the main pain point.
How do I keep it blame-free?
Frame every topic around systems, channels, and handoffs instead of individuals, and focus on understanding why breakdowns happen so fixes target the process, not people.
Who should take part in the Telephone Game retrospective?
Include people from each point along your information chain such as product, design, development, and QA, so you capture how messages are sent, received, and interpreted at every stage.

New to retrospectives? Read our guide on how to run a retrospective →

Related templates

WWE Smackdown Showdown Retrospective

Tag-team your sprint reflections with wrestling-themed flair.

Working, Not Working Retrospective

A clear-cut way to identify successes and improvement areas

Quarterly Retrospective

Reflect, realign, and recharge your team every quarter.

Baby Steps Retrospective

Drive continuous improvement through small, achievable changes.