Community Builder

Community Builder

Expert guidance for building, growing, and nurturing thriving online communities — from platform selection to engagement programs to community-led growth strategies.

Philosophy

Great communities are built on three pillars:

1. Shared purpose — Members need a reason bigger than the product 2. Genuine connection — People stay for people, not features 3. Member empowerment — The best communities run themselves

How This Skill Works

When invoked, apply the guidelines in rules/ organized by:

• strategy-* — Community-led growth, positioning, and strategic planning
• platform-* — Discord, Slack, Circle, and platform selection
• onboarding-* — Member welcome flows and activation
• engagement-* — Programs, rituals, and recurring activities
• content-* — User-generated content and content programs
• programs-* — Ambassador, champion, and super-user programs
• metrics-* — Community health and analytics
• moderation-* — Governance, moderation, and conflict resolution
• devrel-* — Developer relations and technical community building

Core Frameworks

The Community Flywheel

┌─────────────────────────────────────────────────────────────┐
│                                                             │
│   ┌──────────┐    ┌──────────┐    ┌──────────┐             │
│   │  ATTRACT │───▶│ ACTIVATE │───▶│  ENGAGE  │             │
│   │ (Reach)  │    │ (Value)  │    │ (Habit)  │             │
│   └──────────┘    └──────────┘    └──────────┘             │
│        ▲                                │                   │
│        │          ┌──────────┐          │                   │
│        │          │ ADVOCATE │          │                   │
│        └──────────│ (Amplify)│◀─────────┘                   │
│                   └──────────┘                              │
│                                                             │
└─────────────────────────────────────────────────────────────┘

Community Maturity Model

Member Journey Stages

The 1-9-90 Rule

In most communities:

• 1% create content (Creators)
• 9% engage with content (Contributors)
• 90% consume content (Lurkers)

Goal: Move people up the engagement ladder, not force everyone to create.

Community vs Audience

Platform Comparison at a Glance

Key Metrics Overview

Community-Led Growth (CLG) Quick Reference

Engagement Program Types

Anti-Patterns

• Build it and they will come — Communities require constant nurturing, especially early
• Metrics over meaning — Vanity metrics don't equal healthy community
• Over-engineering early — Start simple, add complexity as needed
• Ignoring lurkers — 90% of your community provides value by consuming
• Founder absence — Early communities need visible leadership
• Feature obsession — People join for people, not features
• Forced engagement — Authentic connection beats gamification
• One-size-fits-all — Different member types need different experiences
• Scaling too fast — Growth without engagement destroys community
• Neglecting moderation — One bad actor can poison the well

1. Community Strategy (strategy)

Impact: CRITICAL Description: Community-led growth strategy, community positioning, strategic planning, and growth models.

2. Platform Selection (platform)

Impact: CRITICAL Description: Discord, Slack, Circle, Discourse, and other platform comparison, selection criteria, and setup.

3. Member Onboarding (onboarding)

Impact: CRITICAL Description: Welcome flows, first-value moments, activation sequences, and new member experience.

4. Engagement Programs (engagement)

Impact: HIGH Description: Community rituals, recurring events, engagement programs, and participation drivers.

5. Content & UGC (content)

Impact: HIGH Description: User-generated content programs, content contribution systems, and member-created content strategies.

6. Ambassador Programs (programs)

Impact: HIGH Description: Ambassador programs, champion programs, super-user programs, tier structures, and rewards.

7. Community Metrics (metrics)

Impact: HIGH Description: Community health indicators, engagement tracking, analytics frameworks, and ROI measurement.

8. Moderation & Governance (moderation)

Impact: MEDIUM-HIGH Description: Community guidelines, moderation practices, governance structures, and conflict resolution.

9. Developer Relations (devrel)

Impact: MEDIUM-HIGH Description: DevRel fundamentals, developer advocacy, technical community building, and developer experience.

User-Generated Content Programs

Impact: HIGH

User-generated content (UGC) scales community value exponentially. When members create content, they deepen their commitment and attract new members through authentic voices. Communities with strong UGC see 3-5x more organic growth.

The UGC Value Chain

Member creates content
        ↓
Community amplifies
        ↓
Content attracts new members
        ↓
New members see value
        ↓
New members create content
        ↓
[Flywheel accelerates]

UGC Content Types

UGC Program Framework

Good UGC Programs

Community Templates Program:

"Share Your Template"

We know you've built amazing [templates/workflows/configs].
Share them with the community!

How it works:
1. Submit your template + brief description
2. Community team reviews for quality
3. Approved templates featured in library
4. You get credit + contributor badge

Benefits:
✓ Help other members succeed
✓ Build your reputation
✓ Get feedback on your approach
✓ Featured in newsletter to 10k+ subscribers

[Submit Template] button

Tutorial Contribution Program:

"Write for [Community]"

Share your expertise with our community of [X,000] members.

What we're looking for:
- How-to guides (1,000-2,000 words)
- Real implementations and lessons learned
- Tips and tricks that aren't documented

What you get:
- Editor support and feedback
- Featured on community blog
- Promoted to our audience
- $100 honorarium per published piece

Process:
1. Pitch your idea (2-3 sentences)
2. We respond within 1 week
3. Write with editorial support
4. Publish and promote together

[Submit Pitch] button

Case Study Program:

"Tell Your Story"

We want to feature how you're using [Product] in the real world.

Story format:
- The challenge you faced
- How you solved it
- Results and lessons learned
- Screenshots/examples welcome

What you get:
- Professional writeup (we do the work)
- Featured on website and newsletter
- Backlink to your site/profile
- Recognition in community

Time commitment: 30-minute interview

[Schedule Interview] button

Bad UGC Programs

"Share your content!"

✗ No specific ask
  → Members don't know what to share

✗ No incentive or recognition
  → Why should they bother?

✗ No distribution promise
  → Content dies in obscurity

✗ Complex submission process
  → Friction kills participation

✗ No quality bar
  → Garbage in, garbage out

✗ No templates or guidance
  → Results vary wildly

UGC Incentive Models

Recognition Hierarchy

Level 1: React (everyone)
- Staff reacts to every contribution
- "Thanks for sharing!"

Level 2: Highlight (great contributions)
- Featured in community
- "Check out what [member] built"

Level 3: Amplify (exceptional)
- Newsletter feature
- Social media share
- "Our member [name] wrote this amazing guide"

Level 4: Permanent (outstanding)
- Hall of fame
- Contributor page
- "Community heroes"

UGC Quality Framework

Content Contribution Workflow

1. CALL FOR CONTENT
   - Clear brief with examples
   - Submission guidelines
   - Deadline and timeline

2. SUBMISSION
   - Easy submission form
   - Structured template
   - Auto-confirmation

3. REVIEW
   - Quality check
   - Feedback within [X] days
   - Accept/revise/decline

4. EDITORIAL
   - Light editing for clarity
   - Formatting consistency
   - Author approval

5. PUBLISH
   - Publish with attribution
   - Notify contributor
   - Promote across channels

6. CELEBRATE
   - Public recognition
   - Reward delivered
   - Thank you message

UGC Channels by Platform

Discord:

• #show-and-tell for project shares
• #resources for links and templates
• #guides for member tutorials
• Pinned messages for best content

Slack:

• #wins for success stories
• #share-your-work for projects
• #resources for useful content
• Canvas for curated collections

Forum/Circle:

• Dedicated "Resources" space
• "Tutorials" category
• "Templates" library
• Pinned best-of collections

Content Curation

UGC Metrics

Scaling UGC

Legal Considerations

Anti-Patterns

• Taking without giving — Use member content without recognition
• Over-editing — Change voice so much it's not theirs anymore
• Unpaid labor framing — "Contribute for exposure" to professionals
• No feedback loop — Submit and never hear back
• Low-quality flood — Accept everything, quality suffers
• Gatekeeping — Standards so high no one can contribute
• One-time ask — No ongoing program or system
• Inconsistent amplification — Some content promoted, most ignored
• No attribution — Using UGC without crediting creator
• Complex processes — Friction kills contribution motivation

Developer Relations Basics

Impact: MEDIUM-HIGH

Developer Relations (DevRel) bridges the gap between your product and the developer community. Great DevRel builds trust through genuine value, not marketing disguised as help. Developers have finely tuned BS detectors — authenticity is non-negotiable.

The DevRel Pillars

┌─────────────────────────────────────────────────────────────┐
│                        DEVREL                               │
├─────────────────┬─────────────────┬─────────────────────────┤
│    ADVOCACY     │   COMMUNITY     │      EDUCATION          │
│                 │                 │                         │
│ - Speaking      │ - Forums        │ - Documentation         │
│ - Writing       │ - Discord/Slack │ - Tutorials             │
│ - Social media  │ - Events        │ - Sample code           │
│ - Podcasts      │ - Champions     │ - Workshops             │
│ - Open source   │ - Support       │ - Courses               │
└─────────────────┴─────────────────┴─────────────────────────┘

DevRel Functions

Developer Journey

AWARENESS
├── Discover through content, word of mouth, search
├── First impression of brand and community
└── "This might solve my problem"

EVALUATION
├── Read docs, try tutorials
├── Ask questions in community
└── "Can I actually build what I need?"

ADOPTION
├── First successful implementation
├── Integrate into workflow
└── "This works for my use case"

RETENTION
├── Ongoing usage and expansion
├── Deep platform understanding
└── "This is part of my stack"

ADVOCACY
├── Recommend to peers
├── Create content, contribute
└── "Everyone should use this"

Content for Developers

Good Developer Content

Tutorial: "Build a Real-Time Dashboard with [Product]"

✓ Clear outcome stated upfront
  "By the end, you'll have a working dashboard that updates live"

✓ Prerequisites listed
  "You'll need: Node.js 18+, basic React knowledge, free [Product] account"

✓ Working code throughout
  [Complete, runnable code snippets]

✓ Explains the "why"
  "We use WebSockets here because polling would create latency..."

✓ Copy-pasteable commands
  $ npm install @product/sdk

✓ Troubleshooting section
  "If you see error X, check that Y..."

✓ Next steps
  "Now that you have basics working, try adding Z..."

Bad Developer Content

Tutorial: "Getting Started"

✗ Vague title and outcome
  "Learn how to use our product"

✗ Missing prerequisites
  Assumes knowledge without stating it

✗ Incomplete code
  "Add your configuration here..."

✗ No explanation
  Just code with no context

✗ Outdated examples
  Deprecated methods, old versions

✗ No error handling
  Happy path only, fails silently

✗ Dead end
  "Now you're ready to explore!"

Documentation Principles

DevRel Events

Speaking at Conferences

Before submitting:
✓ Know the audience (beginners? experts? mixed?)
✓ Pick timely, relevant topic
✓ Clear takeaway for attendees
✓ Original angle or insight

Good talk proposal:
"5 Lessons from Scaling WebSocket Connections to 1M Users"
- Clear topic and scope
- Numbers suggest real experience
- Practical takeaways promised
- Relevant to platform users

Bad talk proposal:
"Introduction to [Product]"
- Product pitch, not value
- No clear learning
- Self-serving

Technical Content Calendar

DevRel Metrics

Developer Experience (DX)

DX Checklist:
□ Signup takes < 2 minutes
□ First API call in < 5 minutes
□ "Hello World" tutorial works
□ Error messages are helpful
□ Docs are searchable and complete
□ SDKs for major languages
□ Community support available
□ Status page exists
□ Changelog maintained
□ Migration guides provided

DX Killers:
✗ Complex authentication
✗ Outdated documentation
✗ No error explanations
✗ Slow or unresponsive APIs
✗ Breaking changes without warning
✗ No community or support

Feedback Loop

Developer Feedback Sources:
- Community questions and discussions
- Support tickets
- GitHub issues
- Social media mentions
- Direct conversations
- Surveys and NPS
- Usage analytics

Feeding back to product:
1. Collect and categorize feedback
2. Identify patterns and priorities
3. Create feature requests with evidence
4. Advocate in product discussions
5. Close loop with developers when shipped

Open Source Strategy

Building Trust with Developers

Trust builders:
✓ Ship what you promise
✓ Admit mistakes publicly
✓ Provide honest comparisons (including weaknesses)
✓ Transparent pricing
✓ Responsive to feedback
✓ Active in community (not just announcements)
✓ Hire technical people who understand developers
✓ Open source what you can

Trust destroyers:
✗ Marketing speak in technical content
✗ Ignoring bugs or issues
✗ Fake reviews or testimonials
✗ Hidden pricing or gotchas
✗ Abandoned libraries or docs
✗ Community used only for sales
✗ Non-technical evangelists pretending

DevRel Team Structure

Scaling DevRel

Anti-Patterns

• Marketing disguised as DevRel — Developers see through it instantly
• Non-technical advocates — Can't go deep, lose credibility
• Metrics over value — Optimizing signups over genuine help
• Ignoring feedback — Worst when you ask for it then do nothing
• Documentation debt — Outdated docs worse than no docs
• Conference collecting — Speaking everywhere with no strategy
• Community abandonment — Launch then ghost
• SDK neglect — Unmaintained libraries hurt more than help
• Overselling — Promising what product can't deliver
• No internal voice — DevRel should influence product, not just explain it

Engagement Programs and Rituals

Impact: HIGH

Rituals create rhythm. Regular, predictable engagement opportunities transform occasional visitors into committed members. Communities with consistent rituals see 40-60% higher retention.

The Engagement Hierarchy

COMMITMENT LEVEL (Low → High)
│
├── Consume        (Read, watch, lurk)
├── React          (Like, emoji, upvote)
├── Reply          (Comment, answer)
├── Create         (Post, share, write)
├── Organize       (Host, lead, moderate)
└── Evangelize     (Refer, represent, champion)

Ritual Design Framework

Core Community Rituals

Weekly Rituals

Monday Motivation:

Format: Discussion thread
Prompt: "What's your focus this week?"
Value: Accountability, goal-setting
Participation: Comment your goal

Example:
"Monday Focus: Share one thing you're working on this week.
Reply with your goal and we'll check in Friday!"

Wednesday Wins:

Format: Celebration thread
Prompt: "Share a win from this week"
Value: Positivity, social proof
Participation: Share + celebrate others

Example:
"Win Wednesday: Big or small, share something that went well!
Let's celebrate each other's progress."

Friday Feedback:

Format: Showcase thread
Prompt: "Share something you made"
Value: Peer feedback, visibility
Participation: Share work, give feedback

Example:
"Feedback Friday: Share a project, get constructive feedback.
Rule: Give feedback to get feedback!"

Office Hours Format

Good Office Hours:

Structure:
- 30-60 minutes, consistent time
- Open Q&A or themed topics
- Leader/expert answers live
- Questions can be submitted in advance

Flow:
[0-5 min]   Welcome, housekeeping
[5-45 min]  Q&A (pre-submitted + live)
[45-55 min] Open discussion
[55-60 min] Wrap-up, next session

Post-session:
- Summary posted to community
- Unanswered questions addressed async
- Recording shared (if applicable)

Bad Office Hours:

✗ No structure, awkward silence
✗ Same 3 people ask all questions
✗ No advance promotion
✗ Inconsistent timing
✗ No follow-up or summary

Show & Tell Programs

Structure:

Format: Video call or async thread
Cadence: Weekly or bi-weekly
Duration: 5-10 min per showcase

Good Example:
"Community Showcase
Every Thursday, 3 members share what they're building.
- 5 min presentation
- 5 min Q&A
- Sign up: [link]

Why join?
✓ Get feedback from peers
✓ Discover what others are building
✓ Build your reputation"

Selection Criteria:
- Rotating participants (not same people)
- Mix of experience levels
- Variety of topics/projects

Challenge Programs

Monthly Challenge Framework:

Week 1: Announce + Sign Up
- Clear theme and rules
- Defined success criteria
- Registration open

Week 2-3: Execution
- Progress check-ins
- Support and Q&A
- Midpoint motivation

Week 4: Showcase + Awards
- Submissions due
- Community voting
- Winners announced
- Celebration

Good Challenge Example:
"30-Day Build Challenge
Build and ship something using [product/skill].
- Post daily progress
- Get peer feedback
- Win prizes and recognition

Prizes:
- 1st: $500 + featured spotlight
- 2nd: $250 + swag
- 3rd: $100 + swag
- All finishers: Badge + recognition"

AMA (Ask Me Anything) Sessions

Planning Checklist:

2 weeks before:
- [ ] Confirm guest and topic
- [ ] Collect pre-submitted questions
- [ ] Promote across channels

1 week before:
- [ ] Send guest prep materials
- [ ] Finalize question queue
- [ ] Test tech (if video)

Day of:
- [ ] Final promotion
- [ ] Moderate live questions
- [ ] Keep time, manage flow

After:
- [ ] Share summary/transcript
- [ ] Thank guest publicly
- [ ] Gather feedback

Good AMA Example:

AMA with [Expert Name]
[Role], [Company]

Topic: [Specific focus area]
When: [Date/Time] (timezone)
Where: #ama-channel

How it works:
1. Drop questions below (upvote favorites)
2. [Expert] answers top questions live
3. Follow-up discussion in thread

About [Expert]:
[2-3 sentence bio]
[Why they're relevant to community]

Community Events Calendar

Engagement Program Metrics

Good Engagement Program

Program: "Weekly Wins"
Cadence: Every Friday
Format: Thread in #wins channel

Structure:
- Bot posts prompt at 9am
- Members share wins throughout day
- Team reacts to every post
- Best wins featured in newsletter

Why it works:
✓ Low effort to participate
✓ Positive energy
✓ Consistent timing
✓ Recognition built in
✓ Content for other channels

Bad Engagement Program

Program: "Monthly Mega Event"
Cadence: First Monday each month
Format: 2-hour video call

Problems:
✗ Too long, drops off
✗ Same people every time
✗ No async option
✗ Time zone unfriendly
✗ No follow-up
✗ Unclear value prop

Scaling Rituals

Ritual Launch Checklist

• [ ] Clear name and description
• [ ] Consistent cadence set
• [ ] Value proposition defined
• [ ] Format documented
• [ ] Owner assigned
• [ ] Promotion plan ready
• [ ] First 4 weeks planned
• [ ] Success metrics defined
• [ ] Feedback mechanism in place
• [ ] Iteration plan if needed

Anti-Patterns

• Too many rituals — Member fatigue, none get traction
• Inconsistent timing — "Every other Tuesday-ish" doesn't work
• No one shows up — Launch without promotion, wonder why empty
• Same participants — Clique forms, others feel excluded
• Founder burnout — Running everything yourself isn't sustainable
• Complex formats — Keep it simple, especially early
• No celebration — Miss opportunity to recognize participants
• Copy-paste other communities — What works for them may not fit your culture
• Ignoring feedback — Ritual doesn't improve, participation dies
• All synchronous — Excludes members in different time zones

Community Metrics and Health

Impact: HIGH

What gets measured gets managed — but measuring the wrong things destroys communities. Vanity metrics mislead; health metrics guide. Focus on engagement quality over quantity, and always connect community metrics to business impact.

The Metrics Framework

┌─────────────────────────────────────────────────────────────┐
│                    BUSINESS IMPACT                          │
│    Revenue influence, Support deflection, Retention         │
├─────────────────────────────────────────────────────────────┤
│                    COMMUNITY HEALTH                         │
│    Sentiment, Response quality, Member satisfaction         │
├─────────────────────────────────────────────────────────────┤
│                    ENGAGEMENT DEPTH                         │
│    Active rate, Response rate, Contribution quality         │
├─────────────────────────────────────────────────────────────┤
│                    ENGAGEMENT BREADTH                       │
│    DAU/MAU, Posts, Reactions, Time spent                    │
├─────────────────────────────────────────────────────────────┤
│                       GROWTH                                │
│    New members, Churn rate, Net member growth               │
└─────────────────────────────────────────────────────────────┘

Core Community Metrics

The DAU/MAU Ratio (Stickiness)

DAU/MAU = Daily Active Users / Monthly Active Users

Interpretation:
- 50%+ : Exceptional (daily habit)
- 30-50%: Strong (regular engagement)
- 15-30%: Healthy (weekly engagement)
- 10-15%: Moderate (casual engagement)
- <10%  : Weak (occasional visitors)

Context matters:
- Developer community: 20%+ is excellent
- Customer support community: 10-15% is normal
- Learning community: 15-25% is healthy

Engagement Depth Metrics

The 1-9-90 Measurement

Typical Community Distribution:
- 1% Creators (post original content)
- 9% Contributors (reply, react, engage)
- 90% Lurkers (consume only)

Healthy Targets:
- Creators: 3-5%
- Contributors: 15-25%
- Lurkers: 70-80%

Measurement:
Creator % = Members with 3+ posts / Total members
Contributor % = Members with any interaction / Total members
Lurker % = Members with no interaction / Total members

Health Indicators

Positive Health Signs:

✓ Questions get answered quickly (< 24h)
✓ Multiple members respond to questions
✓ New members stick around (D7 retention > 25%)
✓ Old members stay active (low churn)
✓ Sentiment is positive (> 80%)
✓ Content is diverse (not same few people)
✓ Peer-to-peer interactions happen
✓ Members refer others

Warning Signs:

✗ Questions go unanswered
✗ Same 5 people post everything
✗ New members disappear quickly
✗ Negative sentiment increasing
✗ Drama/conflict escalating
✗ Staff doing all the answering
✗ Spam increasing
✗ Members complaining about community

Retention Cohort Analysis

Reading the table:

• D1: % of members who engage again within 1 day
• D7: % still active after 7 days
• D30: % still active after 30 days
• Improvement over time = better onboarding

Business Impact Metrics

Support Deflection Calculation

Method 1: Volume comparison
- Support tickets before community: 1,000/month
- Support tickets after community: 700/month
- Community questions answered: 400/month
- Deflection rate: (1000-700)/1000 = 30%

Method 2: Cost calculation
- Questions answered by community: 400/month
- Avg support ticket cost: $15
- Savings: 400 × $15 = $6,000/month

Method 3: Survey
- Survey community members
- "Did this answer prevent you from contacting support?"
- Calculate deflection %

Community ROI Framework

Community Investment:
- Team salaries
- Platform costs
- Programs/events
- Tools/software
= Total Investment

Community Value:
- Support deflection savings
- Community-influenced revenue
- Reduced churn (retained revenue)
- Content/UGC value
- Referral value
= Total Value

ROI = (Total Value - Total Investment) / Total Investment

Benchmarks by Community Type

Good Metrics Dashboard

┌──────────────────────────────────────────────────────────┐
│ COMMUNITY HEALTH DASHBOARD                    [Dec 2024] │
├──────────────────────────────────────────────────────────┤
│ GROWTH                                                   │
│ Total Members:  12,450  (+450 this month)               │
│ New Members:    520     (vs 480 last month)             │
│ Churned:        70      (vs 85 last month)              │
│ Net Growth:     +450    (+3.6%)                         │
├──────────────────────────────────────────────────────────┤
│ ENGAGEMENT                                               │
│ DAU:           1,870    (15% of total)                  │
│ WAU:           4,200    (34% of total)                  │
│ MAU:           7,450    (60% of total)                  │
│ DAU/MAU:       25%      (Healthy)                       │
├──────────────────────────────────────────────────────────┤
│ CONTENT                                                  │
│ Posts:         1,240    (vs 1,100 last month)           │
│ Replies:       4,500    (3.6 per post)                  │
│ Contributors:  580      (4.7% of members)               │
├──────────────────────────────────────────────────────────┤
│ HEALTH                                                   │
│ Response Rate:     92%     (Target: >90%)               │
│ Avg Response Time: 3.2h    (Target: <24h)               │
│ Sentiment:         87%     (Target: >80%)               │
│ D7 Retention:      32%     (vs 28% last month)          │
├──────────────────────────────────────────────────────────┤
│ BUSINESS IMPACT                                          │
│ Support Deflection: $18,400 saved                       │
│ Community Revenue:  $245,000 influenced                 │
│ Member NPS:         +52     (vs +38 non-members)        │
└──────────────────────────────────────────────────────────┘

Bad Metrics Focus

Vanity Metrics to Avoid:
✗ Total member count (without engagement context)
✗ Impressions or views (without action)
✗ Followers (if not engaged)
✗ "Community size" without activity

Why they mislead:
- 100k members with 1% active = 1,000 active
- 10k members with 25% active = 2,500 active
- The smaller community is healthier

Better alternatives:
✓ Active members (WAU, MAU)
✓ Engagement rate (DAU/MAU)
✓ Retention (D7, D30)
✓ Business impact (revenue, deflection)

Metric Review Cadence

Tools for Measurement

Anti-Patterns

• Measuring only growth — Big community can be dead community
• Ignoring retention — Acquiring members you can't keep wastes effort
• Vanity over value — "100k members!" means nothing if they're inactive
• No business connection — Can't justify investment without ROI
• Gaming metrics — Engagement for engagement's sake
• Over-measuring — Drowning in data, no action
• Under-measuring — Flying blind, can't improve
• Ignoring qualitative — Numbers don't capture community feel
• Comparing wrong benchmarks — Your community is unique
• Measuring too frequently — Daily changes are noise, not signal

Moderation and Governance

Impact: MEDIUM-HIGH

Moderation is invisible when done well and catastrophic when done poorly. One unchecked bad actor can poison a community; one heavy-handed moderation decision can spark exodus. Clear governance structures and consistent enforcement create the safety that allows authentic community to flourish.

Governance Framework

┌─────────────────────────────────────────────────────────────┐
│                      CODE OF CONDUCT                        │
│           Community values and expected behavior            │
├─────────────────────────────────────────────────────────────┤
│                      COMMUNITY GUIDELINES                   │
│           Specific rules for participation                  │
├─────────────────────────────────────────────────────────────┤
│                      ENFORCEMENT POLICY                     │
│           What happens when rules are broken                │
├─────────────────────────────────────────────────────────────┤
│                      MODERATION TEAM                        │
│           Who enforces and how                              │
└─────────────────────────────────────────────────────────────┘

Code of Conduct Elements

Good Code of Conduct

[Community Name] Code of Conduct

Our Mission:
[Community] is a space for [identity] to [value]. We're committed
to providing a welcoming, inclusive environment for everyone.

Expected Behavior:
- Be respectful and constructive in all interactions
- Assume good intent; seek to understand before reacting
- Help others learn; we were all beginners once
- Give credit where due; cite sources and acknowledge others
- Respect privacy; don't share others' information

Unacceptable Behavior:
- Harassment, intimidation, or discrimination of any kind
- Personal attacks, insults, or inflammatory language
- Spam, self-promotion without value, or advertising
- Sharing private information without consent
- Deliberately derailing conversations or trolling
- Any illegal activity

Enforcement:
1. First violation: Private warning
2. Second violation: Temporary timeout (7 days)
3. Third violation: Permanent removal
Severe violations may result in immediate removal.

Reporting:
- DM any @Moderator
- Email: conduct@community.com
- Reports are handled confidentially

This code applies to all community spaces including chat, forums,
events, and any official community gathering.

Bad Code of Conduct

✗ Too long and legalistic
  → No one reads 10 pages of rules

✗ Too vague
  → "Be nice" doesn't define boundaries

✗ No enforcement clarity
  → People don't know consequences

✗ No reporting mechanism
  → Victims have nowhere to turn

✗ Copy-pasted template
  → Doesn't reflect community values

Community Guidelines vs Code of Conduct

Channel/Space Rules

#general
- All community topics welcome
- Keep it friendly and constructive
- Use threads for longer discussions

#help
- Ask specific, searchable questions
- Show what you've tried
- Mark solved questions as resolved
- No "just Google it" responses

#show-and-tell
- Share what you're working on
- Give constructive feedback
- Celebrate others' work
- Self-promotion allowed here

#jobs
- Job posts only (no discussion)
- Include: role, company, location, salary range
- No recruiters spamming
- One post per opening

Moderation Team Structure

Moderator Selection

Ideal moderator traits:
✓ Respected community member
✓ Calm under pressure
✓ Fair and consistent
✓ Good judgment
✓ Available regularly
✓ Aligned with community values
✓ Can keep confidentiality

Red flags:
✗ Power-seeking
✗ History of conflict
✗ Biased toward certain members
✗ Inconsistent activity
✗ Poor communication

Moderation Actions

The Escalation Ladder

Level 1: Peer feedback
- Community members remind each other
- "Hey, let's keep this constructive"

Level 2: Soft moderation
- Moderator redirects conversation
- Moves content to appropriate channel
- Public but gentle correction

Level 3: Private warning
- DM to member
- Explain the issue
- Set expectations

Level 4: Public warning
- Visible intervention
- Clear statement of violation
- Last chance before action

Level 5: Temporary timeout
- Mute or suspend (1-30 days)
- Explain reason and duration
- Path to return

Level 6: Permanent removal
- Ban from community
- Document reason
- Final decision

Good Moderation Example

Situation: Member posts aggressive reply to someone's question

Bad response:
"Don't be rude. This is your warning."
→ Public shaming, defensive reaction

Good response:
[Private DM]
"Hey [Name], I noticed your reply to [Member]'s question
came across pretty harsh. I know you're knowledgeable
and probably frustrated with basic questions, but we want
everyone to feel comfortable asking here.

Could you help us keep the tone welcoming? Maybe point them
to resources instead of criticizing the question.

Thanks for being part of the community - we value your expertise."

→ Private, assumes good intent, explains impact, requests behavior

Conflict Resolution

Step 1: Cool down
- Pause the public conversation
- "Let's take a break from this thread"

Step 2: Understand
- DM both parties separately
- Get each perspective
- Identify the actual issue

Step 3: Mediate (if appropriate)
- Facilitate direct conversation
- Focus on resolution, not blame
- Find common ground

Step 4: Resolve
- Agree on path forward
- Document if needed
- Follow up to ensure resolved

Step 5: Learn
- What could prevent this next time?
- Do guidelines need updating?
- Were there warning signs missed?

Handling Difficult Situations

Transparency in Moderation

What to share publicly:
✓ Community guidelines and CoC
✓ General enforcement philosophy
✓ Changes to rules (with explanation)
✓ Aggregate moderation stats (optional)

What to keep private:
✗ Specific violation details
✗ Individual warning history
✗ Internal moderator discussions
✗ Reporter identities

Documentation

Moderation Log Entry:
- Date/time
- Member involved
- Violation type
- Evidence (screenshots, links)
- Action taken
- Moderator handling
- Notes for future reference

Why document:
✓ Consistency across moderators
✓ Track patterns
✓ Defend decisions if challenged
✓ Training for new moderators

Automated Moderation

Moderation Burnout Prevention

For moderators:
✓ Set boundaries (don't be on-call 24/7)
✓ Share the load (rotation, coverage)
✓ Private mod channel to vent/debrief
✓ Recognition for the invisible work
✓ Permission to step back when needed

For community managers:
✓ Don't rely on one hero moderator
✓ Compensate volunteer mods (swag, access, recognition)
✓ Regular check-ins with mod team
✓ Clear escalation paths
✓ Handle the hardest stuff yourself

Anti-Patterns

• No rules — "We're chill" until something goes wrong
• Too many rules — Over-regulation kills authentic conversation
• Inconsistent enforcement — Favorites get passes, undermines trust
• Public shaming — Calling out violations publicly creates defensiveness
• Slow response — Drama festers when mods aren't around
• No escalation path — Mods stuck with impossible decisions
• Power-tripping mods — Moderators on ego trips drive members away
• Ignoring context — Rules without judgment miss nuance
• No appeals — One mod's bad call is permanent
• Volunteer mod exploitation — Expecting free labor indefinitely

Member Onboarding and Activation

Impact: CRITICAL

60-70% of new community members who don't engage in the first 48 hours never return. Onboarding determines whether someone becomes an active member or a ghost account.

The First 48 Hours

Hour 0:    Join → Immediate welcome
Hour 0-1:  Orientation → Understand the space
Hour 1-24: First interaction → Post, reply, or react
Hour 24-48: Second visit → Return and engage again
Day 7:     Habit formation → Weekly active
Day 30:    Retention → Monthly active

Member Activation Framework

The "Aha Moment" for Communities

Welcome Flow Design

Good Welcome Flow:

Step 1: Immediate Welcome
┌──────────────────────────────────────────────────────┐
│  Welcome to [Community], [Name]!                     │
│                                                      │
│  You've joined 5,000+ [identity] who [value prop].   │
│                                                      │
│  Here's how to get started:                          │
│  ✓ Introduce yourself in #introductions              │
│  ✓ Check out our top resources                       │
│  ✓ Join our weekly office hours (Thursdays)          │
│                                                      │
│  Questions? Reply here or DM any @Team member.       │
└──────────────────────────────────────────────────────┘

Step 2: Introduction Prompt
"Tell us: What brought you here? What are you working on?"

Step 3: Personalized Follow-up (24h)
"Hey [Name], I noticed you're interested in [topic].
You might enjoy #channel-name and this resource: [link]"

Step 4: Check-in (7 days)
"How's your first week going? Anything we can help with?"

Bad Welcome Flow:

✗ Generic auto-message
  "Welcome to the community. Read the rules."
  → Cold, uninviting, no next action

✗ Information overload
  "Here are 47 channels, 12 programs, 8 rules..."
  → Overwhelming, causes abandonment

✗ No human touch
  → Members don't feel seen or valued

✗ No clear first action
  → Members don't know what to do next

Introduction Post Templates

Prompt that works:

Hey [Name], welcome!

We'd love to learn about you:
- What do you do?
- What brought you to [Community]?
- What's one thing you're hoping to get from being here?

Drop your intro below and we'll connect you with the right people!

What to avoid:

✗ "Introduce yourself"
  → Too vague, gets ignored

✗ 10-question form
  → Too much friction

✗ No response to introductions
  → Members feel invisible

Onboarding by Platform

Discord Onboarding:

1. Server join → Auto-role assignment
2. Welcome DM from bot with quick start
3. Locked channels until intro posted (optional)
4. Reaction roles for interests
5. Team member welcome in public channel

Slack Onboarding:

1. Invite accepted → Slackbot welcome
2. #welcome channel with pinned resources
3. Prompt to post in #introductions
4. Team member DM within 24h
5. Add to relevant channels based on interests

Circle/Forum Onboarding:

1. Account created → Welcome email
2. Guided tour of spaces
3. Prompt to create profile
4. First post in introductions
5. Follow-up email if inactive

Activation Triggers and Actions

Personalization Opportunities

Onboarding Metrics

Reducing Join Friction

Activation Checklist Template

Welcome to [Community]! Complete these to get the most value:

□ Set up your profile (photo + bio)
  "Helps people connect with you"

□ Introduce yourself in #introductions
  "Tell us what you're working on"

□ React or reply to one post
  "Jump into a conversation"

□ Bookmark 3 resources
  "Save what's useful for later"

□ Join your first event
  "Meet the community live"

Progress: 2/5 complete
[🎉 Unlock Champion badge when you finish!]

Cohort-Based Onboarding

For larger communities, onboard in cohorts:

Benefits:
✓ Peer connections from day one
✓ Shared experience creates bonds
✓ Scalable human touch
✓ Built-in accountability

Structure:
Week 1: Welcome, introductions, orientation
Week 2: Deep dive on value, first contributions
Week 3: Connecting with broader community
Week 4: Graduation, integration into main community

New Member Segments

Anti-Patterns

• Gated first action — "Post intro before you can access anything" drives away lurkers
• Bot-only welcome — No human touch in first 48 hours
• Information dump — 20 links in welcome message overwhelms
• One-size-fits-all — Different members need different paths
• No follow-up — Welcome then abandon
• Ignoring introductions — Members post and get no response
• Forcing engagement — Mandating participation creates resentment
• Slow response to questions — First question unanswered = member lost
• Complex onboarding — Every step is a drop-off point
• No clear value — "Welcome" without "here's what you get"

Discord and Slack Community Setup

Impact: CRITICAL

Discord and Slack are the two dominant real-time community platforms. Each requires specific setup, bots, and configuration to run effectively. A well-configured server creates clarity; a poorly configured one creates chaos.

Discord Server Setup

Channel Structure

Good Discord Structure:

📋 WELCOME
├── #rules (read-only, pinned CoC)
├── #announcements (admin-only, important updates)
├── #introductions (new member posts)
└── #roles (self-assign interests)

💬 GENERAL
├── #general (main conversation)
├── #off-topic (non-work chat)
└── #random (memes, fun)

❓ SUPPORT
├── #help (questions and answers)
├── #troubleshooting (technical issues)
└── #feedback (product feedback)

🔧 PRODUCT
├── #feature-requests
├── #bug-reports
└── #beta (invite-only)

📚 RESOURCES
├── #tutorials (pinned guides)
├── #showcase (member projects)
└── #jobs (career opportunities)

🎉 COMMUNITY
├── #wins (celebrations)
├── #events (upcoming activities)
└── #content (member blogs, videos)

🔒 PRIVATE
├── #champions (invite-only)
├── #team (staff only)
└── #mods (moderator discussion)

Bad Discord Structure:

✗ 30+ visible channels
  → Overwhelming, nobody knows where to post

✗ Unclear channel names
  → #channel-1, #stuff, #misc

✗ No read-only channels
  → Announcements get buried

✗ Everything visible to everyone
  → No progression or exclusivity

Discord Role Setup

Discord Bot Essentials

Discord Verification Flow

New Member Joins
       ↓
Lands in #rules (only visible channel)
       ↓
Reads rules, reacts with ✅
       ↓
Bot assigns @Member role
       ↓
Full server access unlocked
       ↓
Welcome bot DMs with quick start
       ↓
Posts intro in #introductions

Discord Best Practices

✓ Use threads for extended conversations
  → Keeps channels clean, creates context

✓ Set slow mode for high-traffic channels
  → #general: 5-10 seconds prevents spam

✓ Use forums for Q&A channels
  → Searchable, structured, resolvable

✓ Pin important messages (sparingly)
  → 3-5 pins max per channel

✓ Create reaction roles for interests
  → Let members opt into topic channels

✓ Set up server discovery
  → Allows organic growth (if public)

✓ Configure logging
  → Track joins, leaves, deletions for safety

Slack Workspace Setup

Channel Structure

Good Slack Structure:

PUBLIC CHANNELS
├── #announcements (admin-only posting)
├── #introductions (new member posts)
├── #general (main conversation)
├── #random (off-topic, social)
├── #help (questions and support)
├── #feedback (product feedback)
├── #jobs (career posts)
├── #events (community events)
├── #wins (celebrations)
└── #resources (links, guides)

TOPIC CHANNELS (as needed)
├── #topic-frontend
├── #topic-backend
├── #topic-devops
└── #topic-design

PRIVATE CHANNELS
├── #champions (invite-only)
├── #team (staff only)
└── #mods (moderator discussion)

Bad Slack Structure:

✗ No default channels
  → People join and see nothing

✗ Too many channels too early
  → Empty channels signal dead community

✗ No topic organization
  → Everything in #general, chaos

✗ Private channels for general discussion
  → Fragments community

Slack Workspace Settings

Slack Apps and Integrations

Slack Etiquette Guidelines

Channel Guidelines:

#general
- All community topics welcome
- Use threads for extended discussions
- Keep it constructive and helpful

#help
- Search before asking (Cmd+K)
- Be specific: include error messages, code
- Use code blocks for code (```)
- Mark questions as resolved with ✅

#announcements
- Admin posts only
- Important updates and news
- React with 👍 to acknowledge

#random
- Off-topic, social, fun
- Memes welcome
- Be respectful

Discord vs Slack: When to Use

Bot Configuration Best Practices

Welcome Bot Setup

Good Welcome Message:

Welcome to [Community], {username}!

You've joined [X,000] [identity] who [value prop].

Quick start:
1. Read #rules and react ✅ to get full access
2. Introduce yourself in #introductions
3. Browse #resources for guides
4. Ask questions in #help

Questions? DM any @Team member or post in #help.

See you around!

Bad Welcome Message:

✗ Too long (10+ lines)
✗ No clear next action
✗ Generic ("Welcome to our server")
✗ Overwhelming with options

Auto-Moderation Setup

Channel Naming Conventions

Prefixes for Slack:

#team-*     → Team channels
#proj-*     → Project channels
#help-*     → Support channels
#social-*   → Social channels
#announce-* → Announcements

Notification Management

Discord:

Server Settings:
- Notification settings: Only @mentions
- Suppress @everyone/@here for most roles
- Create #announcements with @everyone sparingly

Member guidance:
"Right-click channels → Notification Settings
Set most to 'Only @mentions' to avoid overwhelm"

Slack:

Channel Defaults:
- #announcements: All messages
- #general: Mentions only (after initial period)
- Topic channels: Mentions only

Member guidance:
"Click channel name → Notifications → Customize
Most channels work best with 'Mentions only'"

Migration Between Platforms

Anti-Patterns

Discord:

• Too many channels — Start with 10, add when needed
• Complicated role system — Simple hierarchy wins
• No verification — Bots and spam flood server
• Voice channels everywhere — Nobody uses most of them
• No thread culture — Channels become unreadable

Slack:

• Free tier forever — 90-day limit hurts community memory
• Channel explosion — Create policy before proliferation
• No default channels — New members see empty workspace
• Email-like behavior — DMs when channels would build community
• No threading — Conversations collide

Both:

• No onboarding — Join → confusion → leave
• No moderation bots — Manual moderation doesn't scale
• Admin-only posting everywhere — Kills conversation
• No analytics — Flying blind on engagement
• Copy-paste setup — Every community has different needs

Community Platform Selection

Impact: CRITICAL

Platform choice shapes community culture, engagement patterns, and scalability. The wrong platform creates friction; the right one becomes invisible.

Platform Comparison Matrix

Platform Selection Framework

Discord Deep Dive

Best For: Developer communities, gaming, crypto, real-time collaboration

Strengths:

• Rich feature set (voice, video, threads, roles)
• Free at scale
• Bot ecosystem
• Familiar to technical audiences
• Server discovery for growth

Weaknesses:

• Overwhelming UX for newcomers
• No SEO (content is invisible to search)
• Notifications can be noisy
• Professional audience may resist

Good Discord Setup:

Server Structure:
├── 📋 START HERE
│   ├── #welcome (rules, intro)
│   ├── #introductions (new member posts)
│   └── #announcements (read-only)
├── 💬 COMMUNITY
│   ├── #general
│   ├── #help
│   └── #show-and-tell
├── 🔧 PRODUCT
│   ├── #feature-requests
│   ├── #bug-reports
│   └── #beta-testing
├── 🎯 TOPICS
│   ├── #topic-1
│   ├── #topic-2
│   └── #topic-3
└── 🎉 SOCIAL
    ├── #off-topic
    └── #wins-celebrations

Roles:
- @Team (staff, different color)
- @Champion (active contributors)
- @Beta Tester (early access)
- @New Member (auto-assigned)

Bad Discord Setup:

✗ 30+ channels visible on day one
  → Analysis paralysis, members don't know where to post

✗ No welcome channel or rules
  → Chaotic, spam-prone

✗ No role-based permissions
  → Noise everywhere, important stuff buried

✗ No moderation bots
  → Spam takes over quickly

Slack Deep Dive

Best For: Professional communities, B2B, enterprise, workplace-adjacent

Strengths:

• Familiar to professionals
• Excellent search
• Thread organization
• Enterprise-grade security
• App integrations

Weaknesses:

• Expensive at scale ($7.25/user/month for Pro)
• 90-day message limit on free
• Requires email invite
• Can feel like "more work"

Good Slack Setup:

Channel Structure:
├── #welcome (pinned resources, rules)
├── #introductions
├── #announcements (admin-only posting)
├── #general (main conversation)
├── #help-and-support
├── #share-your-work
├── #jobs-and-opportunities
├── #random (off-topic)
└── Topic channels as needed

Slack Connect:
- Enable for partner collaboration
- Create shared channels with power users

Cost Management:

Free tier works if:
- Community is < 500 active members
- 90-day history is acceptable
- Basic integrations suffice

Consider paid if:
- Need full history search
- Compliance requirements
- Advanced admin controls

Circle Deep Dive

Best For: Course creators, paid communities, creator economy

Strengths:

• Beautiful, modern UX
• Spaces organize topics clearly
• Events and courses built-in
• Good mobile experience
• SEO-friendly options

Weaknesses:

• Less real-time feel
• Smaller ecosystem
• Can feel empty if low activity
• Pricing scales with members

Good Circle Setup:

Space Structure:
├── Start Here
│   ├── Welcome (rules, orientation)
│   └── Introduce Yourself
├── Main Community
│   ├── General Discussion
│   └── Ask the Community
├── Learning
│   ├── Resources
│   └── Course Content
├── Showcase
│   └── Member Wins
└── Events
    └── Upcoming Sessions

Discourse Deep Dive

Best For: Open source, technical discussions, knowledge bases

Strengths:

• SEO excellence (content ranks)
• Threaded discussions scale
• Trust level system built-in
• Self-hosted option
• Mature, stable platform

Weaknesses:

• Forum UX feels dated to some
• Less real-time
• Steeper setup for self-hosted
• Mobile experience just okay

Good Discourse Setup:

Category Structure:
├── Welcome (rules, FAQ)
├── General Discussion
├── Help & Support
├── Feature Requests
├── Show & Tell
└── Meta (community feedback)

Trust Levels:
- TL0: New user (limited actions)
- TL1: Basic (earned through reading)
- TL2: Member (active participation)
- TL3: Regular (highly trusted)
- TL4: Leader (moderator-lite)

Platform Decision Tree

Start Here
    │
    ├─▶ Is real-time chat critical?
    │       │
    │       ├─▶ Yes ──▶ Is audience technical/gaming?
    │       │              │
    │       │              ├─▶ Yes ──▶ Discord
    │       │              └─▶ No  ──▶ Slack (if budget) or Discord
    │       │
    │       └─▶ No ──▶ Is SEO/discoverability important?
    │                      │
    │                      ├─▶ Yes ──▶ Discourse or Circle
    │                      └─▶ No  ──▶ Circle or Mighty Networks
    │
    └─▶ Is this for developers/open source?
            │
            ├─▶ Yes ──▶ GitHub Discussions or Discourse
            └─▶ No  ──▶ Continue above

Hybrid Platform Strategies

Migration Considerations

Platform Evaluation Checklist

• [ ] Where does target audience already hang out?
• [ ] What's the communication style (real-time vs async)?
• [ ] What's the 3-year growth projection?
• [ ] What integrations are required?
• [ ] What's the sustainable budget?
• [ ] Who will administer and moderate?
• [ ] What's the content strategy (SEO needs)?
• [ ] What are compliance/security requirements?
• [ ] Is white-label/custom branding needed?
• [ ] How will you handle migration if needed?

Anti-Patterns

• Choosing based on personal preference — What you like isn't what your audience uses
• Discord for enterprise B2B — Professionals may see it as "gaming app"
• Slack for 10k+ free community — Cost becomes prohibitive
• Multiple platforms from day one — Fragments community, exhausts team
• Ignoring mobile experience — 50%+ access via mobile
• No bot/automation strategy — Manual moderation doesn't scale
• Choosing for features, not culture fit — Features < where members thrive
• Assuming you can migrate easily — Platform switching is painful

Ambassador and Champion Programs

Impact: HIGH

Ambassadors are your community's force multipliers. Top community members who become ambassadors drive 10-30% of community activity and influence purchasing decisions 5x more than company content. A well-structured program transforms passionate users into community leaders.

Program Types

Champion vs Ambassador

Program Structure Framework

TIER 1: Community Members
│ Everyone can participate
│ Basic recognition for contributions
│
├── TIER 2: Champions (Top contributors)
│   │ Elevated permissions
│   │ Champion badge
│   │ Direct access to team
│   │
│   └── TIER 3: Ambassadors (Selected leaders)
│       │ Formal program membership
│       │ Exclusive benefits
│       │ External representation
│       │
│       └── TIER 4: Advisory (Top ambassadors)
│           Strategic input
│           Closest relationship
│           Highest benefits

Selection Criteria

Champion Selection (Organic Emergence):

Observe for:
✓ Consistently helpful (answers questions)
✓ Positive attitude (constructive, welcoming)
✓ Quality contributions (accurate, thoughtful)
✓ Regular presence (weekly or more active)
✓ Respected by peers (others engage with them)

Red flags:
✗ Only promotes themselves
✗ Argues or creates conflict
✗ Inconsistent activity
✗ Inaccurate information

Ambassador Application Criteria:

Required:
- Active community member (6+ months)
- Demonstrated expertise
- Positive community standing
- Willingness to commit

Preferred:
- External presence (blog, social, speaking)
- Relevant professional role
- Geographic/demographic diversity
- Passion for the mission

Application questions:
1. How have you contributed to the community?
2. What would you do as an ambassador?
3. What external platforms/audiences do you reach?
4. How many hours/month can you commit?

Ambassador Program Benefits

Tier 1: Basic Ambassador

Recognition:
- Official ambassador badge
- Directory listing
- Community recognition

Access:
- Private ambassador channel
- Monthly ambassador calls
- Early access to features

Resources:
- Exclusive content and assets
- Ambassador swag kit
- Speaking/writing support

Tier 2: Senior Ambassador

All Tier 1 benefits plus:

Recognition:
- Featured profile
- Conference speaking opportunities
- Co-marketing opportunities

Access:
- Product roadmap visibility
- Direct line to product team
- Quarterly strategy calls

Resources:
- Travel budget for events
- Content creation budget
- Premium swag

Tier 3: Advisory Board

All Tier 2 benefits plus:

Recognition:
- Advisor title
- Annual retreat invitation
- Public co-branding

Access:
- Strategic planning input
- Executive access
- Investment/career opportunities

Resources:
- Generous stipend
- Conference sponsorship
- Dedicated support contact

Good Ambassador Program

Program: [Product] Champions

Vision: Empower passionate users to lead and grow our community.

Membership: 50 ambassadors worldwide

Commitment: 5-10 hours/month

Requirements:
- Answer 5+ questions/month in community
- Create 1 piece of content/quarter
- Attend monthly ambassador call
- Represent positively in external interactions

Benefits:
- Champion badge and recognition
- Free premium subscription ($240/year value)
- Annual swag kit ($100 value)
- Quarterly virtual events
- Direct feedback channel to product team
- Priority support
- Conference ticket when speaking
- Referral bonuses ($100 per qualified lead)

Selection: Rolling applications, quarterly cohorts

Expectations documented, benefits clear, achievable commitment.

Bad Ambassador Program

Program: "[Product] VIPs"

Problems:
✗ Vague requirements
  "Help spread the word when you can"
  → No accountability, uneven participation

✗ Unclear benefits
  "Exclusive access and perks"
  → Sounds like marketing, not real value

✗ No structure
  → Enthusiastic launch, dies in 3 months

✗ One-size-fits-all
  → High performers feel same as inactive

✗ No community among ambassadors
  → Isolated, not connected to each other

✗ Take, don't give
  → Expect content, provide nothing

Activity Expectations

Gamification (Use Carefully)

Point System Example:
- 100 points/quarter: Maintain status
- 200 points/quarter: Silver tier
- 400 points/quarter: Gold tier
- 600 points/quarter: Platinum tier

Tier Benefits:
Silver: Basic swag, badge
Gold: Premium swag, early access
Platinum: All benefits, advisory access

Caution:
✓ Gamification motivates some
✗ Gamification turns off others
✓ Points for outcomes, not vanity
✗ Points for points' sake

Onboarding New Ambassadors

Week 1: Welcome
- Welcome email with program details
- Add to private channels
- Pair with ambassador buddy
- Send welcome swag

Week 2: Orientation
- Program expectations walkthrough
- Tools and resources training
- First activity assignment
- Meet the team call

Week 3-4: Integration
- First contribution supported
- Feedback and recognition
- Connect with peer ambassadors
- Establish regular rhythm

Month 2+: Ongoing
- Monthly check-ins
- Quarterly reviews
- Continuous feedback
- Growth opportunities

Managing Ambassador Performance

Ambassador Community

Build community among ambassadors:

Channels:
- Private Slack/Discord for ambassadors only
- Monthly video calls
- Annual ambassador summit

Culture:
- Peer recognition
- Knowledge sharing
- Collaboration on projects
- Genuine friendships

Benefits:
- Networking with peers
- Learning from each other
- Collective voice to company
- Career opportunities

Program Operations

Metrics

Ambassador Program Launch

Phase 1: Design (4 weeks)
- Define program goals
- Structure tiers and benefits
- Create application process
- Build onboarding materials

Phase 2: Seed (4 weeks)
- Invite 10-15 founding ambassadors
- Hand-select top community members
- Iterate on program with feedback

Phase 3: Open (Ongoing)
- Open applications
- Regular cohort intake
- Continuous improvement
- Scale operations

Anti-Patterns

• Ambassador in name only — Badge without real benefits or access
• Too many ambassadors — Dilutes meaning, hard to manage
• No accountability — Accept everyone, expect nothing
• One-way extraction — Take content, give nothing back
• Ignoring ambassadors — Launch program, forget about them
• No community — Ambassadors don't know each other
• Static program — Same benefits forever, no progression
• Heavy-handed requirements — Mandate specific activities, kill authenticity
• Poor offboarding — Inactive ambassadors stay, program credibility suffers
• No feedback loop — Don't ask ambassadors what they want

Community-Led Growth Strategy

Impact: CRITICAL

Community-led growth (CLG) transforms your community from a support channel into a growth engine. Companies with strong communities see 5-25% of revenue influenced by community activities.

Community-Led Growth Motions

CLG vs PLG vs SLG

The Community Growth Funnel

┌─────────────────────────────────────────────────────────┐
│  AWARENESS                                              │
│  ├── Community content ranks in search                  │
│  ├── Member social sharing                              │
│  └── External community reputation                      │
├─────────────────────────────────────────────────────────┤
│  CONSIDERATION                                          │
│  ├── Prospects lurk in community                        │
│  ├── See real user problems solved                      │
│  └── Observe product-market fit in real-time            │
├─────────────────────────────────────────────────────────┤
│  DECISION                                               │
│  ├── Ask questions, get peer answers                    │
│  ├── Social proof from successful users                 │
│  └── Reduced risk through community validation          │
├─────────────────────────────────────────────────────────┤
│  ONBOARDING                                             │
│  ├── Community accelerates time-to-value               │
│  ├── Peer help for common issues                        │
│  └── Templates, examples, best practices                │
├─────────────────────────────────────────────────────────┤
│  RETENTION & EXPANSION                                  │
│  ├── Ongoing value beyond product                       │
│  ├── Feature discovery through peers                    │
│  └── Relationship lock-in                               │
├─────────────────────────────────────────────────────────┤
│  ADVOCACY                                               │
│  ├── Organic referrals                                  │
│  ├── Content creation                                   │
│  └── External speaking, writing                         │
└─────────────────────────────────────────────────────────┘

Community Strategy Canvas

Good Community Strategy

Purpose Statement:
"We're building a community of DevOps engineers who help each other
ship reliable software. Our product is one tool in their toolkit,
but the community serves their broader career and craft."

Value Proposition:
✓ Peer support for complex problems
✓ Career networking and job opportunities
✓ Early access to industry trends and tools
✓ Direct influence on product roadmap
✓ Recognition among peers

Growth Model:
- Content creates SEO discovery
- Free value builds trust
- Engaged members refer peers
- Champions amplify externally

Bad Community Strategy

Purpose Statement:
"We're building a community to reduce support costs
and generate leads for the sales team."

Anti-patterns:
✗ Community is a thinly veiled sales channel
  → Members feel used, leave quickly

✗ Value flows one direction (company → members)
  → No peer-to-peer connection, no stickiness

✗ Success measured only in MQLs
  → Short-term extraction destroys long-term value

✗ No investment in community team
  → Founder does it part-time, community dies

✗ Launch to thousands immediately
  → No core group, no culture, chaos

Community Positioning Framework

Recommendation: Start product-centric, evolve to practice/identity-centric for sustainability.

Building the Initial Core

Phase 1: Founding Members (0-50)
├── Handpick passionate early users
├── 1:1 conversations to understand needs
├── Invite-only, high-touch
└── Establish culture and norms

Phase 2: Early Community (50-500)
├── Open access with curation
├── First community programs
├── Champion identification
└── Early rituals established

Phase 3: Growing Community (500-5,000)
├── Scalable systems required
├── Moderation team needed
├── Sub-communities emerge
└── Governance becomes important

Phase 4: Scaled Community (5,000+)
├── Community runs itself (mostly)
├── Professional community team
├── Ecosystem thinking
└── Multiple touchpoints and programs

CLG Metrics That Matter

CLG Investment Model

Community-Product Integration

Anti-Patterns

• Lead gen disguised as community — Members sense transactional intent, trust dies
• No clear purpose — "Community" without shared identity fails
• Measuring only business metrics — Miss community health, optimize for extraction
• Underinvesting in team — Communities need dedicated attention to thrive
• Scaling before culture — Growth without norms creates chaos
• Ignoring community feedback — Members who feel unheard leave
• Separating community from product — Integration creates network effects
• Expecting immediate ROI — Community compounds; give it 12-18 months