Draw the Team
If you're running this for an engineering team on a Tuesday, you're going to hear groans. Run it for a design offsite or skip it.
A collaborative drawing exercise — the team co-creates a visual of who they are, how they work, what they value. Works for design teams, mixed-discipline workshops, and offsite contexts where people aren't time-pressured. For an engineering team mid-sprint, it lands as enforced fun. We say so directly.
When to use
Design team offsites. Mixed-discipline workshops where drawing is already in the toolkit. Education contexts. Multi-day team retreats where the cringe ceiling is lower because nobody's late for a meeting. Skip it for engineering teams mid-sprint — the format will land as forced and the team will resent it. Use Personal Map for engineering teams; use Team Canvas if you want a structured-visualisation alternative without the free-drawing cringe.
How it runs
Read the room first
If you're scrolling this page on a Tuesday morning planning your engineering team's quarterly retro, this isn't your activity. Run Personal Map or Team Canvas instead. The honest move is to narrow the audience; the rest of the page assumes you're in the right context.
Frame the prompt deliberately
'Draw the team' is too vague — pick a specific lens. 'Draw how the team works on a good day.' 'Draw the team as a vehicle.' 'Draw the team five years from now.' The specific prompt is the difference between thirty minutes of useful exposure and thirty minutes of awkward.
Co-create on a single shared canvas
Miro, Mural, butcher paper. Everyone draws on the same surface, simultaneously. Don't break into pairs first — the whole-team-on-one-canvas chaos is the format. If somebody won't draw, let them annotate or write labels; participation can be light.
Step back and read it together
Twenty minutes drawing, ten minutes reading. What's at the centre of the picture? What's at the edge? What did three people draw versions of independently? The conversation about the picture is where the value lives — not in the picture itself.
Why it works
When it works, drawing forces a different cognitive register than talking. The team produces metaphors and structural relationships that wouldn't surface verbally — who's at the centre, what's connected to what, what's at the edge of the picture. The cringe risk is real and audience-specific; the format earns its place when the audience is comfortable with non-verbal expression. For audiences that aren't, it produces less than a thirty-minute conversation would have.
Variations
- Single-prompt variant: each person draws a small picture answering one question ('what does the team do best?'), then assembles into a collage. Lower commitment than free co-creation.
- Sketch-the-system: same exercise focused on the team's working system rather than identity. Less personal, more diagnostic, lower cringe ceiling.
- Async-first: each person uploads a sketch in advance; the live session is reading and discussing only. Much smaller cringe footprint.
- Comic-strip version: draw a four-panel comic of a recent project. Funnier, more constrained, surprisingly diagnostic.
Facilitator notes
Go first with a sparse, slightly bad sketch. Setting a high artistic bar kills the format — people refuse to draw if they think the output will be judged. The whole point is the metaphor, not the line work. Don't comment on individual drawings; comment on the whole picture once it's done. If somebody opts out and writes labels instead, that's fine; don't make participation forced.
Pitfalls
- Running it for an engineering team. They'll groan, draw stick figures ironically, and resent the time.
- Setting a specific aesthetic prompt. 'Draw in the style of...' kills the format — the metaphor is the artefact, not the art.
- Hand-waving the read. The drawing is half the work; the conversation about what's in it is the other half. Skip the conversation and you've wasted thirty minutes.
- Doing it on a 13-inch laptop with a trackpad. Drawing in Miro on a small screen with a trackpad is genuinely painful; either ship the team tablets or skip the format remotely.
Remote tips
Drawing tablets help; trackpad-only drawing is awkward enough that people disengage. If most of the team is on laptops, switch to the comic-strip variant (fewer drawings, more constrained) or run it async first. A 90-minute live drawing session on a video call with no tablets is the worst case — you'll lose the team in the first ten minutes.
Example outputs
- A team drawn as a vehicle: nobody at the steering wheel, three people in the back, the engine on fire. Conversation that surfaced: 'we're not sure who's actually leading this project.' The picture said it; the meeting that followed acted on it.
- A team drawn as a building: kitchen at the centre (regular all-hands), library at the edge (knowledge nobody reads), front door wide open (constant context-switching). Each metaphor opened a real conversation.
- A team drawn as stick figures with labels. Probably an engineering team, probably resentful. The drawing was thin because the audience was wrong.
FAQ
- Draw the Team or Personal Map?
- Personal Map is structured (eight branches, concrete categories) and works for engineering teams. Draw the Team is unstructured and works for design teams. Don't substitute. If you're an engineering manager looking at this page, you almost certainly want Personal Map.
- Draw the Team or Team Canvas?
- Team Canvas is the structured-visualisation alternative for engineers who'd hate free drawing — eight named sections, fill them in. Same family of move (make team dynamics visible); different cringe profile. Pick Team Canvas when you want the artefact without the drawing cost.
- Will my engineering team enjoy this?
- Probably not. The honest answer is most engineering teams find unstructured drawing exercises infantilising. Run it only if you have specific evidence your team will engage — a previous successful workshop, a strong design culture, or an offsite context where the cringe ceiling is lower. Otherwise run Personal Map or Team Canvas.