Brainstormer

Empathize to test, time boxed

Design thinking workshop activities, exercises and a full-day agenda

A design thinking workshop moves a group through five stages, empathize, define, ideate, prototype and test, against one real user problem. A workable full-day format spends roughly 90 minutes each on empathizing and defining, two hours ideating, and the afternoon on a rough prototype and a test plan. Six to ten participants is the practical range, and the session is judged by the artifact each stage hands to the next, not by how energized the room felt at 5pm.

Last updated July 2026

  • Every stage has a time box, an exercise and an output it owes the next stage
  • The ideate stage runs on forced angles, not on whoever talks first
  • Clustering and scoring happen in the room, so the wall becomes a shortlist
  • Works the same remotely: participants add silently, the facilitator reveals the wall
Get started

No credit card needed.

Brainstorm Studio
Try it: pick a challenge

Challenge:

+ more on the wall

Winner

score / 10

Why

Sample brainstorm shown. Your challenges stay private.

◇ A one-day design thinking workshop agenda: what each stage costs, produces and prevents
Stage Time box (full day) Activities that work What the stage owes the next one What goes wrong without it
Empathize 90 minutes Interview playback, empathy mapping, journey mapping from real support and usage evidence Quotes and observations from actual users, not opinions about users The room solves the problem the loudest attendee brought from their inbox
Define 60 to 90 minutes Affinity clustering of the evidence, then one point-of-view statement converted into How Might We questions A single agreed problem statement, narrow enough to answer and wide enough to have several answers Five people ideate on five different problems and nobody notices until the readout
Ideate 2 hours Silent brainwriting, SCAMPER, Six Thinking Hats, Crazy 8s, reverse brainstorming, then clustering and dot voting A wall of genuinely different options, collapsed into two or three named territories and scored Thirty variations on the first idea anyone said out loud
Prototype 90 minutes Paper sketches, clickable wireframe, storyboard, or a scripted role play of the service One artifact concrete enough that a stranger can react to it The team ships an opinion instead of something testable
Test 45 to 60 minutes Five-user feedback round, or a written test plan with recruiting criteria if users are not on site A list of what was wrong and what to try next, with an owner and a date Everyone leaves confident and nothing gets validated

What is a design thinking workshop?

A design thinking workshop is a facilitated working session that takes a group through the five stages of design thinking against one specific user problem, and ends with something tangible: a defined problem, a shortlist of solutions, a rough prototype and a plan to test it. The format came out of Stanford's d.school and IDEO's practice, and it spread into corporate innovation because it forces the two things that meetings usually skip, which are grounding the problem in evidence and generating more than one option before committing.

It is a workshop, not a training course. The distinction matters when you are buying: an off-the-shelf design thinking training day teaches the method using a fake brief, while a workshop applies the method to a live problem you actually own. If your goal is a decision on a real challenge, run the workshop and pick up the method along the way. Our page on the wider innovation workshop tool covers the shorter, generation-only version of the same arc.

What are the 5 stages of a design thinking workshop?

Empathize, define, ideate, prototype, test. Empathize gathers real evidence about the people with the problem. Define turns that evidence into one agreed problem statement. Ideate produces many possible solutions to it. Prototype makes the most promising one concrete enough to react to. Test puts it in front of users and collects what was wrong.

The stages are non-linear in practice, and skipping backward is normal: a test result routinely sends a team back to define. What is not optional is the handoff. Each stage owes the next one a specific artifact, and the table above names them. Workshops fail most often at the define stage, because a group that has not agreed on the problem will still happily ideate for two hours. If you want the framing step done properly, the guide to writing a How Might We question and the comparison of How Might We versus a problem statement both work through the conversion with real examples.

How long should a design thinking workshop be?

One full day is the shortest format that gets through all five stages honestly. Two hours can cover define and ideate for a problem the team already understands. A half day works when the research is already done and you are starting at define. Two days is the right call when the problem is genuinely new, because it gives you a second round of ideation after the first prototype fails, which is usually where the good idea shows up.

Practical guidance from facilitators who publish their agendas lines up here: plan three to four substantial activities in a one-day session and six to eight across two days. More than that and you are running a demo of design thinking rather than doing it. The five-day compressed version has its own name and its own rules, and we compare the two on the design sprint tool page and in what is a design sprint.

Design thinking workshop activities and exercises that earn their time box

Empathize runs on evidence, so the strongest exercises are the ones that put real material in the room: playing back three recorded user interviews, mapping a journey from actual support tickets, or building an empathy map from quotes rather than guesses. Define runs on convergence: cluster the evidence into themes, name each theme, and write one point-of-view statement the whole group signs off on.

Ideate is where most of the value and most of the wasted time live. Start silent. Brainwriting has everyone write before anyone speaks, which stops the first idea from anchoring the group, and the research on why that matters is in why group brainstorming fails. Then apply a lens: SCAMPER stretches an existing solution seven ways, Six Thinking Hats stops optimism and risk from cancelling out inside the same five minutes, and Crazy 8s forces eight sketches in eight minutes when the room is over-thinking. Close ideation with clustering and impact versus effort scoring, so the wall leaves the room as a ranked shortlist. For the full menu with time boxes, our page of innovation workshop activities maps twelve exercises to the stage and group size each one needs.

Who should attend a design thinking workshop?

Six to ten people, mixed on purpose. Below six you lose the cognitive diversity the method depends on. Above ten, every timed activity stretches and the session turns into an audience watching three people talk. Bring product, design, engineering, marketing or customer success, and at least one person who speaks to customers daily, because that person is the reason the empathize stage has anything real in it.

Decision makers are the recurring problem. An executive who attends but does not participate either silences the room or redirects it with an opinion nobody can outrank. The fix is a rule stated before the session starts: everyone in the room works under the same rules, and anyone who only wants the outcome gets the readout instead. Facilitators running these for clients tend to work from the consultant workflow, and in-house design and product groups from the designer and product team setups. Whoever facilitates should not also contribute ideas, and the practical mechanics of holding that line are in how to facilitate a workshop.

How do you run a design thinking workshop remotely?

The same five stages, with two changes. First, move the silent work off the call: participants write their ideas and their evidence into the wall before anyone speaks, and the facilitator reveals everything at once. That is closer to the intent of the method than an in-person session where the extrovert starts talking at minute one. Second, shorten the day. Four hours of remote workshop is harder than six hours in a room, so run a full-day agenda as two half-days a few days apart and use the gap for real user contact.

Distributed groups also need the output to survive the call, which is where a canvas alone falls short. A whiteboard arranges ideas that already exist; it does not produce them, and it does not score them. The setup for asynchronous and hybrid sessions is described on our online brainstorming page, and the tools worth pairing are broken down on facilitation tools and in the honest roundup of brainstorming software with current prices.

Where this tool fits in the day

Brainstormer is built for the ideate stage and the convergence that follows it. Type the problem statement your define stage produced, and the studio above returns dozens of tagged directions in about thirty seconds, each one flagged with the angle it came from so ten ideas are ten actual directions rather than ten rewordings. Switch on a lens mid-session and the wall widens again in front of the room. Then cluster into named territories, score impact against effort, and leave with one pick and the reasoning written down.

What it does not do is replace the empathize and test stages, and any tool that claims otherwise is selling you something. Real user contact is the part of design thinking that makes the rest worth running. Pricing is per seat with no AI credit meter: Solo is $16 per month, Pro $39, Team $99 for five seats with a shared workspace. Put your actual workshop challenge into the studio above and see what the ideate stage would look like before you book the room. If the ideate stage is what you want to read about in depth, our article on design thinking ideation covers the techniques stage by stage, and design thinking vs agile covers where the workshop sits relative to your delivery process.

Questions

What is the agenda for a design thinking workshop?

A one-day agenda runs about 90 minutes on empathize, 60 to 90 on define, two hours on ideate, 90 on prototype and an hour on test, with breaks between stages. Each block ends with a named artifact rather than a discussion, which is what stops the day from drifting.

How many people should attend a design thinking workshop?

Six to ten participants plus a facilitator who does not contribute ideas. Fewer than six and the group lacks the range the method needs. More than ten and every timed exercise stretches, so if you need more voices, split into parallel groups and merge the walls at the clustering step.

What is the difference between a design thinking workshop and a design sprint?

A design thinking workshop is a format for applying the five stages, usually one to two days, and it can stop at a shortlist. A design sprint is the specific five-day Google Ventures process that always ends with a prototype tested on five real users. The sprint costs far more people time and buys evidence rather than a decision.

Do you need a whiteboard tool to run a design thinking workshop?

No. You need a way to capture evidence, generate options, cluster them and score them. A whiteboard covers capture and arrangement well and generation not at all, which is why most teams pair a canvas with something that produces and ranks the options.

Can a design thinking workshop work with no user research done beforehand?

It can, but the empathize stage has to be real rather than imagined. Playing back three recorded interviews or reading fifteen support tickets aloud takes 45 minutes and changes the entire session. Skipping straight to ideation with assumed user needs is the single most common reason these workshops produce nothing anyone acts on.

From blank page to a decided direction

Plans from $16 per month. Every framework included.

Get started