You already know how to run a meeting. But designing a workshop that actually changes something that’s the hard part.

This 4‑hour live session is for facilitators, UX leads, and team coaches who want to sharpen the way they design, sequence, and debrief workshops. We’ll work through real examples, build reusable templates, and break down what separates an engaging session from a forgettable one. By the end, you’ll have a reusable framework for designing any workshop, for any audience, with a clear outcome.

There are limited spots available at $449.

Think about your last workshop. How much of the time did you spend explaining what was about to happen, why it mattered, and how each step fit together? If you added it up, it might be more than you expect.

That is usually not a personality issue, it is a structural one. When every step in the session needs a lot of set-up, you end up narrating the whole way through. Participants sit and listen while you walk through the agenda and frame every activity in detail. They fixate on some future “fun” activity instead of the one in front of them, or they simply forget half of what you said by the time they need it. The way the session is built makes the workshop feel long, and it often makes it longer than it needs to be to get the work done.

Last week, I wrote about workshops that run longer than they need to; this is one structural reason why.

In UX, progressive disclosure is a design technique for reducing cognitive load by gradually revealing information as people move through a task instead of showing everything at once. It keeps interfaces easier to learn and helps people complete tasks more efficiently by limiting what they have to process at any given step.

You can borrow that, structurally, for workshops. Here, progressive disclosure means designing the sequence so you only reveal context, instructions, and structure when participants actually need them, in real time, inside the work. Each activity sets up the next, so you do not need to keep stopping to explain the whole path; you give just enough for the current step, then build on what they produce. Earlier, I wrote about why I keep agendas hidden in workshops; progressive disclosure is the same instinct applied to how and when you reveal the content itself.

In my training workshops, I am tempted to over-explain. I usually have a lot of material I want to share, and if I am not careful, I front-load the content with definitions, frameworks, objectives, and background before anyone tries anything. Participants can end up listening and taking notes while the actual learning is still on hold.

If I use progressive disclosure, I design the session differently. I build it so the opening only needs a few minutes: why they are there, what problem this training helps them solve, and what they will do first. Then I move straight into a hands-on task that forces them to surface the concepts themselves, like talking about the worst workshop they have ever experienced and using that discussion to introduce the concepts we will be covering.

The explanations arrive in small chunks during the debrief and the next round, when people have something concrete to attach them to. I end up sharing the same ideas, but:

The session feels shorter and is often actually shorter, because that whole block of redundant explanation has been removed and the teaching is folded into the activity.

If you recognise yourself in the long explanations before each step, the fix is not to become a different kind of speaker; it is to design your workshops so less explanation is needed. For your next session, you could experiment with one or two of these:

All of those are examples of progressive disclosure in workshop design: structural ways to say less while participants do more. You are getting people into the work faster and anchoring ideas in something they actually did, not in something they once heard you say. It is a simple shift, but it changes the experience: less talking about the work, more time spent doing it.