The Reveal

Test whether your team is really aligned before you commit.

The Reveal

What this fixes

Your team agreed. Everyone nodded. The meeting ended early. Weeks later, the work starts going in different directions - not because people disagreed, but because everyone thought they agreed.

The dangerous part isn’t disagreement. It’s false agreement: you were all certain you were aligned. This makes those hidden differences visible now - before they become rework, conflict and missed deadlines.

How this works

Ask the team one sharp question - “what matters most for this to succeed?”

Everyone answers privately, in writing, before anyone speaks.

When the answers go up together, the hidden differences become visible. That’s the reveal. Don’t fix them yet. Just see them.

Team: one person acts as the facilitator - they run the activity while everyone else takes part. They ask the question and run the reveal; they do not steer the answers.

Time required

Team ✓     10–20 minutes.

The time required is indicative and will depend on the nature of the problem and the size of the team.

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

When to use

Run it whenever an important “we’re aligned” needs testing before you commit to it.

Good signs it’s the right tool:

  • a kick-off where everyone seemed to agree quickly
  • a strategy or priority that “everyone’s agreed on”
  • a goal stated in words that could mean several things (“ship quality”, “move fast”, “delight users”)
  • a leadership team that believes it’s in agreement

What you get

  • The hidden differences in what people value, made visible
  • A specific divergence you didn’t know existed - on paper
  • A shared view of where alignment is real - and where it isn’t

You’ve done it well when: the team can point to a real difference it was certain didn’t exist - and sees it would have surfaced later, as a problem.

What you’ll notice

  • The room goes quiet at the reveal
  • “I genuinely thought we all meant the same thing”
  • The team realises it wasn’t aligned - it only thought it was
  • Relief that it surfaced now, not mid-project

Why this works

Once people start talking, they quickly borrow each other’s words. The differences disappear before anyone sees them. Writing privately first captures what each person really thinks. That’s what makes the reveal possible.

What you need

One statement the team believes it already agrees on. For example: “Customer experience comes first.” “Move fast.” “Quality matters most.”

One question about what people value - not what they should do. For example: “What matters most for this to succeed?”

Index cards or sticky notes. One per person - so each answer is written privately before any are seen.

A wall or table. Space to reveal all the answers at once, side by side, so the divergence is visible to everyone together.

Roles - Team: a facilitator (asks the question, runs the reveal, does NOT influence answers) and participants (answer privately, then read the wall).

Steps

  1. Set up. Appoint a facilitator - they run the activity. Name the one statement you all “agree” on, and write it where everyone can see it.
  2. Ask ONE question about what matters most (2 min). Ask one question about what people value. Don’t ask what people should do. One question, asked once.

Safe examples: “What matters most for this to succeed?” · “What’s the single biggest priority here?” · “How would we know this succeeded?”

  1. Write privately (3 min). Everyone writes their own answer, alone, before anyone speaks. No discussion. This is the step that makes it work - protect the silence.
  2. Reveal together (5 min). Put all the answers up at once. Read them aloud as written. Let the differences sit - and do not allow discussion yet. Don’t explain them away.
  3. Name the gap (5 min). Point to the specific differences. Where did you assume agreement that wasn’t there? Write down the one that would most have hurt the work. Don’t try to solve it. The discovery is today’s output.

Output / Takeaways

  • The differences, captured as written - not smoothed over
  • The one divergence that would most have disrupted the work
  • A shared, honest base for the next conversation (elsewhere)

Important rules

  • Private writing first - no discussion before the reveal, ever
  • Ask about what people value, not what they heard
  • Reveal all answers at once, read as written
  • Stop at the reveal - do NOT rank, fix or resolve here

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

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