Something goes badly wrong. The team reviews it, agrees on actions, and moves on. Months later, a version of the same problem appears again.
The issue is not a lack of reflection. Most reviews happen after the outcome is visible - when everyone knows how the story ended, and the warning signs look obvious. Teams do not repeat failures because they failed to analyse them. They repeat them because nobody recognised the pattern while there was still time to act.
Match Tape builds that recognition.
A normal review asks what happened and why. Match Tape asks:
What could we see, what did we think was happening, and when should our understanding have changed?
Match Tape is not an event history. It is a reconstruction of the decision environment.
The team moves through four stages - Reality Check, then the Tape, then the Recognition Gap, then the Recognition Play. You find out what different people actually saw, rebuild what was known at each decision point, find where recognition lagged behind reality, and turn that pattern into a play for next time.
A normal retro produces lessons. Match Tape produces a Recognition Play - what to notice, how to read it, and what to do before the pattern repeats.
Solo ✗ Team ✓ About 60 minutes, with a facilitator.
This is not a replacement for your sprint retro. It is for the events you cannot afford to repeat. The facilitator reads the guide first - downloadable on this page.
Use this when:
Good examples: a customer escalation that surprised everyone; a launch delay that appeared suddenly; a dependency problem that has now repeated across projects.
Not for routine sprint reviews, status discussions, or while you are still firefighting.
The team can finish this sentence:
When we see --, we know --, and we will --.
If the team only understands what happened, the learning is not finished.
The completed tape is photographed before anyone leaves.
Once you know the outcome, the earlier signals look obvious. Match Tape rebuilds each decision using only what was known at the time, then turns the missed pattern into something the team can recognise and act on next time.
Before you start. One person facilitates: they keep the sequence, keep hindsight out, and keep the room on learning rather than blame. Nobody is looking for who made the wrong call.
Working alone: with the information you had at the time, when did you first think something might be changing - and what did you think was happening?
Answers go on the board. The facilitator asks what we notice. Do not debate whose answer was right - the different starting points are the finding.
For each important moment, capture four things: what happened, what we knew at that point, how we were understanding it, and what we decided.
Facts before explanations. Only information that was available at that moment. Disagreements are settled by the record, not by seniority.
Read the tape and ask: when did reality change while our understanding stayed the same? Mark the earliest point where recognising it could have changed the outcome, then ask what we should have recognised there.
Ask what situation we were actually in. Do not accept communication failed, planning was weak, or ownership was missing - those are symptoms. Name the pattern underneath.
Four lines: the pattern, the signals that tell you it is forming, how to read it, and what you will do.
Worked example - Silent Scope Expansion. Signals: small changes accepted after commitment, timeline unchanged, no trade-off discussed. Read it as: the execution model has changed. Response: stop and reset scope, timeline or people.
Then ask whether this would help another team recognise the situation earlier. If it would, save it.
10 · Important rules
Planning to facilitate this activity? Access the resources below to get started.