Story vs Reality Review

Separate the story the team tells from what actually drove the outcome.

Story vs Reality Review

What this fixes

Many reviews repeat the explanation the team already agrees on - “scope changed,” “bad luck,” “requirements shifted” - and learn nothing new. The real drivers (a quiet decision, an unspoken assumption, a risk everyone saw and no one named) stay below the surface, because saying them out loud feels uncomfortable.

This activity brings those drivers up - honestly, and without blame - so the team learns what actually happened, not just the version it settled on.

How this works

Imagine this: after a release, the agreed story is “the timeline slipped because scope changed.” On the board, the below-the-line cards tell a fuller story - a date promised before scoping, a concern nobody raised, a dependency everyone assumed someone else owned. The team finally discusses what really happened.

You draw a waterline. Above it goes the agreed story that the team tells out loud. Below it go the real drivers - true, but usually unsaid. Everyone privately writes what they believe actually drove the outcome, places each card above or below the line, and then the below-the-line cards are revealed and discussed together.

The private write is what makes it work. People won’t say the hidden drivers out loud, but they’ll write them - and once they’re on the board, the team can finally talk about them.

Team: one person acts as the facilitator - they run the activity using the Facilitator Guide while everyone else takes part.

Time required

Team ✓   About 30–45 minutes, with a facilitator.

The time required is indicative and will depend on the size of the team and how much sits below the line.

The facilitator should read the short facilitation guide first - about 8–10 minutes. It is a downloadable PDF on this page.

When to use

Bring one finished piece of work the team has a settled story about - and you suspect the real drivers haven’t been said.

Use it whenever:

  • a project ended, and the team settled on a comfortable explanation
  • reviews keep reaching the same agreed conclusions
  • you sense there’s a “thing no one’s saying” about how it went
  • you want to learn something the team doesn’t already know

What you get

  • The team’s told story and its real drivers, side by side
  • The honest drivers that were known but never said
  • One thing to do differently next time, with an owner

You’ve done it well when: the below-the-line cards hold something the team had never said in an open review - and you name what to do with it.

What you’ll notice

  • The story you agreed on was only the surface part
  • How many of you privately saw the same thing
  • The honest version is more useful than the comfortable one

Why this works

After the fact, teams settle on a shared story that’s comfortable and incomplete - the real drivers feel unsafe to name, so they stay unsaid. Writing privately and sorting above or below a waterline lets people surface what they wouldn’t say aloud; revealing the below-the-line cards together makes it safe and collective. The honest version was there all along - it just needed a way onto the board.

What you need

One finished piece of work. A completed project, release or initiative with an agreed explanation of what happened.

One facilitator. Their role is to protect anonymity and keep the discussion focused on learning, not blame - reading the below-the-line cards neutrally, never attributing a card to a person.

The waterline board. A board or wall with a clear horizontal line. Above = the agreed story. Below = the real drivers.

Driver cards + pens. One driver per card, no names. Written privately before the card goes on the board, so the honest ones reach it.

Steps

  1. Choose the work and draw the waterline (3–4 min). Team: appoint a facilitator first. Agree on the piece of work you’re reviewing and draw a line across the board. Above = the agreed story. Below = the real drivers.
  2. List the agreed-upon story (6 min). Put the agreed explanations above the line - “scope changed,” “bad luck.” Fast, no debate.
  3. Private write (8 min). Each person, privately and anonymously, writes what they believe actually drove the outcome - including what hasn’t been said. One idea per card.
  4. Place and reveal (8 min). Place each card above or below the line. Group similar cards together, then the facilitator reads the below-the-line cards aloud, neutrally. Notice how many people privately saw the same thing - and never said it.
  5. Carry one forward (10 min). Select the one driver that would most improve the next project if addressed. Decide what to do differently next time, and who owns it.

Output

You leave with:

  • The told story and the real drivers, side by side
  • The one driver the team agrees mattered most but had not been previously discussed openly
  • One change for next time, with an owner

Important rules

  • The writing is private and anonymous - no names on cards.
  • Don’t identify who wrote any card. Read the below-the-line cards neutrally. If someone asks “who wrote that?”, redirect the discussion to the idea, not the person.
  • Challenge ideas, not individuals. Name drivers, not people - the purpose is to improve future work, not assign blame for past work.
  • End with one honest change - not just the uncomfortable moment.

Planning to facilitate this activity? Access the resources below to get started.

MIndn
Execution must be smooth. Not chaotic or stressful.
Built by Witmer.