You've seen it in team building workshops. Maybe you've even done it yourself — sitting back-to-back with a coworker, one of you holding a simple line drawing, the other with a blank sheet of paper and a pen. Don't use gestures. Don't show it. The instructions seem straightforward: describe the image. Just words.
It sounds simple, but the gap is usually here It's one of those things that adds up..
Fifteen minutes later, you're both laughing at a drawing that looks nothing like the original. A house becomes a rocket ship. A cat becomes a very confused triangle.
That's the back to back drawing communication exercise. And if you've only ever treated it as an icebreaker, you're missing the point.
What Is Back to Back Drawing
At its core, this is a constrained communication game. That said, one image. Two people. One blank page. Zero visual contact.
The describer — sometimes called the "speaker" or "instructor" — has a pre-drawn image. Could be something deliberately ambiguous. Could be a simple house with a tree and sun. Could be a geometric shape arrangement. Their job: translate visual information into verbal instructions.
The drawer — the "listener" or "artist" — receives only those instructions. No questions allowed in the classic version. No peeking. They draw what they hear No workaround needed..
That's it. That's the whole exercise.
But here's what makes it deceptively powerful: the constraint forces every communication failure to the surface. Assumptions. Vague language. Missing context. The stuff that slides by unnoticed in Slack messages and Zoom calls gets exposed in real time, on paper, where everyone can see it That's the part that actually makes a difference..
The Classic Setup
Most facilitators run it like this:
- Pairs sit back-to-back (chairs facing opposite directions)
- One person gets the reference image — face down until start
- The other gets blank paper and pen
- Time limit: usually 5–10 minutes for the drawing phase
- Debrief: 10–20 minutes discussing what happened
Simple materials. Zero tech. Works in a conference room, a classroom, or a kitchen table.
Variations You'll See
Some facilitators allow questions — turning it into a dialogue instead of a monologue. Others run it in triads: one describer, two drawers working independently, then compare results. I've seen versions where the image is built from LEGO bricks instead of drawn, or where the describer can only use geometric terms ("equilateral triangle, base down, centered").
The constraints change. The lesson doesn't Easy to understand, harder to ignore..
Why It Matters / Why People Keep Using It
This exercise has survived decades of corporate training trends for a reason. It's not because it's fun — though it usually is. It's because it compresses months of workplace communication dysfunction into ten minutes Simple, but easy to overlook. Less friction, more output..
Think about it. How many times has this happened on your team?
Someone says "make the button pop more" and the designer adds a drop shadow. The stakeholder meant brighter color. Two weeks of revisions later, they finally align It's one of those things that adds up..
Or a product manager writes "user-friendly dashboard" in a ticket. The PM wanted tooltips, onboarding flows, and a help widget. Plus, neither was wrong. And the engineer builds a clean, minimal interface. Both were vague Still holds up..
Back to back drawing makes that gap visible. Here's the thing — immediately. Irrefutably.
What It Actually Reveals
Assumption blindness. The describer assumes the drawer knows what a "standard house shape" looks like. The drawer assumes "triangle on top of a square" means equilateral triangle, centered. Neither checks.
Missing reference points. "Draw a line" — from where? To where? At what angle? Without shared coordinates, "line" means nothing useful.
The curse of knowledge. The describer sees the whole image. They can't un-see it. So they describe the result ("draw the roof") instead of the steps ("draw a triangle centered on top of the square"). The drawer needs steps. The describer gives outcomes.
One-way vs. two-way communication. In the no-questions version, errors compound silently. The drawer draws a window in the wrong spot. The describer keeps going. By the end, the drawing is structurally wrong but the describer thinks it's fine — they've been describing a different drawing the whole time.
Sound familiar? Plus, this is every handoff meeting. It should. Every requirements doc. Every "quick sync" that wasn't.
How It Works — Step by Step
If you're running this for a team, here's how to get more than just laughs out of it.
1. Choose Your Images Deliberately
Don't grab random clip art. The image is the difficulty setting.
Level 1 — Basic shapes: Square, circle, triangle arranged simply. Good for new teams or non-visual thinkers.
Level 2 — Recognizable objects: House, tree, sun, cloud. The "standard" version. People think they know what these look like. They don't — not in shared detail.
Level 3 — Abstract composition: Overlapping shapes, specific angles, relative sizing matters. "The circle touches the square's top-right corner" — that precision exposes vague language fast.
Level 4 — Ambiguous forms: A shape that could be a bird or a boat. A squiggle with intentional asymmetry. Forces the describer to describe, not label.
Pro tip: have multiple image sets ready. Here's the thing — run round one with Level 1. On top of that, round two with Level 3. The contrast teaches more than either alone Not complicated — just consistent..
2. Set the Rules — And Enforce Them
Classic rules:
- No turning around
- No questions (or: questions allowed, but only yes/no)
- No gestures
- Describer cannot see the drawing
- Drawer cannot see the image
- Time box: 7 minutes
Write the rules where everyone can see them. Someone will try to peek. Someone will start miming. Call it out immediately — gently — and reset. The constraint is the teacher The details matter here. Simple as that..
3. Run the Debrief Like You Mean It
This is where the exercise lives or dies. Don't just ask "how'd it go?" and move on.
Structure the debrief in layers:
Layer 1 — What happened? (Facts only)
- "Describers: what was your strategy?"
- "Drawers: what was hardest to follow?"
- "What did the final drawing look like vs. the original?"
Layer 2 — What did you notice? (Observations)
- "At what point did you realize you were off track?"
- "What instruction would have helped most?"
- "Did anyone assume something that turned out wrong?"
Layer 3 — Where does this show up at work? (Transfer)
- "When have you been the describer in a real project?"
- "When have you been the drawer?"
- "What would 'asking questions' look like in your actual workflow?"
Let silence sit. The best insights come after the awkward pause.
4. Run a Second Round — With Changes
This is the part most facilitators skip. Run it again. Worth adding: same pairs. New image.
— switch who goes first, tighten the timebox to 5 minutes, or move to Level 3 images. The improvement should be visible. Teams often discover that the second round reveals everything they missed the first time Nothing fancy..
Level 5 — Your Actual Work: Replace the Pictionary board with a real requirement doc, a user story, or a system architecture diagram. Same rules, same time. This is where the magic happens — or doesn't Surprisingly effective..
Common Pitfalls (And How to Dodge Them)
The "I'm not creative" brigade: Some folks freeze when asked to describe a simple circle. Have them start with Level 1 shapes. Creativity isn't the goal; communication is Took long enough..
Over-explaining: "The big circle has a smaller circle inside it, and there's a rectangle below..." Slow down. The act of choosing words carefully is the exercise.
Drawing too fast: The drawer rushes and creates something "close enough." Force pauses between each instruction. This mirrors the cost of unclear requirements Turns out it matters..
Skipping the debrief: Without reflection, it's just a game. The debrief is where vocabulary gets built — terms like "tangent," "proximate," "bisect" become useful in both contexts The details matter here..
Real-World Translation
When your product manager describes a feature as "a search bar at the top," what does that mean to different people? Now, how wide? Consider this: where's the search icon relative to the logo? What about mobile? These are the same gaps filled in Pictionary Worth keeping that in mind..
When engineering hears "make it faster," are they optimizing the database query or lazy-loading images? Description without precision equals rework.
The Deeper Pattern
This exercise reveals a fundamental truth: Most communication failures happen at the boundary between imagination and execution.
The describer holds the mental model. The drawer holds the canvas. Between them lives all the lost time, the duplicate work, the "that's not what I meant" conversations.
Every requirements document is a Pictionary board. Think about it: every sprint planning meeting is a drawing session. Every API spec is an image that someone has to recreate from memory Small thing, real impact. Which is the point..
Making It Stick
Don't file this under "fun team building." Return to it quarterly. That's why after particularly messy releases. Think about it: before major project kickoffs. When new people join No workaround needed..
Create a shared vocabulary from the debrief. When someone says "be more specific about the circle's position," you'll know you're speaking the same language Took long enough..
Track the pattern: "Last month we had three miscommunications about button placement. This month we're asking for more precise positioning descriptions upfront."
The Real Win
You'll know it worked when someone says, "Wait, I need to describe this more clearly," before starting a task. That moment of metacognition — recognizing the gap between what's in your head and what others can see — that's the whole point.
Communication isn't about talking more. In practice, it's about bridging the distance between minds. This exercise builds the bridge, one imprecise description at a time.
In the end, every successful handoff, every clear requirement, every well-documented API is just someone taking extra care with how they describe what they see. The difference between chaos and clarity often lives in the spaces between words — and sometimes, you have to draw a circle to find it.
Counterintuitive, but true It's one of those things that adds up..
