Facilitation is design work

I used to think of facilitation as a soft skill. Something you're either good at or not, like telling jokes at parties.

I was wrong. Facilitation is design. The material just happens to be people, time and attention.

A workshop is a product with a two-hour lifespan and extremely demanding users. So I design it like one.

Your users are the participants

Every design process starts with the user. Workshops are no different. Before I plan anything, I ask:

• Who's in the room, and what do they need to walk out with?
• What do they already know? What do they think they know?
• Who has power, and who doesn't?
• What's the mood? Excited, skeptical, or tired of workshops?

That last one matters more than you'd think. A group that has sat through three "alignment sessions" this month needs a very different design from a group meeting for the first time.

Start with the outcome

Start with what should exist when the session is over. Not "we discuss X". Something concrete:

• A shortlist of three priorities
• A problem statement everyone can live with
• A decision, with an owner

If you can't name the outcome, you don't need a workshop. You need a meeting, an email or a nap.

The agenda is a flow

An agenda isn't a list of topics. It's a user flow. Each step should hand the group something the next step needs.

A pattern I lean on all the time comes from Sam Kaner's Facilitator's Guide to Participatory Decision-Making. First the group diverges: it opens up and generates options. Then it hits the "groan zone", where things get messy, people disagree and it feels like nothing is working. Then it converges: narrowing down and deciding.

The groan zone isn't a bug. It's where understanding happens. My job is to make it safe to stay there long enough.

Separate divergence from decisions

The most common workshop failure I see: generating and judging in the same breath. Someone suggests an idea, someone else shoots it down, and suddenly you're debating before you even have options.

Be explicit about which mode you're in. Say it out loud: "For the next twenty minutes, we're only collecting. No evaluating." Then, later: "Okay. Now we choose."

Write before you talk

This one comes straight from my psychology degree.

Groups are not neutral machines for combining opinions. A few well-known traps:

• Anchoring. The first number or idea on the table pulls everything else toward it. Tversky and Kahneman described this back in the 1970s.
• Groupthink. Close-knit groups can quietly suppress doubts to keep the peace. Irving Janis made the term famous in the 1970s by studying policy disasters.
• HiPPO. The Highest Paid Person's Opinion. Once the boss has spoken, the discussion is mostly over.

On top of that, research on brainstorming has shown for decades that people who think alone first come up with more ideas than the same number of people brainstorming out loud. Part of the reason is painfully simple: in a group, only one person can talk at a time.

The cheapest fix I know: let everyone write silently for a few minutes before anyone speaks. Then share. Everyone's thinking is on the table before any anchors drop.

Prototype your workshop

You'd never ship a product without testing it. So why run a workshop you've never tried?

• Dry run the exercises with a colleague. Confusing instructions reveal themselves fast.
• Time everything. It all takes longer than you think. I plan for one and a half times my first guess.
• Put instructions on a slide. Spoken instructions evaporate the moment people start working.
• Have a plan B for the exercise most likely to flop.

Design the energy curve

Energy in a room goes up and down over the day, and you can design for that.

• Get everyone talking early with something easy. The first thing someone says in a workshop is the hardest.
• Put the heavy thinking where energy is high, usually in the morning or right after a break.
• Switch formats: alone, pairs, small groups, everyone. Movement is energy.
• Don't schedule important decisions right after lunch. Just don't.

Scaling up

Earlier this year I facilitated a gathering for around 70 people at Nav. Big groups change the design problem. You can't have everyone talk to everyone, so structure has to do more of the work:

• Small tables with clear tasks and a simple way to report back
• Fewer, sharper questions
• Clear roles at each table, like who writes and who keeps time
• Way more time for transitions than feels reasonable

The principles are the same as for eight people. The margins are just smaller. And honestly, logistics are half the design. Markers that work and sticky notes that actually stick are not a detail.

Follow-up is part of the product

The workshop isn't over when people leave the room. If nothing happens afterwards, you've taught everyone that workshops don't matter, and your next one starts with a handicap.

• Send a summary within a day or two, while memory is fresh.
• Make decisions and owners visible.
• Close the loop. Tell people what happened to their input, even when the answer is "not now".

The short version

• Participants are your users.
• Start with the outcome.
• Design a flow, not a topic list.
• Keep divergence and decisions apart.
• Write before you talk.
• Test it before you run it.
• Follow up, or it didn't happen.

Designers already know how to do all of this. We just don't always notice that a room full of people is a design material too.