Community-Led Growth
RGM° · Training
Community Design and Rituals
Intentional design prevents drift. Purpose, norms, rituals, events, content, moderation.
Why design matters
Communities without intentional design devolve into spam, silence, or single-voice dominance. Mature communities have explicit norms, recurring rituals, and active programming.
Purpose
- What members get out (learning, networking, recognition).
- What brand gets out (advocacy, feedback, retention).
- Both must be clear; otherwise mismatched expectations.
- Purpose stated publicly.
- Onboarding reinforces purpose.
Norms
- Code of conduct.
- What's welcomed and what's not.
- Self-promotion rules.
- Off-topic guidelines.
- Disagreement handling.
- Confidentiality if applicable.
- Sales / vendor rules.
Rituals
- Weekly thread / topic.
- Monthly office hours.
- Quarterly virtual events.
- Annual conference.
- New member welcome ritual.
- Milestone recognition.
- End-of-year recognition.
Events
- Virtual roundtables.
- Webinars with member panels.
- In-person meetups (where geography supports).
- Annual conference.
- Member-led workshops.
- Industry conferences with member presence.
Content programming
- Curated content shared regularly.
- Member-contributed content highlighted.
- Expert AMAs.
- Behind-the-scenes from brand.
- Industry news commentary.
- Member spotlight features.
Moderation
- Active moderation; not just reactive.
- Volunteer moderators from community.
- Clear escalation paths.
- Norm enforcement consistent.
- Conflict resolution playbook.
- Spam and bad-actor management.
Advanced playbook
- Annual community strategy with rituals calendar.
- Member-led ritual creation.
- Cross-pollination between groups.
- Volunteer moderator program.
- Annual conference / major event.
- Member journey mapped (newcomer to leader).
- Recognition layered (badges, status, real-world).
- Cross-team participation (product, CS, marketing).
- Community-driven product feedback structured.
- Annual rituals review.
Common mistakes
- No code of conduct.
- Rituals one-shot, not recurring.
- Events marketing rather than member-serving.
- Moderation reactive only.
- Volunteer moderators not developed.
- Member-led content discouraged.
- Cross-team participation absent.
- Community drifts from purpose.
- Annual review absent.
- Conflict resolution playbook missing.
Operating checklist
- Purpose documented and shared
- Code of conduct
- Weekly rituals
- Monthly events
- Annual major event
- Member-led content
- Active moderation
- Volunteer moderator program
- Cross-team participation
- Annual rituals review
Sources and further reading
- David Spinks community design
- CMX Hub research
- Holly Firestone community building
- Bevy community + events platform
- Discourse, Vanilla Forums
- Slack, Discord community management
- RGM Community-Led Growth fundamentals
- Sangram Vajre B2B community
- Mighty Networks research
- Reforge community curriculum
- HubSpot community case study
- Salesforce Trailblazer Community
Part of the Community-Led Growth series.