Three hours. Twelve people. A Miro board with 94 sticky notes, colour-coded by theme, dot-voted into a rough priority order. The facilitator called it a wrap. Everyone said it was productive. The PM took a screenshot of the board.
That screenshot is still in a Slack channel. Nobody has looked at it since.
Twelve people at a blended rate of $130/hr. Three hours. That’s $4,680 for a JPEG.
Six weeks later the team is designing the same feature they were designing before the workshop. When someone asks what was decided, there are four different answers. None of them match the screenshot.
This is what most UX design workshops actually produce: a feeling of alignment that evaporates the moment people open their laptops.
A UX Design Workshop Is Not a Brainstorm
The word “workshop” has been so thoroughly abused in product teams that it now means almost anything. A call where someone shares their screen. A Figma review. An afternoon of sticky notes with a vibe of collaboration.
A UX design workshop is a decision-making event. That’s it. You enter with a problem you haven’t solved. You leave with a decision that is written down, owned by one person, and specific enough that the designer knows what to do tomorrow morning.
If you didn’t leave with that, you didn’t run a workshop. You ran a very expensive brainstorm.
What a UX Design Workshop Should Actually Produce
One written decision. Not a list of insights. Not a ranked backlog of ideas. Not a shared understanding of the problem space – though that can happen along the way.
The output is a sentence. “We are designing X for user Y, solving problem Z, and we’re not solving [the thing everyone wanted to also solve].” Signed off by the person with the authority to sign off. Before anyone leaves the room.
Everything else – the sticky notes, the affinity mapping, the crazy eights, the dot voting – those are inputs to that sentence. They are not the output.
If the workshop ended without that sentence, it didn’t end.
Four Reasons Yours Probably Didn’t Work
Too many people in the room. Workshops expand to fill whoever is invited. Twelve people means twelve opinions, at least three of which directly contradict each other, and a facilitator who spends 40% of the session managing dynamics instead of driving to a decision. Every person you add past five increases the chance of a deferred outcome by more than it increases the quality of the thinking in the room. Five is the right number. Maybe six. Beyond that you’re running a committee, not a workshop.
Nobody was empowered to decide. The most common failure. You run the whole session, surface genuine insights, reach a natural conclusion – and then nobody says “we’re going with this.” Because the person with actual authority wasn’t in the room, or was in the room but unwilling to commit in front of the group. The decision gets deferred to a follow-up meeting. That meeting never happens with quite the same energy. Three weeks later someone makes the call alone, in a Slack message, at 11pm.
The facilitator ran activities instead of driving to a decision. There is a version of workshop facilitation that is really just activity management – here’s the exercise, here’s the timer, here’s the debrief. It feels structured. It produces nothing bindable. Good facilitation is uncomfortable. It means interrupting a discussion that’s going in circles, asking “what are we actually deciding here,” and holding the room to an answer when everyone wants to keep exploring.
No pre-work. When teams skip it, the first 45-60 minutes of a three-hour workshop is spent getting everyone to the same starting point. By the time you’re ready to decide anything, people are tired, one person has checked their phone four times, and the calendar says you have 30 minutes left. You schedule a follow-up. The follow-up becomes optional.
The Test
One question. Ask it at the end of every UX design workshop before anyone closes their laptop.
“If I emailed the team tomorrow and said we’re going with [X], would anyone be surprised?”
If yes – you haven’t decided yet. Stay in the room.
If no – you’re done. Write it down. Send the email.
Before the Workshop
Send a two-paragraph brief 48 hours ahead. Problem in one sentence. What you need to decide – specifically, not “the direction.” Anyone who doesn’t read it doesn’t attend.
Five people maximum. The designer. The PM. One engineer. One person who talks to users. The person who can say yes.
If that last person can’t make it, reschedule. There is no point running a ux design framework session where the output needs approval from someone who wasn’t in the room. You already know how that ends.
During
The facilitator’s job is to get to the decision, not to make everyone feel heard. Both can happen. But when they conflict, the decision wins.
Time-box the divergent part hard. 45 minutes of problem exploration, maximum. Then pivot. “We’ve heard the space. What are we deciding?” Don’t let the team escape back into exploration when a decision gets uncomfortable – and it will get uncomfortable, because committing to one direction means closing off three others that people liked.
Write the decision in progress on the board, in plain language, as the conversation converges. Make it visible. Make people react to the words, not the abstract concept.
After
One person sends a summary within two hours. Not the Miro link. Not the photo. A paragraph: what we decided, who owns it, what happens next and by when.
If that paragraph is hard to write, the workshop didn’t produce a decision.
The summary is the real output. The workshop was just how you got there. For how this feeds into the ux design stages that follow, the decision from the workshop is the brief that everything else runs on. Without it, the stages start with a guess dressed up as a direction.
A UX design workshop takes three hours, twelve people, and $4,680 of salary, and produces a screenshot nobody looks at.
Or it takes two hours, five people, and produces a sentence that tells the designer exactly what to build.
The difference isn’t the activities. It’s whether anyone in the room was willing to say: we’re going with this, and we’re not going back.
We’re strict about this because a workshop that doesn’t decide anything is just a meeting with better snacks.