Most workshops that disappoint went wrong weeks before the day. The purpose was vague, the wrong people came, nobody agreed what success looked like, and the invitation arrived too late for anyone to prepare. The facilitator can rescue some of that in the room. Most of it, they can’t.
There’s a saying that if you have six hours to chop down a tree, you should spend the first four sharpening the axe. It’s usually credited to Abraham Lincoln. Quote Investigator found no evidence he said it, and traced early versions to an anonymous woodsman. Whoever said it, the advice holds for workshops: the preparation is most of the work.
Here’s how to plan one, as a set of questions and answers, with four figures to try, including a planner that builds your timeline from the date of the day.
Where should you start?
At the end. Decide what result the business wants from the workshop, then work backwards to what people need to do differently, what they need to learn, and how the day should feel.
The best-known way to think about this is Donald Kirkpatrick’s four levels of training evaluation. He developed them for his PhD in 1954, published them in a series of articles in 1959, and later in a book, Evaluating Training Programs (1994). The levels are reaction, learning, behaviour and results. They were designed for evaluating training, but they work just as well for planning it. Facilitators trained in the Kirkpatrick method now stress “starting with the end in mind”: begin with level 4 and work back (Wikipedia).
Plan from the top, measure from the bottom
Most workshops are only ever measured at levels 1 and 2: did people enjoy it, and did they learn something? Wikipedia notes it’s common for trainers to get stuck there, when the most useful information is in levels 3 and 4. Planning from the top is the easiest way to avoid that.
In practice, this usually starts with a discovery call with the sponsor, to put into words what the event is for and what good looks like. Once that’s agreed, every other decision follows from it.
What kind of workshop is it?
Workshops tend to do one of five jobs, and each needs a different design. A skills workshop is mostly practice. A decision workshop is mostly discussion, and pointless if the person who can decide isn’t there. Pick one and see how the shape of the day changes.
Five kinds of workshop
Many workshops try to do two jobs at once, for example teaching a new method and then using it to build a plan. That can work, as long as you know which job comes first and leave enough time for the second. If you’re short of ideas for the topic itself, ten ideas for corporate workshops has a list, with an activity for each.
How do you write the objectives?
Make them something you could check. “Improve teamwork” can’t be checked. “Each team agrees three changes to how it hands work over, with an owner for each” can, before anyone goes home. The same rules that make a goal SMART apply: specific, measurable, and with a date.
A useful test is to write the objective as something attendees will be able to do or will have produced, rather than something the facilitator will cover. Try it on these.
Which objective is stronger?
Three objectives is plenty for a day. If you have more, some of them belong to a different workshop.
Who should be in the room?
The people the objectives need, and no one else. That sounds obvious, and it’s where a lot of workshops go wrong: the decision-maker sends a deputy, the people who will do the work aren’t invited, or the room is filled to make the day look well attended.
Think about job role, experience and department. A session for new starters needs to cover the basics. One for senior managers can go straight to the strategic questions. Mixed groups work well for problem-solving and alignment, and less well for skills, where people want to practise at their own level.
Think about location too. If people are spread across sites or countries, a virtual or hybrid session might be better than flying everyone in, though some things, like building trust in a new team, are much easier face to face.
How far ahead should you plan?
Further than you think. Getting the stars to align always takes longer than expected, especially the first time. Eight weeks is comfortable for a one-day workshop. Put in the date of yours and the planner works backwards from it.
Your workshop timeline
Two steps in the timeline get skipped more than any others. The invitation should come from the sponsor, not the organiser, and say why the day matters. And the follow-ups after the day, at six weeks and three months, are where you find out whether it worked.
How do you design the day?
Build it around the objectives, in the mix the kind of workshop needs. A few things help almost any day:
- Vary the activity. Switch between input, exercises and discussion regularly. A long stretch of any one of them loses the room. It’s sometimes said this is about catering for different learning styles, but there’s little evidence that matching teaching to individual learning styles improves results. Variety helps everyone.
- Make people do things. I’m a big fan of making workshops as interactive as possible. Sticky notes and flip charts make thinking visible, let everyone contribute, and are easy to move around as ideas take shape.
- Choose the right facilitator. Someone who knows the subject, can hold the room, and can answer questions on the fly. If the workshop is about something contentious inside the business, an outside facilitator can ask the questions an insider can’t.
- Start with something that gets people talking. See how to break the ice.
- End with actions. Every workshop should finish with who does what by when. The 3-12-6 framework is one way to do it.
For an example of how a half-day fits together, see what a good half-day looks like.
How do you get people there?
Most corporate workshops are internal, so the job is making it easy and worthwhile to come:
- Invite early, from the sponsor. Diaries fill weeks ahead. An invitation from a senior sponsor, saying why the day matters, gets a different response from a calendar invite from an organiser.
- Say what’s in it for them. One or two lines on what they’ll leave with.
- Involve them before the day. Ask a question in advance, or send a short piece of pre-work. People who’ve contributed turn up.
- Use the channels people read. Email, the intranet, team meetings, and managers mentioning it to their teams.
- Get buy-in as you go. Talk to as many stakeholders as you can during the planning, so nobody is surprised by the day or its outcomes.
If it’s a public workshop, the usual routes still work: LinkedIn events, your email list, and listing sites such as Eventbrite.
How do you know if it worked?
Go back to the four levels. Ask for reactions at the end of the day, and keep it short. Check the learning in the room, through the work people produce. Then do what most organisers don’t: check behaviour at six weeks, and results at three months, against the measure you agreed with the sponsor at the start.
Ask for feedback too, and act on it. It’s the cheapest way to make the next one better.
What mistakes should you avoid?
- Starting with the agenda. The agenda comes from the objectives, not the other way round.
- Vague objectives. If you can’t check it, it isn’t an objective.
- The wrong people. Especially the missing decision-maker.
- Too much content. A day with too much in it ends with no time for the actions.
- No follow-up. Without it, most of what was learned fades, as the forgetting curve shows.
- Too little notice. Eight weeks is comfortable. Three is a scramble.
Can AI help?
Yes. An AI assistant can draft objectives from a sponsor’s brief, suggest activities for each part of the day, write the invitation, and turn the flip charts into a tidy summary afterwards. It’s a fast way to get a first version of each.
What it can’t do is the discovery conversation with the sponsor, or read the room on the day. Those are still the most important parts of the job.
Sources: Quote Investigator, To Cut Down a Tree in Five Minutes Spend Three Minutes Sharpening Your Axe; Wikipedia, Donald Kirkpatrick; Kirkpatrick, D.L. (1994) Evaluating Training Programs, Berrett-Koehler; Wikipedia, Learning styles.