Conference breakout

When to use it

A conference programme has a breakout slot on a topic the field cares about, and the usual format is a panel followed by questions from the four people willing to hold a microphone. This session turns the slot into something the association can publish: every delegate contributes, the room names its own themes, and the organizer walks out with a record rather than a memory.

For the facilitator or the platform, this is also the highest-leverage room available, because the delegates experience the method as participants rather than hearing it described.

Do not use it when the organizer wants a keynote with audience interaction. This needs the full arc and a room that stays put for it.

The question

Conference audiences are strangers to each other with a shared professional context. The question must be answerable from their own practice within two minutes of hearing it.

Seeds:

• What is the problem in our field that everyone works around and nobody names?
• What did you try this year that did not work, and what did it teach you?
• What do newcomers to this work get wrong, and whose fault is that?
• What would have to change for [the sector's stated goal] to be realistic rather than aspirational?

The question that fails: "What are the trends shaping our sector?" It produces the same eight answers every conference produces, because it asks for commentary rather than experience.

Session settings

• Participants: cap at 100. If the room is bigger, see the notes
• Anonymous participation: on
• Raffle: off
• Blind gather: on
• Blind then reveal voting: on
• Shuffle order: on
• Access after finish: on, so delegates can find the report later

Run of show

Timings for a 60-minute slot. Add the spare fifteen to Gather and Emerge if you have 90.

Ends at: Validate, with ratification. A breakout that renames at least one pattern leaves with a map the delegates own rather than a draft the software wrote, and there is no Resolve segment in a 60-minute slot.

Facilitator notes

Test the wifi from the back row the day before, not the morning of. Conference wifi is the single most common cause of failure in this guide. If it is unreliable, tell the room at the start that mobile data works fine, and have the join code on a slide rather than only a QR, because scanning fails in low light.

Above 100 delegates, do not push the cap. Either run parallel rooms with separate sessions and compile afterwards, or take contributions from 100 and tell the rest they are observing. Overrunning the cap in front of an entire conference is a bad way to be memorable.

Project everything. This guide is unusual in that the screen is the show. Delegates watching their own contribution become a theme, and then watching the room overrule the software, is the demonstration. Narrate what you are doing as you do it.

Deliver the output before the closing plenary. The organizer's incentive for booking this is having something to say at the end of the day. Get the report to them with enough time to read it.

What the group leaves with

Themes the delegates named, what resonated across the room, the open items nobody could group, and a report the organizer can publish. Delegates can request the report themselves without an account.

The failure mode

The room does not settle, because delegates arrive late, leave early, and treat it as a session they can dip into. A conference audience has no obligation to you, and a thin gather produces a weak emerge, which is a public failure in front of exactly the people you want as customers.

Prevent it by starting the gather within nine minutes, before the room has fully assembled, and telling latecomers they can still contribute. Watch the counter: if you have fewer than about 25 ideas at the eight-minute mark, extend by two minutes and prompt with a narrower version of the question rather than pushing on to clustering. A slightly long gather is recoverable; a thin one is not.