How to run an unconference: structured chaos that actually works

The best unconference session most participants ever attend is one where six people, none of whom had met before breakfast, spend 45 minutes workshopping a specific problem one of them brought in — and walk out with three concrete ideas they plan to try on Monday. The worst unconference session is 22 people staring at a whiteboard while two loud voices debate definitions. Both happen in the same format. The difference is facilitation, room setup, and knowing when not to use the format at all.

Unconferences — attendee-driven, agenda-built-on-the-day events — produce extraordinary engagement when run well and complete chaos when run badly. This guide covers when the format fits, how to facilitate the morning agenda build, how to set up rooms, and the recurring mistakes that sink first-time organizers.

1. When the unconference format fits

The format works when three conditions hold: the audience has shared specific expertise, peer exchange is more valuable than expert presentations, and the group is small enough (50-250) to reach collective decisions in real time. FooCamp, BarCamp, the original THATCamp gatherings, and most internal engineering offsites share those traits.

The format fails when any of the following are true:

• The audience expects curation. Senior executive buyers pay for someone else to have filtered the signal from the noise. Giving them a blank agenda insults the time commitment.
• Sponsors need predictable agenda placement. You cannot sell a "Track B sponsorship" when there is no Track B until 10am on day one.
• The group is new to each other with no shared context. Without a baseline, open calls produce vague topics and sparse engagement.
• The group is very large. Above 300, the morning agenda build breaks down and people get lost.

A reliable decision rule: if you cannot explain to a first-time attendee why the format is right for the content in two sentences, use a traditional agenda.

2. The morning agenda build — where most unconferences succeed or fail

The first 60-75 minutes of the day determine everything else. Run them deliberately. The pattern that consistently works:

1. 30-minute orientation (09:00-09:30). What an unconference is, ground rules (law of two feet, whoever comes is the right people, whatever happens is the only thing that could have), the specific mechanics of today's schedule.
2. 15-minute open call for topics (09:30-09:45). Anyone can propose. Each proposer writes name + topic + session type (discussion, demo, workshop) on an index card, comes to the front, speaks for 30 seconds. A seasoned facilitator cuts rambling proposals short.
3. 15-minute scheduling (09:45-10:00). Facilitator and one or two volunteers organize cards onto a physical grid (rooms on one axis, time slots on the other). Duplicate topics get merged. Popular topics get the larger rooms.
4. First session starts at 10:15. A 15-minute coffee buffer lets the grid get photographed and posted everywhere before people need to move.

Two details that matter more than they sound: use physical cards, not a digital board (physicality builds commitment), and have the facilitator narrate the scheduling decisions out loud so the room understands the logic.

3. Room setup — fixed seating kills the format

Unconferences demand room configurations most corporate venues do not provide by default. Specify these in the venue contract:

• Movable furniture in every room. Attendees will rearrange. If they cannot, the session defaults to lecture mode and you have lost the format.
• Multiple small rooms rather than one large one. A 6-person conversation in a 40-person room feels empty; the same conversation at a round table in a right-sized room feels intimate.
• Whiteboards or large flip charts in every room. Someone will want to sketch. Without surface space, ideas evaporate.
• A clear, visible grid in a central area. The schedule changes during the day; the grid is the source of truth.
• Easy room reassignment. If a "scaling outbound" session draws 40 people and the assigned room holds 10, you need a mechanism to swap rooms on the fly — typically a floating facilitator whose only job is flow management.

Hotel ballrooms with theater seating are the worst venue for this format. Converted loft spaces, university classrooms with movable chairs, and purpose-built collaboration venues are the best.

4. Capturing what happens

Unconferences generate a lot of value in small rooms — and most of it evaporates if not captured. A lightweight system works:

• One Google Doc per session, linked from the grid.
• Each session picks a notetaker in the first two minutes (the "whoever comes" principle applies — anyone can volunteer).
• End-of-day 20-minute readback where each session reports its top three takeaways.
• Shared doc distributed to all attendees within 48 hours.

The readback is often the most valuable session of the day, because it gives people who missed a session a reason to follow up with participants.

5. Common mistakes that sink first-time unconferences

1. Running the format without an experienced facilitator. The morning agenda build is a specific skill; hire someone who has done it at least 3-5 times.
2. Mixing scheduled and unconference sessions in the same day. Attendees cannot hold both modes at once. Pick one per day.
3. No documentation. Without notes, the value walks out the door with the attendees.
4. Over-scheduling. Leave 30% of the day unscheduled for hallway conversation, which is often where the real connections happen.
5. Sponsor placement inside the grid. Sponsors hate it, attendees hate it. Give sponsors a dedicated physical space that is not part of the session grid.
6. Ignoring the room-size feedback loop. If a session fills at 09:50, move it to a bigger room before it starts, not during.

The day-of checklist

Print this and hand it to the facilitator the morning of:

• [ ] Index cards, Sharpies, and tape ready by 08:30
• [ ] Large physical schedule grid posted in central area
• [ ] Every room labeled with a visible sign
• [ ] Every room has whiteboard or flip chart plus markers
• [ ] Notetaker shared-doc links prepped
• [ ] End-of-day readback slot on the schedule (20 minutes)
• [ ] Floating facilitator identified for room-swap flow
• [ ] Ground rules read aloud at 09:00, printed on every table
• [ ] Coffee and snacks accessible continuously, not at fixed breaks
• [ ] Camera to photograph the grid every 90 minutes

FAQ

Can a paying-customer event include unconference sessions? Yes — as one dedicated track or one full day, not scattered through a traditional agenda. Dreamforce and Web Summit have both experimented with unconference-style side programs, but the main conference stays curated.

Who should facilitate? Someone with prior unconference facilitation experience. If your team does not have one, hire one — the facilitation trade has experienced professionals who charge a day rate. It is the single most impactful cost line for this format.

How do sponsors fit in? Offer a dedicated sponsor lounge, branded swag in the welcome kit, or a sponsored meal. Do not put sponsors inside the grid. Sponsors who want more visibility belong at a different kind of event.

Should there be a keynote? An optional short opening keynote (15-20 minutes) to set thematic context can work. Anything longer crowds out the agenda build and signals to the room that "experts talk, you listen" — the opposite of the format's premise.

What tech stack do I need? Minimal. A shared folder for session notes, the event's networking app for events for post-session follow-up, and printed materials. Heavy software tooling usually gets in the way of the physical, social nature of the format.

Related guides

• Networking session formats
• Session track design
• Moderator training guide

Ready to run a hybrid agenda with scheduled sessions and unconference tracks on the same platform? Create your event on WebMobi →