Facilitator's Guide

What you're doing — and why it works

Snapshot captures what people actually think before group dynamics can distort it. You ask one question, show a set of ambiguous images, and everyone picks independently and simultaneously — without seeing each other's choice. The reveal shows the pattern. That pattern is your data.

The method works because images activate perception before language does. By the time your team tells you what they think in words, they've already adjusted for what they know you want to hear. An image pick happens faster than that edit. Research calls it social desirability bias. Snapshot sidesteps it.

When to use it

• Before a strategy conversation — surface where the team actually stands before you ask them to commit to a direction.
• When you suspect misalignment — you feel it but can't prove it. Snapshot makes it visible.
• Team formation or onboarding — fast way to understand how differently people see the same situation.
• After a major change — restructure, acquisition, new leadership. What does the team actually feel?
• Any time the real conversation isn't happening — when the official story and the corridor story are different.

It works best with 4–20 people. Smaller than 4 and there's not enough pattern to reveal. Larger than 20 and the reveal conversation becomes difficult to facilitate well.

Write one good question

The question is everything. It should be specific enough to generate meaningful choices, and open enough that the image does the work. A few tests:

• One thing at a time. "How aligned are we on strategy and culture?" is two questions. Pick one.
• Genuinely open. If you already know the answer you want, don't ask it — people will sense it and respond to that, not the question.
• Present tense. "Where is this team right now?" surfaces current reality. "Where should we be?" surfaces aspiration. Both are useful. Know which one you want.

Examples that work well:

• "Where is this team right now?"
• "How does our strategy feel from where you sit?"
• "What does our culture look like in practice?"
• "How aligned do you feel we are as a leadership team?"
• "What does the road ahead look like to you?"

Running the session

1. Start a Snapshot. Go to Start a Snapshot, write your question, and set a deadline if you want one. You get a session code and a QR code.
2. Share the code. Show the QR on screen, or share the link. Participants go to snapshot.connecteddale.com and enter the code. Each person picks independently — they don't see anyone else's choice until the reveal.
3. Wait for responses. The waiting room shows you how many have responded. Most sessions complete in under five minutes when people are in the room together. For async sessions, a 24–48 hour deadline works well.
4. Reveal. When everyone has responded (or you've decided to proceed), open the reveal. Every participant's image appears at once, alongside the words they used to explain their choice.

Facilitating the reveal conversation

The reveal is where the value lives. The images are a prompt for a conversation the team couldn't have without them — because without them, everyone would have edited their answer before speaking.

Start with images only — hide the text

When the reveal opens, the written explanations are hidden by default. Keep them hidden. Press T (or click Show text) to toggle them — but don't do that yet.

Go around the room and ask each person to describe their image in their own words first: "Tell us about your image — what did you see in it?" Only after they've spoken, ask: "Can I show what you wrote when you picked it?" Then press T to reveal their text alongside what they just said.

This matters for two reasons. First, verbal description is richer and more spontaneous than text typed alone — people will say things they didn't write down. Second, and more importantly, sometimes what someone says out loud and what they wrote are different. That gap is some of the most valuable data in the session. A person who wrote "we're stuck" but describes it out loud as "cautious momentum" is telling you something about how safe they feel being honest in the room. Don't smooth over that gap — name it gently and explore it.

The other reason to keep text hidden initially: if participants read each other's words before speaking, they'll calibrate their explanation to the room. You're back to social desirability bias. The whole point of the method is to capture what people reached for before they knew what the room thought. Preserve that by keeping the text hidden until each person has spoken for themselves.

When you ask "Can I show what you wrote?" — accept no as a complete answer. Some people will have written something more honest than they're ready to say in the room. That's fine. The image and what they said verbally is already data. Don't press. The fact that someone wants to keep their text private is itself something worth noting — it usually means the psychological safety in the room isn't quite where it needs to be yet, and that's useful to know.

Other principles for the conversation

• Don't interpret first. Let the pattern land. Give the room 20–30 seconds of silence after the reveal appears. People need to take it in.
• Ask about meaning, not justification. "What does this image mean to you?" not "Why did you pick this?" Why invites rationalisation. What keeps it open.
• Name the pattern, don't explain it. If three people picked images about isolation and two picked momentum, name that. Don't interpret it yet. Let the team do that.
• Start with the outliers. The person whose image looks very different from the group's often has the most important thing to say. Ask them first, gently.
• The alignment score is a starting point. High alignment isn't always good (everyone aligned on stagnation) and low alignment isn't always bad (healthy creative tension). The score opens the question — it doesn't answer it.

A simple opening that works: "Before anyone explains their choice, just look at what's here. What do you notice?"

After the session

The reveal shows you where the team actually is. What you do with that depends on what you found. A few common patterns and what they usually mean:

• High alignment, positive images. The team is solid. Use the session to name what's working and ask what would threaten it.
• High alignment, challenging images. Everyone sees the same problem. That's actually a gift — it means the conversation is possible. The question is why no one has said it out loud until now.
• Low alignment. People are experiencing the same situation very differently. Don't try to resolve it in the session. Name it, then schedule a deeper conversation.
• One clear outlier. This person may be seeing something the rest of the team isn't — or they may be in a different situation. Either way, their perspective is the most important one to understand.

The test of a good Snapshot session: everyone should be able to describe what the team revealed and what it means for the next conversation. If that's not true at the end of the session, you haven't gone deep enough yet.

Common mistakes

• Asking the question out loud before people respond. Participants hear your tone and already know what answer you want. Write the question, share the code, stay neutral.
• Moving to solutions too fast. The reveal is diagnostic. Resist the urge to fix what you see before the team has had a chance to understand it.
• Treating the alignment score as a grade. It's a description, not an evaluation. Don't let the team spend the conversation defending or explaining the number.
• Skipping the silence. The 20 seconds after the reveal lands are the most valuable 20 seconds in the session. Don't fill them.
• Using it as a gotcha. If the real purpose is to prove a point you've already decided, participants will sense it and the data becomes unreliable.