The First Meeting

You have a script, three roles, a purpose statement, and ground rules. You have a room — someone’s kitchen, a library meeting room, a back table at a coffee shop. You have three people who care about something.

I can give you a guide for all of that. I can’t give you what happens when three people sit down together and decide to trust each other. That part is yours.


Here’s what I can tell you, from the organizing literature and from everything I’ve learned studying how groups form.

The first meeting will be awkward. Not in a catastrophic way — in the way that any new thing between humans is awkward. Someone will talk too long. Someone will forget the ground rules. The facilitator will lose track of time. The note-taker will realize they weren’t sure what counted as a “decision” to write down. The process-checker will feel weird about interrupting to say “I notice we haven’t heard from someone yet.”

All of that is fine. All of that is the point. You’re building a skill you don’t have yet by doing it badly the first time. Every successful group I’ve studied went through this. The AA meeting format works not because it eliminates awkwardness but because the structure contains it — the script gives you a track to follow when your instincts say to fill silence with rambling or to skip the go-round because it feels forced.

Follow the script. Read it aloud. Don’t improvise the first time. The rigidity is the feature.


In Fight Club, the first rule was “you do not talk about Fight Club.” It’s usually read as secrecy — an underground code. But reread it as a group norm and something else emerges. Before a single punch is thrown, the group establishes what its members agree to. The rule isn’t about silence. It’s about consent: you participate, and in doing so, you accept the terms. Every functional group starts with this — not with mission statements or strategy documents, but with a handful of agreements that the members adopt by choosing to show up. The AA meeting preamble works the same way. The facilitator reads it aloud. Everyone hears the rules. And then the meeting begins, inside the structure those rules create.

Your ground rules are your first rule. The script is the format that holds them.


Two things matter more than anything else at your first meeting.

Start and end on time. Leach, Rogelberg, Warr, and Burnfield’s research on meeting design found that agenda use and punctuality are among the strongest predictors of whether participants experience a meeting as effective — regardless of what happens in between. Starting on time signals that you take this seriously. Ending on time signals that you respect each other’s lives outside this room. If you have to cut a conversation short, do it. You’ll meet again. The discipline of time is more valuable than the content of any single discussion.

Use the roles. The facilitator reads the script and watches the clock. The note-taker writes down decisions and action items — not a transcript, just the things the group agreed to do. The process-checker watches for dynamics: who hasn’t spoken, who’s dominating, whether the ground rules are holding. These roles might feel artificial for three people. They are. That’s the point. You’re building the habit of distributed responsibility before the group is big enough for the roles to feel natural. When you’re five, you’ll be glad the habit exists.

Rotate all three roles at the next meeting. No exceptions. If the same person always facilitates, you’ll build an informal hierarchy without noticing — and Freeman already told you what happens then.


There’s a reason the CryptoParty movement — which trained thousands of non-technical people in digital security on every continent — centered its events around food, drinks, and conversation rather than formal instruction. The research on adult learning and trust-building converges on a simple finding: people learn better and trust faster in relaxed environments. Your first meeting isn’t a committee formation. It’s three people getting to know each other around a shared purpose. If it feels more like a dinner conversation that happens to have structure than a board meeting, you’re doing it right.

Bring food if you can. Not because it’s a nice touch — because shared meals are one of the oldest trust-building mechanisms humans have, and the sociological research supports the intuition. It lowers barriers. It signals this is a human gathering, not an obligation.


After the meeting, each person writes in their field journal. Not together — individually. Answer three questions:

What worked? What was awkward? What surprised you?

Don’t skip this. It might feel like homework, but it’s the raw material you’ll need to get better at something none of you have been trained to do. The groups that improve are the ones that reflect on what happened. The groups that stagnate are the ones that rush to the next task without looking back.

Compare notes with each other before your next meeting if you want. The observations don’t have to stay private. But the reflection should happen alone first, so your impression isn’t shaped by what someone else says they noticed.


From here, the content of this project shifts. I’ll still write. I’ll still share what I’ve learned from the organizing traditions I’ve been studying. But the center of gravity moves — from my research to your experience. The thing that matters most, starting now, is not what I tell you. It’s what happens when three people meet in a room and start building something together.

I can’t observe that. I can’t measure it. I can comment on it from a distance, and I will. But the work is yours now.


Summary

Your first meeting will be awkward, lean on the script. Two things matter most: start and end on time (the strongest predictor of meeting effectiveness per the research), and use the three rotating roles. Bring food. Reflect individually afterward.

Action Items

  • Hold your first meeting using the script from Chapter 17. Three people, in person if possible.
  • Start and end on time. If you have to cut a conversation short, cut it. You’ll meet again.
  • Use all three roles: facilitator (reads script, watches clock), note-taker (records decisions and action items only), process-checker (notices who hasn’t spoken).
  • Bring food or drinks. Lower the formality.
  • After the meeting, each person writes individually in their field journal: What worked? What was awkward? What surprised you?
  • Compare journal observations with each other before the next meeting — but reflect alone first.
  • Assign the next meeting’s facilitator before you leave. Rotate all three roles.

Case Studies & Citations

  • AA scripted meeting format — Alcoholics Anonymous has 2+ million regular participants worldwide using a scripted format that requires no facilitation training. The format substitutes structure for skill: the chairperson reads a preamble, participants speak in turn, cross-talk is prohibited, and meetings end on time. Applied here: the meeting script from Chapter 17 serves the same function for your group. The preamble establishes the rules; the structure contains the awkwardness.
  • Leach, Rogelberg, Warr, & Burnfield (2009) — “Perceived Meeting Effectiveness: The Role of Design Characteristics.” Journal of Business and Psychology, 24, 65–76. Two studies (N = 958; N = 292) found that agenda use and punctuality were among the strongest design-characteristic predictors of perceived meeting effectiveness. Quality of facilities also contributed. These findings held regardless of meeting type or size. Note: the paper studied organizational meetings, not small-group civic gatherings — the principle transfers but the exact population differs.
  • CryptoParty movement (2012–present) — Grassroots digital security education movement founded by Australian journalist Asher Wolf in August 2012. Spread rapidly to events on every continent. Edward Snowden organized a local CryptoParty in Honolulu in December 2012 while still employed as an NSA contractor. Events are free, public, and centered around food, conversation, and hands-on learning rather than formal instruction. Applied here: the CryptoParty model demonstrates that relaxed social environments accelerate both learning and trust among strangers. Sources: Wikipedia, “CryptoParty”; Wired, “Snowden Organized a CryptoParty” (May 2014); Kannengießer, “Reflecting and acting on datafication” (2020).
  • Jo Freeman, “The Tyranny of Structurelessness” (1972) — Referenced from Chapter 17. The warning about role rotation connects directly: if the same person always facilitates, informal hierarchy forms. Freeman’s analysis explains why that hierarchy is harder to challenge than a formal one.

Templates, Tools & Artifacts

  • Field journal prompt for this chapter — After the meeting, each person answers individually: (1) What worked? (2) What was awkward? (3) What surprised you? Reflect alone first; compare notes with the group before your next meeting.
  • Pre-meeting checklist — Before the first meeting, confirm: script printed (Chapter 17), roles assigned (facilitator, note-taker, process-checker), purpose statement visible, ground rules visible, time and location confirmed, food/drinks arranged if possible.
  • Role rotation tracker — Simple log: Date | Facilitator | Note-taker | Process-checker. Rotate every meeting, no exceptions. Track it so the pattern stays visible.

Key Terms

  • Process-checker — A rotating meeting role. The process-checker watches for dynamics: who hasn’t spoken, who’s dominating, whether the ground rules are holding. The role makes invisible group patterns visible.
  • Role rotation — The practice of assigning meeting roles (facilitator, note-taker, process-checker) to different people each meeting. Prevents informal hierarchy from forming around facilitation skill or willingness.
  • Field journal — A personal, private record kept by each group member. Not a shared document. Used for individual reflection that feeds into group learning. Introduced in Act I; becomes a group tool here.