Musing 11 · Workshop design

Don't close the workshop. Land it.

Why do people leave a workshop feeling aligned, then return with different interpretations of what was decided?

A workshop can create clarity and alignment in the room, then lose it again on the way out. “Next steps” help. Designing the landing goes one level deeper.

The thought

We spend a lot of time designing what happens inside a workshop. We think carefully about the questions, activities, sequence, room and conversations we want people to have. We try to create the conditions for good thinking, useful challenge, alignment and progress.

But I’m increasingly wondering whether we spend enough time designing what happens immediately after the workshop.

I’ve been thinking about the idea of collaboration debt. It describes the friction that builds when gaps in process, relationships and information are left unresolved. Context gets lost, decisions are revisited, and people leave with different interpretations of what happened. None of these things may feel significant in the moment, but over time they make collaboration slower and harder.

A well-designed workshop should help reduce some of that debt. It can bring different perspectives into the same room, surface assumptions, build shared context and help people make progress.

But there is an uncomfortable possibility too: a workshop can also create collaboration debt.

A group can leave feeling aligned without necessarily being aligned. One person may believe a decision was made, while someone else thinks it was only discussed. The room may have been full of energy and useful thinking, but a week later nobody is quite sure what happened next.

“Next steps” might not be enough

This is where the familiar workshop question of “what are the next steps?” starts to matter.

Most workshops already try to close this way, and rightly so. The challenge is that the answers can still be surprisingly vague. “Sarah will speak to James.” “We’ll socialise this with leadership.” “We’ll come back together in a few weeks.”

These sound like actions, but they don’t always give the work enough momentum to survive beyond the session. What is Sarah speaking to James about? Is James being asked to decide something, approve something, or simply be informed? What does “socialise” actually mean? Who is responsible for moving things forward?

So perhaps the opportunity isn’t to replace next steps. It is to go one level deeper.

Go one level deeper

Instead of asking only what happens next, we can be more explicit. What did we actually decide? What remains unresolved? What is the next meaningful movement of the work? Who now has the baton? What context or shared understanding needs to survive once people return to their day jobs?

These questions are still, in a sense, next steps. They simply force greater precision. They separate decisions from open questions, ownership from activity, and action from intention.

Importantly, this doesn’t mean the facilitator becomes the project manager. It doesn’t mean chasing actions, running stand-ups or staying attached to the work. Responsibility for delivery should still sit with the sponsor and the team who own it.

The facilitator’s role is different.

It is to make the handover stronger.

From closing to landing

That has made me wonder whether “close” is the wrong way to think about the final stage of a workshop.

Closing tells us the session is finished.

Landing asks whether the work is ready to continue once the session is finished.

The question shifts from “Have we finished the workshop?” to “Have we designed the work to survive without us?”

Because the real value of a workshop isn’t the energy in the room, the number of Post-it notes on the wall or even the clarity people feel at 4:30pm. The value is what people are able to do differently afterwards.

So perhaps the final responsibility of a facilitator isn’t simply to bring the workshop to a good close.

Perhaps it is to design the landing.

Try it in the room

Keep asking for next steps, but make the closing conversation more deliberate. Before the room breaks, work through five lenses: Decisions, Unresolved, Next, Baton and Context. The aim isn’t to create a detailed delivery plan. It is to make the handover explicit enough that the people who own the work can pick it up without having to reconstruct the workshop a week later.

Watch for

Landing should not become a heavy project-management ritual. The point is not to capture every action or keep the facilitator involved indefinitely. It is to remove the most important ambiguity while the people, context and decisions are still in the room.

Don’t just close the workshop. Design the landing.

About the author

Daniel Logan-Gill is a facilitator and workshop designer with more than 15 years' experience across transformation, customer experience and human-centred design. His musings share practical observations, experiments and lessons from helping groups think better together.

More about Daniel →