You don't need another workshop. You need a decision.
I have a bit of a problem with designers who love the process more than the outcome.
There, I’ve said it… anddddd relax.
I’ve spent years running workshops, facilitating discussions and getting people into rooms to solve problems. I love a good workshop, especially when you get the right people together, challenge each other and actually move something forward. It’s fun, and it’s really interesting to chat with very smart people who bring snacks.
BUT, with the good comes the bad. I’ve also sat through far too many where we spend hours talking, fill a wall with sticky notes, congratulate ourselves on a brilliant session and leave without making a single decision or one damn job-to-do.
And then somebody suggests another workshop.
Bloody hell.
I think there’s a point where collaboration stops being useful and becomes an expensive way to avoid decisions, and I mean expensive in more ways than one.
Put ten people in a room for two hours, and you’ve just used twenty hours of someone’s money. That’s before you account for the preparation, travel, follow-up and everything else that goes into making it happen.
There’s also the personal cost. If I’m travelling to London to run a workshop, I’ve probably spent hours preparing, travelled down, facilitated the session, caught a train home and then walked through the door to be a dad. That’s a lot of energy for something that might produce absolutely nothing.
And the worst bit? Within minutes, you can often tell that the workshop hasn’t been properly thought through.
There’s no structure, no clear direction and no agreement about what we’re actually trying to achieve. One person ends up controlling the conversation while everyone else either talks around the problem or switches off.
I’ve become much more comfortable stepping in when that happens. I park irrelevant conversations, challenge people who are dominating the room and bring quieter voices into the discussion.
But most importantly, I make sure we leave with something. A job, a task, something that actually moves us forward.
If we’ve got three possible directions, brilliant. Let the decision-maker choose one. If they can’t decide, then let’s agree they’ll make the call tomorrow and explain it to the team.
If we genuinely need another conversation, fine. But let’s timebox it to an hour, make sure everyone comes prepared and agree that we’re leaving with a decision.
Another thing that frustrates me is how often designers run workshops with only other designers.
Where are the developers? The product people? The delivery people? Where’s the understanding of what users actually need, what we can build and when we need to deliver it?
You can’t spend weeks designing something in isolation and then act surprised when development pushes back or delivery tells you there’s no time.
And yes, sometimes discovery genuinely is too short. But sometimes I wonder whether we’ve become so comfortable exploring problems that we’ve forgotten we’re supposed to help solve them.
I’m not saying every workshop needs to end with a fully formed solution. Sometimes understanding the problem better is exactly the outcome you need, but there should always be an outcome. A decision, a direction, a question answered, an assumption challenged or a clear next step with someone responsible for it.
Otherwise, what have we actually achieved?
I love collaboration. I love bringing people together and making space for different perspectives, but I don’t want to spend two hours talking about what we could do when we could spend that time getting closer to doing it.
Sometimes you don’t need another workshop - you need a decision.