The program that stalls at session four
Most community programs open well. Session one is full — everyone came to see what this is. By session four the same faces say the same things, the founder is quietly carrying the room, and new arrivals can't find a way in. It looks like a scheduling problem. It's a design one: the thing was booked as a run of gatherings, never built as a system that turns strangers into members and members into hosts.
So we start at the arc, not the invite list. If you can't tell us where a member should stand at month six versus month one, there isn't a program yet — there's a calendar. That's our honesty test: if we can't name the twelve-month arc with you, we won't take the brief. Naming it is what lets every session afterwards earn the next.
What we build into a program
Members-first programming, designed to compound. Four components carry most of the work, and we scope them together rather than one session at a time.
- Concept + creative direction. The through-line that makes a room recognisably yours — why it exists, who it's for, and the tone a host can hold three years in without a script.
- Salon + dinner formats. The actual containers — table sizes, seating logic, the shape of a conversation — designed so the right people meet in the right order, not left to whoever sits down first.
- Members integration + retention frameworks. The engineered path from first-timer to regular to host, plus the belonging signal that tells a member they've crossed over instead of leaving them to guess.
- Curation systems. The repeatable way you decide who's in the room next time — so the program keeps its character as it grows, and growth doesn't dilute the thing people joined for.
How the program runs
Underneath the formats, four design moves decide whether a program compounds or plateaus. We build all four in before session one, not after the drop-off starts.
- Design the arc, not the session. A multi-month trajectory — strangers, members, participants, hosts — that each gathering serves. Session eight then reads as an inflection point in a plan, not another pleasant evening.
- Engineer the belonging signal. The specific, felt moment a member shifts from attending to belonging — a role, an artefact, an in-house name — designed on purpose rather than left to emerge, if it emerges at all.
- Install the ritual only insiders know. The in-group cue members notice about themselves and can pull an outsider into. It turns a series of events into a place with a culture, and culture is what recruits the next cohort without you having to ask.
- Pass the founder-independence test. A pre-agreed session where you step out of the room and members carry the format. Survive it and you've built a community; fail it and you've built a session series that ends the week you get busy.
When to bring us in
Before session one, ideally — the arc, the belonging signal and the ritual are cheap to design early and expensive to retrofit once a cohort has settled into habits. We also take on programs that have already plateaued; there the first job is diagnostic, working out which of the four moves was never designed and whether the existing members can carry a reset. Either way, the sooner the arc is named, the more of it we can still engineer.
The test at brief stage is simple. Can you name the twelve-month arc, the belonging signal, one ritual an outsider couldn't fake, and what happens the day you step back? Answer those honestly and you'll know whether you're building something that compounds or a calendar of good nights out. Both are legitimate — but they're different products, and only one survives you.
Reading on how we think about this
- How Community Programs Compound (And Why Most Don't) — the long-form argument behind this practice — the four design moves in full, and why programs stall at session four
- Impact Measurement for Events — the sibling practice — how we prove a program actually compounded rather than just felt warm
- Anatomy of a Memorable Moment — why rituals and moments members can retell travel further, and recruit the next cohort for you
- 6 Questions Every Event Brief Must Answer — the brief-stage filter we run before we'll commit to designing an arc
Common questions
What makes a community program compound instead of plateau?
A designed arc, an engineered belonging signal, a ritual only insiders know, and a founder-independence test — all built in before the first session. Programs that stall have none of these; they run as a series of good gatherings that lean on the founder's energy until it runs out. Programs that compound are built so members carry the design forward.
Can you fix a community program that has already plateaued?
Yes. We start with a diagnostic — which of the four design moves (arc, belonging signal, ritual, founder-independence) was never built — then decide whether the existing members can carry a reset. Sometimes the fix is a new arc; sometimes it's handing a format to members so the founder stops carrying the room. The earlier a program has stalled, the more of it we can still rework.
What formats do you design for community and membership?
Mostly salon and dinner formats — small rooms where seating, table size and the order of conversation are designed so the right members meet, rather than left to chance. Around them we build the membership path, retention framework and curation system that decide who's in the room next time and keep the program on-tone as it grows.