Module 2: Community Foundations
Platforms change and features come and go, but communities live or die on three things that never change: a purpose members can state, a journey that turns newcomers into regulars, and rules that protect the culture without strangling it. This module covers all three — the foundations every setup in the next module is built on.
Why communities die
Almost every dead community died of one of three causes, and none of them is "the algorithm." First: no clear purpose. Members joined for a reason that was never said out loud — or was said once in a sales page and never repeated — so nobody knows what the room is for, what to post, or what a good week looks like. Rooms like that fill with awkward silence and the occasional self-promotion, because unclear rooms default to whatever the least shy member wants.
Second: no rhythm. Healthy communities run on a predictable pulse — a Monday prompt, a midweek wins thread, a monthly live session. Rhythm is what turns "I should check the group sometime" into a habit. When the rhythm depends on the host's mood or spare time, it breaks the first busy week, and every gap teaches members the room will be empty when they visit. People don't leave quiet communities in anger. They just stop coming, then cancel at renewal.
Third: an absent host. The owner doesn't have to post daily, but they have to be visibly, reliably present — and when the owner vanishes, the manager's job includes saying so early and plainly, with a plan. Your diagnostic habit from Module 0 applies here: when you audit a struggling community, check purpose, rhythm, and host presence before you touch a single setting. Nine times out of ten, the leak is one of those three, and no platform feature fixes any of them.
A membership owner says: "Posts dropped off over the summer. Should we switch platforms? The new one has better features." Activity fell right after she stopped her weekly live calls during a busy launch. What's your first move?
The member journey: arrive, first win, habit, belonging
Every member travels the same four stages, and your systems exist to move people along them. Arrive: the first minutes after joining, when they're deciding if this was a good purchase. First win: the first time the community gives them something concrete — an answered question, a useful template, a small public success. Habit: the point where checking in becomes part of their week without being reminded. Belonging: when they know names, get referenced by other members, and start helping newcomers the way they were helped.
Each stage fails in its own way. Arrivals fail when a new member lands in a wall of old posts with no welcome and no obvious first step. First wins fail when a member's first post — usually a question or an intro — sits unanswered for two days; they've learned the room doesn't respond, and many never post again. Habits fail when there's no rhythm to attach to. Belonging fails when everything runs through the host and members never actually meet each other.
Manage the journey as a pipeline, the way a salesperson manages theirs. At any given week you should be able to say roughly how many members are brand new, how many have had a first win, and who among the regulars has gone quiet. You won't have perfect data on every platform, and you don't need it — a simple weekly pass through the newest members and the recent-activity list catches most of what matters. Modules 4 and 5 build the specific mechanics for each stage; this map is how you know which mechanic a struggling community actually needs.
You audit a paid community and find this: a warm welcome post exists, weekly prompts run on schedule, but you spot six intro posts from new members in the last month that never got a single reply. Which stage of the journey is broken?
Rules that protect culture without smothering it
Good community rules are short enough to read in a minute and specific enough to enforce without an argument. Most communities need five to eight, and they fall into natural groups: what belongs here (topics, self-promotion limits), how we treat each other (no harassment, critique work not people, no medical or financial advice stated as fact where that's a risk), and how the room runs (no spam, no DMing other members to pitch them, what happens when a rule breaks).
Write each rule with its reason attached, in plain words: "No pitching other members by DM — people paid to learn here, not to be sold to" gets followed. "Management reserves the right to remove any content for any reason" gets resented and tested. Publish the rules where members actually join — pinned, linked in the welcome flow, and referenced in the moment you enforce them, so enforcement reads as keeping a promise instead of inventing one.
Two habits make rules work. Enforce them evenly: the day a popular member breaks the no-pitch rule and nothing happens, the rule is dead and every quieter member noticed. And enforce them proportionately — most first offenses are ignorance, not malice, and a friendly private note fixes them (Module 6 builds the full ladder). Your goal is a room where good members barely feel the rules and problem members feel them immediately. If your regulars are quoting the rules at each other in normal conversation, you've written too many.
A well-liked, long-time member starts dropping links to his own paid workshop in the wins thread every week. The guidelines say no self-promotion outside the monthly promo thread. Several members have noticed. What do you do?
What you can now do
- Diagnose why a community died in one pass: the purpose was never stated, the member journey never built, or the rules strangled the culture instead of protecting it.
- Design a member journey that moves people through all four stages — arrive, first win, habit, belonging — instead of hoping they wander there.
- Write five to eight community rules a new member can read in a minute and a moderator can enforce without starting an argument.