Back to events

Organizing an AT Protocol unconference

How to run a participant-driven AT Protocol unconference, where the attendees set the agenda.

An unconference is a participant-driven event. It drops the usual top-down conference format in favor of topics that attendees propose, pitch, and schedule on the day. People show up with what they want to talk about, and the program builds itself. More on unconferences.

Thank you for organizing one. Here are some tips and guidelines.

General organization

Facilities

Content and topics

Content is participant-driven, but you can seed a few topics and open with a short keynote or workshop to set the tone. Sessions get proposed and voted on by the people in the room.

The kickoff

The kickoff is the first part of the day and runs roughly like this:

  1. Intro. Explain the topic, the rules, and how participation works.
  2. Session proposals. Participants write topics on sticky notes.
  3. Pitches. Each proposal is explained, similar ones get merged, and co-leaders step up.
  4. Voting. People vote on topics, and sessions are scheduled by how much interest they draw.
  5. Scheduling. The host places sessions on the wall, then everyone takes a short break before the first one.

The wall

The wall is the living agenda: a grid where topics are posted and updated through the day. Sessions usually run 20 to 30 minutes with 10-minute breaks between them.

During the event

Facilitate the proposals, pitches, voting, and scheduling. Encourage the law of two feet: if you are not learning or contributing in a session, quietly move to another one.

Ground rules

An unconference only works when everyone takes part and looks out for each other. A few basics:

Participation takes a few shapes:

Self-running sessions

Sessions can run themselves when each one has:

After the event

What you can expect from us

Ready to start? Say hi to @atproto.nl or open an issue on the site repo.