How to run a design thinking workshop
A workshop is won or lost before it starts. This guide covers who does what, how to set up the room or the board, the facilitation moves that work, and how to chain methods into a half-day or a full day.
Roles in the room
One person can hold two roles in a small group. Do not hold three.
- Facilitator. Runs the process, not the content. Keeps time, keeps voices even and protects the quiet ones.
- Scribe. Captures notes and decisions visibly. Writes what was said, not what they think it meant.
- Timekeeper. Calls the clock out loud and helps the facilitator say no to extensions.
- Sponsor. Opens with the why and returns to close. Does not lead the content and speaks last.
- Domain expert. Answers questions of fact. Joins the group and does not steer it.
- Frontline voice. Someone who does the work. Without them the output reads as theory.
Set-up in the room
- One table per group of five or six, round if possible.
- Wall space for notes. Test the tape.
- Sticky notes in one colour, and markers thick enough to read at two metres.
- Print the canvas at A1 or A0, or A3 per table.
- Phones away unless needed. Agree a break time.
- Water and food. People stay longer when fed.
Set-up for a remote workshop
- One shared board with the canvas pre-loaded. Test access before the day.
- Cameras on for the first and last ten minutes.
- Silent writing in the board, not in chat.
- Break-out rooms of three or four, with a scribe in each.
- Keep sessions to 90 minutes with a break. Concentration falls faster remotely.
- Send a short note beforehand with the aim and time.
Facilitation moves that work
| Move | What to do |
|---|---|
| Open | State the aim, the output and the time. Say what will not be decided today. |
| Start in silence | Ask people to write alone first. It protects the quiet and the junior. |
| One idea per note | Easier to cluster and vote. Fewer long notes means fewer speeches. |
| Defer judgement | No "yes, but" while generating. Judge later against criteria. |
| Park, do not argue | Keep a visible parking board. Write it down and move on. |
| Close | Read the output aloud. Ask what has changed. Name the next step and who owns it. |
The shape of every session
- Open (5 minutes). Aim, output, time and rules.
- Warm up (5 minutes). One easy question so every voice is heard.
- Do the method. Follow the steps and timings on the method page.
- Review (10 minutes). Read the output aloud. What stands out?
- Close (5 minutes). Next step, owner and date.
Add ten to fifteen minutes to the method time for the open and close. In a half-day workshop, add a fifteen-minute break after each ninety minutes.
Fitting the method to the group and the time
| Situation | Methods that fit | How to run it |
|---|---|---|
| 2 to 3 people | Interview Guide, Five Whys, Day-in-the-Life Walkthrough, Idea Card | One person leads, one writes. Keep it conversational. |
| 4 to 12 people | Most mapping, framing and placement methods | The sweet spot. One table, one facilitator. |
| 13 to 25 people | Write, Pair, Share, Dot Voting, Pains and Gains Board, Pre-mortem | Break into tables of five or six, each with a scribe, then report back. |
| More than 25 people | Write, Pair, Share, Dot Voting | Use sub-groups and a short plenary. Expect shallow output. |
| Under 30 minutes | Five Whys, Crazy 8s, Dot Voting, Idea Card | One method, one output. Do not combine. |
| Half a day or more | Map, then frame, then ideate | Chain methods so each feeds the next. |
When executives are in the room
Several methods work well with executives. A few need a short briefing first.
- Brief the most senior person beforehand, and agree they will speak last.
- Use silent writing so ideas arrive without rank attached.
- Keep to the time. Executives value a clock.
- Show the output as a one-page summary at the end.
- Ask for decisions you actually need.
- Avoid methods marked "better with a working team". They need detail that executives do not have time for.
- Do not let a sponsor reframe the problem during ideation, and do not ask for a vote on something they have no information about.
- Say "task" instead of "use case" until the group does.
Sample workshop flows
| Workshop | Methods, with minutes | You leave with |
|---|---|---|
| Half-day: define the problem | Stakeholder and Impact Map (40), Pains and Gains Board (30), Affinity Clustering (40), Problem Statement (30) | An agreed problem and stakeholders |
| Half-day: find a use case | Day-in-the-Life Walkthrough (45), Automation Fit and Trust Cost Placement (40), Idea Card (25) | One to three scored tasks |
| Full day: ideas to a choice | How Might We (30), Crazy 8s (15), Idea Card (25), Value and Feasibility Placement (30), Dot Voting (15) | A ranked shortlist |
| Two hours: test an idea | Pre-mortem (30), Trust and Oversight Check (35), Experiment Card (25) | Risks named and a test planned |
The free Workshop Toolkit includes a facilitator checklist and printable canvases for every method in Understand, Frame, Ideate and Select.
Questions
How long should a design thinking workshop session be?
Keep each session to the method time plus ten to fifteen minutes to open and close. In a half-day workshop add a fifteen-minute break after each ninety minutes. Remote sessions should be kept to 90 minutes with a break.
How many people should be in a workshop?
Four to twelve people is the sweet spot for most methods, with one table and one facilitator. Larger groups should be split into tables of five or six, each with a scribe.
How do I run a design thinking workshop remotely?
Use one shared board with the canvas pre-loaded, write silently in the board and not in chat, use break-out rooms of three or four with a scribe in each, and keep sessions to 90 minutes with a break.
How do I run a workshop with executives?
Brief the most senior person beforehand and agree they will speak last, use silent writing, keep strictly to time, show the output as a one-page summary, and only ask for decisions you need.