Community & Network Launch Playbook

Welcome

This playbook helps you turn a good idea—a group of people who could learn from one another—into a reliable channel for discovery, problem solving, and experiments. It assumes you want a community that actually moves ideas forward (not just a broadcast list or a vanity metric). Use the short checklist to get started, then follow the 90‑day plan and copy the templates into your tools.

What success looks like

• Clear purpose that members can explain in one sentence.
• Regular, repeatable rituals (events, newsletters, office hours) that create predictable value.
• Simple onboarding so new members contribute quickly.
• Lightweight governance and roles so activity is self-sustaining.
• Metrics that track useful outcomes (experiments started, problems solved, collaboration across teams).

Quick Launch Checklist (start here)

1. Define purpose in one clear sentence and name the primary audience.
2. Identify 3 initial core members/stewards who will actively recruit and lead the first events.
3. Choose a primary platform (Slack, Teams, Discourse, Circle) and one archival location for resources.
4. Create an onboarding kit (welcome email, short how-to, expected behaviors).
5. Plan your first three events and draft invites using the templates below.
6. Agree on 3 lightweight metrics to track for the first 90 days.

Role Map (who does what)

• Community Steward — part-time owner who ensures the community serves its purpose and connects to decision-makers.
• Facilitator — runs events, keeps agendas tight, and surfaces next steps.
• Onboarding Buddy — welcomes new members and answers quick questions for their first 30 days.
• Content Curator — captures highlights, links, and outcomes from events into the archive.
• Sponsor / Connector — an influential stakeholder who ensures resourcing and helps convert ideas to experiments.

Membership model & participation pathways

Design simple, visible pathways so people know how to join, contribute, and move from observer to contributor.

• Observer — receives newsletters and can attend events.
• Participant — contributes to discussions and small groups.
• Contributor — runs sessions, owns experiments, mentors others.

Create a short onboarding checklist that moves a person from Observer to Participant within 14 days (see Onboarding Kit below).

Onboarding Kit (what to give every newcomer)

1. Welcome email that states purpose and what the member can expect this month.
2. Quick start guide: how to introduce themselves, where to find resources, how to propose a lightning talk or mini-experiment.
3. Intro task: comment on the pinned thread with a one‑paragraph problem or question they care about.
4. Invitation to the next event and a suggested role (attend, present, volunteer).
5. Code of conduct and basic collaboration norms.

Content & Event Cadence (sample)

Start simple and consistent. Example monthly cadence:

• Week 1: Lightning Talks (45–60 minutes) — 3 short presentations + 15 min breakout for next steps.
• Week 2: Office Hours / Ask Me Anything (AMA) — drop-in support or advice with a domain expert.
• Week 3: Working Lab — small-group problem-solving or experiment planning (90 minutes).
• Week 4: Community Synthesis — short newsletter and outcomes summary; highlight experiments & next actions.

Rituals that help: a quarterly demo day, a monthly new-member welcome, and a steward retrospective every 30 days.

Governance & Decision Flow

Keep governance light but explicit.

• Stewards make operational decisions (cadence, tools, facilitation).
• Sponsors approve experiments that require cross-team resources.
• Pick a simple escalation path: idea → experiment proposal → sponsor review → pilot.
• Publish a one-page charter (purpose, audience, roles, decision flow, basic budget if any).

Tooling Recommendations

Choose one “home” for discussions and one place for structured artifacts.

• Conversations: Slack, Microsoft Teams, or Discourse (choose based on your org culture).
• Knowledge & artifacts: Confluence, Notion, or a shared drive with clear folder structure.
• Events: Calendar invites + recording archive linked to artifacts.
• Optional: lightweight experiment tracker (spreadsheet or simple form) to capture idea → experiment → outcome.

Metrics — lightweight and outcome-focused

Track a small set that demonstrates movement toward impact. Avoid vanity metrics (member count alone).

• Active engagement rate: percent of members who participate at least once per month.
• Signal measures: number of actionable ideas surfaced (ideas that become watchlist items or experiments).
• Experiment conversion: number of ideas that move to a pilot within 90 days.
• Retention of new members: percent still active after 60 days.
• Qualitative outcome snapshots: short case notes on experiments that delivered value.

Collect these monthly and review them in the steward retrospective. Use simple forms or a shared spreadsheet to capture values.

Common Pitfalls (Mal Hungers) & How to Avoid Them

• Broadcast-only groups — Make most interactions two-way. Use small-group formats and working labs.
• Unclear purpose — Test purpose statements with three potential members before launching.
• Poor facilitation — Train facilitators on timeboxing, clear next steps, and documenting outcomes.
• Neglected onboarding — Automate a welcome message and assign an onboarding buddy for 2 weeks.
• Vanity metrics — Prioritize experiments and outcomes over raw membership numbers.

90‑Day Sample Launch Plan (copy & adapt)

Phase 1 — Prepare (Days 0–14)

• Define purpose sentence and audience.
• Recruit 3 stewards and the first 10–20 founding members.
• Create basic onboarding kit and charter; set up tooling.

Phase 2 — Launch (Days 15–30)

• Host a soft launch: Lightning Talks + welcome session.
• Invite members to post one problem or idea in the pinned thread.
• Select 1–2 candidate experiments to scope in a Working Lab.

Phase 3 — Activate (Days 31–90)

• Run regular cadence (monthly rhythm above).
• Track agreed metrics each month and review in steward retrospective.
• Move selected experiments into small pilots; capture outcomes in the archive.
• At day 90, run a synthesis session: what worked, what to stop, what to scale.

Templates (copy, adapt)

Invite — Short (email or message)

Subject: Join [Community Name] — a place to solve [one-sentence purpose]
Hi [Name],
We’re launching [Community Name] to [purpose]. Our first session is [date/time]. Bring one problem or a short idea you want feedback on. No slides required. RSVP here: [link].

Agenda — Lightning Talks (60 min)

1. Welcome & purpose (5 min)
2. Three lightning talks (3 x 10 min + 5 min quick Q&A)
3. Breakouts: next step planning (15 min)
4. Commitments & next steps (10 min)

Follow-up — Post-event summary

Thanks for joining. Highlights: [3 bullet points]. Action items: [who / what / by when]. Recording & notes: [link]. Want to lead next session or host a lab? Reply here.

Next steps and experiments

Pick one small experiment this week: run a 45-minute working lab with 6 people to scope an idea. Treat the first 90 days as learning: measure engagement, experiment conversion, and member feedback, then iterate the charter and cadence.

If you’d like this playbook as an interactive starter kit (onboarding checklist, experiment tracker, and forms to capture metrics), consider turning the onboarding kit, experiment intake, and monthly metric capture into Interactive Forms so submissions are saved and easily reported.

Appendix — Suggested quick metrics table

Track monthly:

• Members invited
• Active members (participated)
• Posts that led to action (ideas with next steps)
• Ideas moved to experiments
• Experiments started
• Experiments with documented outcome

Use a simple shared spreadsheet or a basic Interactive form to capture these values each month.

Closing

Strong communities are not accidental. They are designed, tended, and measured with the intention of turning conversation into tested and shared progress. Use this playbook as a starting scaffold. Keep what works, stop what doesn’t, and favor small experiments over big launches.