Marcus Andrey Study
Ler em português Library

Framework · Facilitation techniques · 3 min read

Workshop canvas

Why now, outcome, participants, decision method, pre-work, agenda, materials, risks, follow-up. No clear outcome means no workshop.

1Why now

The problem behind the workshop.

e.g. three filter patterns in three apps
2Outcome

The tangible output: decision, prioritised list, map or principles.

No outcome, no workshop
3Participants

Who comes and why each one. Max 8–10 per facilitator.

e.g. 6 designers, 2 developers
4Decision method

Vote, consent or a named approver. Decided before you start.

e.g. consent, approver = UX lead
5Pre-work

What participants read or do beforehand.

e.g. screenshot your current filters
6Agenda

Activity, purpose, diverge or converge, minutes.

e.g. 20 min silent inventory
7Materials

Board, templates, data, user quotes.

e.g. FigJam board with frames
8Risks

Dominant person, politics, missing decision maker, and mitigations.

e.g. senior voice: silent writing first
9Follow-up

Who sends the summary, by when, where it is stored.

e.g. summary within 24 hours
The workshop canvas is filled in before anyone is invited, and the Outcome box decides whether you need a workshop at all.

Use it when

  • Someone asks you to "run a workshop" and the goal is not yet clear.
  • You plan a session that crosses teams, where the decision method and the right people matter.
  • A past workshop ended with lots of stickies and no decision, and you want to avoid that next time.

How to use it

  1. Write why now and the outcome. Name the problem behind the workshop and the tangible output: a decision, a prioritised list, a map or principles. If you can't, stop here and send an email instead. Output: one problem and one outcome.
  2. Choose the participants. Write who comes and why each one is needed. Plan a maximum of 8–10 people per facilitator. Output: a short list with a reason per person.
  3. Decide how you'll decide. Pick the decision method before the session: vote, consent, or a named approver (DACI). Output: a decision method you can state in the invite.
  4. Plan pre-work, agenda and materials. For each agenda block, write the activity, its purpose, whether it diverges or converges, and the minutes. See Diverge and converge. Output: a timed agenda and a ready board.
  5. Name the risks. Think about a dominant person, politics or a missing decision maker, and write a mitigation for each. Output: risks with mitigations.
  6. Plan the follow-up. Name who sends the summary, by when (within 24 hours), and where it is stored. Output: a follow-up owner and date.

Worked example

A UX lead plans a 2-hour design-system workshop on data table filtering for an internal operations platform with 6 product teams.

Field What the lead wrote
Why now Three apps filter tables in three different ways; users who switch apps make mistakes.
Outcome One agreed filtering standard, tiered core or recommended.
Participants 6 designers (one per team, they know the use cases) · 2 frontend developers (build cost) · design-system designer (owner).
Decision method Dot vote for direction, then consent decision. Approver = UX lead.
Pre-work Each designer posts screenshots of their current filters.
Agenda Context 10 · use-case inventory 20 · affinity 20 · break 10 · sketching 25 · converge and consent 20 · DACI 15.
Materials Board with one frame per team, screenshots, two user quotes.
Risks One senior designer dominates: silent writing first. The frontend lead may not come: confirm attendance two days before.
Follow-up Design-system designer sends the summary within 24 hours, stored on the design-system page.

Watch out for

  • No outcome, still a workshop. A workshop without an outcome erodes trust in future workshops. Use a meeting or an email.
  • Deciding how to decide in the room. If the method is unclear, the group argues about process at the end. Put it in the invite.
  • Too many people. More than 8–10 per facilitator means fewer voices are heard. Split the group or add a co-facilitator.
  • Forgetting the follow-up. The summary is what people remember. Send it within 24 hours.

Template

Copy this before every workshop.

WORKSHOP CANVAS
Title:
Why now (the problem behind the workshop):
Outcome (the tangible output: decision / prioritised list / map / principles):
Participants (who + why each one; max 8–10 per facilitator):
Decision method (vote / consent / approver = ___):
Pre-work (what participants read/do beforehand):
Agenda (activity — purpose — diverge/converge — minutes):
Materials (Miro/FigJam board, templates, data, user quotes):
Risks (dominant person? politics? missing decision maker?) & mitigations:
Follow-up (who sends summary, by when, where is it stored):
Saved only on this device.

↑ ↓ to move · Enter to open · Esc to close