Managing

How to run a workshop

A workshop works when the group leaves with something they could not have made alone: a decision, a plan, a set of agreements someone owns. Getting there is mostly design and sequence, not charisma. Below is the arc, the actual sentences to say at the hard moments, and what to do when the room goes flat.

A workshop is not a meeting with biscuits, and it is not a presentation with pauses for questions. It is a session designed so that a group produces something. If the group could have received the same content by email, you have run a briefing and called it a workshop.

Design backwards from the output

The most common reason workshops fail is that they were designed around a topic instead of an output. "A workshop on communication" has no finish line, so it never crosses one. "By four o'clock we will have agreed three handover rules and a named owner for each" does, and it quietly rules out half the activities you were considering.

Write that sentence before you write a single agenda item. Then work backwards in this order:

  1. The output. One sentence, written as if it has already happened. Test it: could a stranger walk in at the end and see whether you got it?
  2. The smallest number of steps that could produce it. Most drafts have twice as many activities as the day can hold. Cut until it feels slightly under-planned. It won't be.
  3. The material the group brings. Real cases, real decisions, real friction. Generic scenarios produce generic conversation.
  4. The timings, out loud. Say each block's length to yourself. "Twenty minutes for that" usually means forty.

Then check the room, the group size, and who is in it. Twelve people is a workshop; thirty is a conference session with breakouts, and needs a different plan. If someone's manager is in the room, you have a different design problem again, covered further down.

The arc of a working session

Almost every effective workshop, from ninety minutes to two days, runs the same five movements. The proportions matter more than the labels.

  1. Frame (about 10% of the time). Why we are here, what we will leave with, how I will run it.
  2. Surface (about 25%). Get what is already in the room out of people's heads and onto a wall, a doc or a screen. No evaluation yet.
  3. Sort (about 25%). Group, compare, argue. This is where the real disagreement lives, and where most facilitators flinch.
  4. Decide (about 25%). Narrow to what the group will actually do. Fewer, sharper, owned.
  5. Commit and close (about 15%). Names, dates, next contact. Protect this block with your life.

Notice that content delivery is not one of the five. If you need to teach something, it belongs inside Frame or just before Sort, in blocks of no more than ten minutes. Longer than that and you have switched the group from participants to audience, and switching them back is harder than it sounds.

The first five minutes

The opening sets the contract for the whole session: who talks, how honest we are, whether this is worth anyone's attention. Four moves, in order.

Start on time, with whoever is there. Waiting for stragglers teaches the room that your timings are decorative.

Say the output out loud. Something like: "By four o'clock we will have three agreed handover rules and a name against each one. If we leave without that, today did not work." It sounds blunt. It is the most useful sentence in the session.

Say how you will run it. Try: "I am not the expert on your work. My job is to keep time, keep us on the question, and make sure the quiet half of this room gets heard as much as the loud half." That last clause does a lot of work later, when you interrupt someone.

Get every voice into the air inside five minutes. Not an icebreaker for its own sake, but one round where each person says a sentence: what they are hoping to stop doing after today, or the one thing that would make this a waste of their afternoon. Someone who has not spoken in the first ten minutes usually will not speak at all. If you need prompts, borrow from icebreaker questions for work, but keep them tied to the task.

You are not there to supply the answers. You are there to make sure the group's answers surface, get tested in public, and turn into something a named person owns by Friday.

What to say instead

Most facilitation advice stops at principles. Here are the specific moments, the reflex most of us reach for, and the line that actually moves the room.

The momentThe reflexBetter
Nobody answers your opening question"Anyone? No? Okay, I'll start us off then.""Ninety seconds on your own. Write one line. Then I'll go round the table."
One person is dominating"Let's hear from someone else.""Hold that thought, I want to bank three other views first, then come straight back to you."
The group keeps circling the same argument"Let's park that.""We've had this one twice now. What would we need to know to settle it, and who can find that out by Friday?"
Someone challenges the exercise itself"Trust the process.""Fair. Tell me what would make the next hour worth your time, and I'll adjust."
The most senior person answers first, every timeYou say nothing and move on"Let's do this one in writing first, so we get everyone's version rather than the first version."
The room goes flat after lunch"Stay with me, we're nearly there.""Everyone up. Two minutes, find someone you haven't spoken to today, tell them your one takeaway so far."

Read those aloud once before the session. Lines you have said out loud arrive on time; lines you have only read arrive about four seconds too late, which is exactly when you needed them.

Keeping the middle honest

The middle is where workshops sag. A few habits keep it alive:

When it goes wrong

The room goes silent

Almost always a safety problem or a difficulty problem, not a motivation problem. Switch from speaking to writing: silent two minutes, everyone writes, then you read a few out anonymously. Written first, spoken second, is the single most reliable fix in facilitation, and it also stops the fastest talker setting the frame. If silence persists across the day, the issue is psychological safety, not your questions.

The group argues with the exercise

Do not defend the design. Name it and renegotiate in public: "You're right that this is a bit abstract. Give me the real version. What's the actual decision you're stuck on this month?" Resistance is usually information about the design, arriving rudely.

The sponsor takes over

Agree their role before the day, not during it. In the room: "I want your view on this, but last. If it comes first it becomes the only one." If they are the reason people are quiet, use the mid-session break to ask them to sit out one block. Most will, if you ask privately and give a reason.

You run out of time

You will. Cut content, never the close. Say it plainly: "We're not getting through the third section. I would rather leave with two things we actually do than four we half-discussed. Any objection?" A workshop that ends with three owned actions and no theory beats one that ends with a full deck and nothing owned.

The close is the part everyone cuts

Ten minutes short, and the natural instinct is to squeeze the ending. That is exactly backwards: the ending is what converts a good conversation into changed behaviour.

  1. Commitment round. Every person, one sentence: what I will do, and by when. Out loud, in front of the others. Public specificity is the whole mechanism.
  2. Write it down where they can see it, and send it within a day while the language is still theirs.
  3. Book the follow-up before anyone leaves the room. Twenty minutes in three weeks. Without it, the list decays quietly.
  4. Ask one question about the session itself: "What would you change about how we ran today?" Take the answer without defending. It is the cheapest facilitation training you will get.

Why reading this will only get you part of the way

Everything above is learnable in an afternoon and hard to do at 2:40pm when a director is talking over a junior and the clock is against you. Facilitation is a performance skill, like presenting or interviewing: it changes through rehearsal, live feedback and a second attempt, not through understanding. Run a short session, get someone to watch you and tell you one thing, then run it again. That loop is the entire method behind experiential learning, and it is why the third workshop you run is unrecognisably better than the first.

If you want a lower-stakes place to start, the same moves apply at smaller scale in effective meetings. Practise interrupting the dominant voice there, where it costs nothing, and it will be available to you on the day it matters.

Tour De Force runs this as live, experiential training for teams worldwide — online and in person. Talk to us, or play Gamified learning appsThe Weekly Challenge to see the method in ten minutes.

Questions

How to run a workshop FAQs

How do you structure a workshop?

Work backwards from the output. Write one sentence describing what the group will leave with, then build five movements: frame it (about 10% of the time), surface what people already think (25%), sort and argue (25%), decide (25%), then commit and close (15%). Content delivery sits inside the frame in blocks of ten minutes or less.

How long should a workshop be?

Long enough to reach a real decision, short enough to hold attention. Ninety minutes suits a single question; half a day suits a topic with genuine disagreement in it. Two full days is rarely about capacity and usually about travel logistics. Whatever the length, change format every twenty minutes and protect the last fifteen for commitments.

What is the difference between a workshop and a meeting?

A meeting coordinates: it shares updates, checks progress and assigns work. A workshop produces: the group makes something during the session that did not exist beforehand. The test is simple. If the same result could have arrived by email or a status update, it was a meeting wearing a workshop's clothes.

How many people should attend a workshop?

Eight to fourteen is the comfortable range for one facilitator: small enough that everyone speaks, large enough for real disagreement. Above about twenty you are running a conference session and need table-level structure, timed breakouts and someone helping you. Below six, the format is often better run as a working session or a series of one-to-ones.

How do you get a quiet group to participate?

Switch from speaking to writing. Give two silent minutes, have everyone write, then read a few out. Written-first stops the fastest talker setting the frame and gives slower thinkers a fair start. If quietness persists all day, the cause is usually safety, seniority in the room or an unclear task, not shyness.

How do you run a workshop online?

Same arc, tighter blocks. Halve the length of every segment, use breakout rooms of three rather than open discussion, and put everything in a shared document so thinking stays visible. Ask for cameras but do not fight over them. Above all, use the chat and the doc as legitimate ways to speak, not as a second-class channel.

Keep reading

Related reading

Get in touch

Build it with your team.

Book a 30-minute discovery call and we'll shape an experiential programme around your goals.

Book a discovery call