Running a workshop that people remember a month later

Ask people about a workshop they attended last year and most will remember the lunch and the trainer’s personality — not what they learned. The sessions that stick are built differently. Here is how we structure ours.

Decide the one thing before you decide anything else

Every workshop should have a single sentence: “by the end of today, everyone can _____.” Not three things. One. Every exercise, every example, every slide either serves that sentence or gets cut. A workshop that tries to cover everything covers nothing.

Front-load the “why”, then get out of the way

People need about fifteen minutes of context — why this matters, where it fits, what good looks like. After that, talking at them has sharply diminishing returns. The rest of the day should be participants working, with the trainer moving between them.

Use their real work as the material

Generic exercises produce generic learning. When participants bring their actual report, their actual dataset, their actual presentation, two things happen: they are more engaged, and they leave with something already improved. The workshop pays for itself before it ends.

Build in a “stuck” checkpoint

Halfway through the day, stop and ask what isn’t landing. There is always something. Adjusting in the moment — slowing down, re-explaining, pairing people up — is worth more than sticking to the plan.

End with the day after, not a summary

The last twenty minutes are the most wasted in most workshops, spent recapping. Use them instead to answer: what will you do differently on Monday, what do you need to make that happen, who will check in with you in two weeks. Send people out with a plan, not a feeling.

The test

A month later, the question is not “did they enjoy it”. It is “are they doing the thing”. If the structure above is right, the answer is usually yes — and that is the only measure that matters.