Lesson 69.1 gave you a purpose: a recurring member job with peer help that compounds. Now that purpose needs a place to live. Founders usually pick the tool they like — "everyone is on Discord" — and then wonder why a slow, thoughtful practice dies in a fast chat stream. The home should follow the interaction, not fashion.

Speed versus memory: the core tradeoff

Every community home sits somewhere between fast and forgetful, and slow and searchable:

| Home | Speed | Memory | Best for | Hidden cost |

|---|---|---|---|---|

| Chat (Discord, Slack) | Instant, lively | Poor — scroll buries gold | Daily co-working, quick help, cohorts | Needs constant presence; empty rooms feel dead |

| Forum (Discourse, Circle) | Slower, threaded | Excellent — search compounds | Q&A archives, critiques, how-tos | Feels quiet at first; needs seeding |

| Newsletter + replies | Slow, curated | Good — issues are artifacts | Small expert groups, curated practice | One-to-many by default; replies need routing |

| Social group (X, Facebook, LinkedIn) | Fast discovery | Poor — algorithm owns reach | Top-of-funnel gathering, events | You rent attention; rules change |

| Website hub + comments | Slow | Good if organized | Public archive that attracts search | Needs moderation and structure work |

| Membership platform | Varies | Varies | Paid accountability, courses + community | Paywall shrinks seeding pool early |

The rule: fast interaction needs fast homes; compounding knowledge needs searchable homes. Most healthy communities eventually use two — a fast room for presence and a slow archive for memory — but they start with one. Starting with both splits ten active people across two empty rooms.

A tailor's referral circle lives fine in a small chat group: speed matters, history does not. A research-builders community that turns filings into citable briefs needs a forum first: a Discord scroll cannot preserve "how we handled footnote 14 of a 10-K" for next month's newcomer.

Stage the home: crawl, walk, run

Do not buy infrastructure for a community you have not proven. Stage it:

Stage 1 — Prove interaction (weeks 1–4). Use whatever is free and familiar: an email thread, a single chat channel, a newsletter with reply-to-everyone. The question is only "will five people talk weekly?" No bots, no tiers, no custom domain.

Stage 2 — Add memory (months 2–3). Once weekly threads recur, move durable answers somewhere searchable — a simple forum category, a shared doc index, a website page per answered question. Keep the fast room; add the archive.

Stage 3 — Fit the scale (month 4+). Now choose deliberately: forum-first, chat-first, or paid membership. Move only when the current home demonstrably breaks — search fails, noise drowns signal, free riders dominate. Each move should fix a named pain, not chase a feature list.

This staging saves the most common waste: a founder configuring roles, bots, and twelve channels for a community with four members. Empty architecture signals "nobody is here." One lively channel signals "come in."

How to choose in ten minutes

Match your purpose statement's interaction sentence to a home:

• "Bring one live question, get unstuck today" → start in chat.
• "Show work, get critique, keep the improved version" → start in a forum.
• "Read one curated teardown weekly, discuss" → start with a newsletter plus one discussion thread.
• "Find nearby help fast" → start with a small social or messaging group.
• "Build a public library together" → start with a website hub.

Then answer three constraint questions: where do your members already hang out (do not make a Slack user install Discord for you)? How much hosting and moderation time can you actually sustain? And who owns the archive if the platform changes rules — do you export weekly?

The export question matters more than founders expect. Social groups and some chat platforms make leaving hard. Forums and email lists export cleanly. If compounding memory is your engine, own the archive from Stage 2 onward, even if conversation happens elsewhere.

Exercise: write the home decision

Create COMMUNITY-HOME.md with five fields:

• Purpose link: paste your five-sentence purpose from Lesson 69.1.
• Interaction type: fast help, slow critique, curated discussion, local coordination, or public library.
• Stage 1 home: one venue, one channel or thread, and why.
• Memory plan: where durable answers go, and how often you export or index them.
• Move trigger: the named pain that justifies Stage 2 ("same question asked three times with no linkable answer") and Stage 3.

Example — research builders: Stage 1 is a single weekly email thread ("one filing question each"). Memory is a shared page per answered question. Move trigger: more than ten questions per week, at which point a Discourse forum with filings, brief-reviews, and templates categories replaces email.

Finish line: a one-page decision record naming one starting home and one explicit move trigger.

Verify quickly: check that your home has at most two places to post. If a new member asks "where do I post my first question?" and the answer takes more than one sentence, simplify.

Common failure mode: launching five channels for five imagined use cases. One channel with real conversation beats five quiet ones every time.

Check your understanding

1. Why do fast chat homes and searchable forum homes serve different community jobs? 2. What belongs in each of the three staging phases? 3. What single question should a confused newcomer never have to ask about where to post?

Next

Home chosen, rooms still empty. Lesson 69.3 solves the cold start — seeding the first 30 days with prompts, rituals, and founding members so the room feels alive before strangers arrive.