community-manager

Overview

Communities turn customers into advocates: places (forums, Slack/Discord, social groups) where members help each other, share wins, and deepen their relationship with your brand. This skill covers community strategy, launch, daily engagement, moderation, advocacy programs, and measuring community impact on the business.

When to use

• Launching a brand community

• Reviving a dead forum or group

• Designing engagement programs

• Writing moderation guidelines

• Building customer advocacy (reviews, referrals, case studies)

• Measuring community ROI

• Launching a user community from zero

• Turning power users into advocates

• Managing community crisis or backlash

Core concepts

Community purpose. Define the member's reason to join in their words: "get answers fast," "learn from peers," "network with people like me." Communities built around the brand's needs (not members') die.

Platform choice. Match where your audience already gathers: developers → Discord/forum; professionals → Slack/LinkedIn group; consumers → Facebook group/Discord; async knowledge → forum. Don't fight existing habits.

The engagement ladder. Lurker → contributor → regular → leader/advocate. Design for each rung: easy first actions (introduce yourself), recognition for contributors (badges, spotlights), responsibility for leaders (moderator roles, advisory board).

Seed and rituals. New communities need seeded activity (team + founding members posting daily) and rituals (weekly threads, monthly events, AMAs) that create habit. Empty rooms stay empty.

Moderation. Clear guidelines (published, enforced consistently), graduated response (warn → mute → ban), fast response to conflict, and transparency about decisions. Protect the culture early — toxic members drive out good ones.

Advocacy. Identify happy, active members; invite them into advocacy: reviews, testimonials, referrals, beta testing, speaking. Reward with access and recognition, not just swag.

The 90-9-1 rule. 90% lurk, 9% contribute occasionally, 1% create most content. Design for all three: lurkers need great reading experiences, occasional contributors need low-friction prompts, creators need recognition and tools. Trying to convert lurkers into posters usually fails — serve them where they are. Member journey. Newcomer (confused, needs orientation) → explorer (browsing, needs discovery) → participant (posting, needs feedback) → leader (organizing, needs authority and recognition). Design touchpoints for each stage: welcome sequences, discovery prompts, feedback rituals, leadership pathways. Communities die when the journey stalls at newcomer. Advocacy programs. Identify power users → invite to formal advocacy (early access, advisory boards, speaking opportunities) → equip with content and swag → recognize publicly → measure their influence (referrals, content, support deflection). Advocates are your most credible marketers — invest in them like a channel.

Practical workflow

1. Define strategy. Purpose (member-first), audience, platform, success metrics (active members, response time, support deflection, advocacy actions, retention lift). Get executive sponsorship — communities need patience.
2. Build the foundation. Platform setup, categories/channels, guidelines, welcome flow (onboarding that gets a first post within 24h), seed content (FAQs, starter discussions).
3. Recruit founding members. 50–100 ideal members personally invited: best customers, friendly prospects, internal experts. Their early activity sets the culture.
4. Launch and seed. 30–60 days of deliberate daily activity: team posts, questions, AMAs, events. Personally welcome every new member. Respond to every post quickly — early responsiveness trains participation.
5. Build rituals and programs. Weekly themed threads, monthly events/challenges, recognition programs (member of the month, contributor badges), advocacy invitations for top members.
6. Moderate consistently. Enforce guidelines fairly, address conflict fast, remove bad actors without drama, publish transparency updates when rules change.
7. Measure and report. Active members (not just signups), posts per active member, median response time, % questions answered by members (deflection), NPS of members vs. non-members, advocacy actions, retention comparison.

Welcome flow: personal greeting → "introduce yourself" prompt → guided tour of key areas → first-week check-in → invitation to first ritual/event.

Community health dashboard (review monthly): active members (posted in last 30 days) → new member activation rate (% who post within 7 days of joining) → response time (median time to first reply) → power-user ratio (% of members creating 80% of content) → sentiment trend (sample 50 posts/quarter) → churn (members going silent). Declining activation is the earliest warning sign — fix onboarding before anything else.

Rituals that build belonging: weekly welcome threads, monthly AMAs or challenges, member spotlights, annual awards, and traditions only insiders understand. Rituals turn a user base into a community.

Weekly community ops: Monday: plan week's rituals and prompts → daily: moderate, respond, seed discussions → Wednesday: member spotlight → Friday: week-in-review digest + metrics check. Consistency of presence matters more than brilliance — members return to communities that feel alive. Crisis playbook: acknowledge quickly (silence reads as guilt) → move detailed discussion to a dedicated channel → state what you know and what you are doing → follow up with resolution → retrospective with moderators. Communities forgive mistakes; they do not forgive cover-ups.

Common pitfalls

• Brand-centric purpose. "A place to talk about our product" isn't compelling. Center member needs.
• Launching to crickets. No founding members, no seeded content. Recruit before you launch.
• Inconsistent moderation. Enforcing rules selectively destroys trust. Clear rules, fairly applied.
• Metric vanity. Celebrating member counts while engagement is zero. Measure activity and value.
• Abandoning the community. Launching with fanfare, then going quiet. Communities need sustained presence.
• Over-moderation. Deleting legitimate criticism. Handle complaints transparently — it builds trust.
• No business linkage. Running a community without connecting it to retention, support deflection, or advocacy. Prove value or lose budget.
• Over-moderation. Deleting criticism or dissent kills trust. Moderate behavior (abuse, spam), not opinions — and be transparent about the line.
• Founder-as-only-voice. Communities built on one personality collapse when that person is busy. Cultivate member leaders deliberately.
• Metric vanity. Celebrating member counts while engagement collapses. Active contributors and response times are the real health metrics.
• Corporate voice. Posting like a press release in a human space. Communities need human voices — preferably named humans, not brand accounts.
• Neglecting lurkers. Optimizing only for posters. Lurkers are future customers and advocates — the reading experience is the product for 90% of members.