The Telephone Game Retrospective

See where messages get garbled across your team

Try this retrospective live

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?

The Telephone Game Retrospective is based on the children's game where a whispered phrase changes a little with every person until it arrives as something else entirely. Your team uses the same idea to look at how requirements, decisions and updates traveled during a sprint or project, and where they changed along the way. The board follows the message from start to finish. The Original Message covers what was communicated clearly. Lost in Translation is where information was distorted, dropped or misread as it passed between people and tools. The Source of the Static digs into why, and Clearing the Line turns that into changes the team will make. Tracing the path of a real message keeps the conversation on handoffs and channels, not on who got it wrong. You come out with a few specific fixes, such as a single place for decisions or a written summary after meetings. It suits distributed and cross-functional teams, where a lot depends on handoffs going right.

The Telephone Game retrospective format

The Original Message

What was clearly and effectively communicated from the start?

Start with what went right: information that was shared accurately and understood as intended. Ask which channels, formats and habits kept the message intact, so you know what to keep before you look at the breakdowns.

Lost in Translation

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

Find the points where information changed or disappeared as it passed between people and tools. Keep it about handoffs and systems, not individuals, and ask where assumptions crept in and which channels tend to garble things.

The Source of the Static

What caused the breakdowns in how information traveled?

Look for the root causes behind the breakdowns, especially ones that keep coming back, such as unclear ownership, too many channels or missing documentation. Fixing the cause stops the same message getting lost next sprint.

Clearing the Line

How can we make our communication clearer and more reliable?

Turn what you've found into specific commitments with an owner. Pick two or three changes the team can realistically adopt, and check on them at the next retrospective.

When to use this retrospective

  • When recurring misunderstandings or rework suggest information is getting lost somewhere.
  • After a project with many handoffs between people, teams or tools, to trace where clarity was lost.
  • For distributed or cross-functional teams that rely on async and written communication.
  • When onboarding new people exposes gaps in how knowledge is shared and documented.
  • When you want a lighter format for a serious topic, so people talk honestly about communication problems.

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?

Want a warm-up your team plays, not just answers out loud? Browse free icebreakers →

Ideas and tips for your retrospective meeting

  • Keep the conversation on systems and handoffs, not individuals.
  • Trace one real message that got distorted, step by step, to ground the discussion in a concrete story.
  • Invite people from different roles and teams so every point along the chain is represented.
  • Timebox each topic, especially The Source of the Static, where discussion can run long.
  • Pick two or three improvements so the commitments are realistic and easy to track.
  • Check the agreed actions at the next retrospective to see whether communication actually improved.

Frequently asked questions

What is the Telephone Game retrospective?
It's a communication-focused retrospective based on the children's game where a whispered message changes as it passes from person to person. Your team traces how information traveled and where it broke down between people, teams and tools. Like the party games Gartic Phone and Telestrations, the point is to find where along the chain the original message changed.
When should I use the Telephone Game retrospective?
Use it when you notice recurring misunderstandings, rework or missed information, especially after a project with many handoffs or with a distributed team that relies on async communication.
How long does the Telephone Game retrospective take?
Most sessions take 45–60 minutes. That leaves time to cover what was clear, where messages got lost, the root causes and a few specific improvements.
How is it different from a standard sprint retrospective?
A standard retro reviews the whole sprint. This one looks only at communication and information flow, so it's the better choice when miscommunication is the main problem.
How do I keep it blame-free?
Frame every topic around systems, channels and handoffs instead of people. When you ask why a breakdown happened, look for the gap in the process, so the fix changes how the team works.
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. That way you see how each message was sent, received and understood at every stage.

Related templates

WWE Smackdown Showdown Retrospective

Tag-team your sprint review with a wrestling theme.

Working, Not Working Retrospective

Sort what's working from what isn't, then fix it.

Quarterly Retrospective

Step back from the sprints and review the whole quarter.

Baby Steps Retrospective

Pick one small change your team will actually finish.

Ready to run this retrospective?Try this retrospective live