community-strategy

name	community-strategy
description	Build and grow brand communities that drive engagement, retention, and advocacy. Use when launching or scaling community programs.
origin	ECM

Community Strategy

When to Activate

Use this skill when launching a new brand community, scaling an existing community, choosing a community platform, designing engagement programs, measuring community health, building a community team, integrating community into the marketing funnel, or when someone asks to "build a community" or "increase customer engagement." Also activate when community-led growth is part of the business strategy or when retention and advocacy are key priorities.

First Questions

Before building or optimizing a community, clarify:

1. What is the business goal? (retention, support cost reduction, product feedback, brand advocacy, lead generation, content creation)
2. Who is the community for? (customers, prospects, practitioners, developers, fans — be specific)
3. What value will members get? (knowledge, networking, recognition, access, support, entertainment)
4. What existing community activity exists? (social media groups, forums, Slack channels, Reddit threads — even informal ones)
5. What resources are available? (dedicated community manager, budget, executive sponsorship, content team support)
6. What is the timeline? (community building is a long game — expect 6-12 months to meaningful traction)

Core Rules

1. Community is not a channel — it's a strategy. A community is not another place to broadcast marketing messages. It's an ecosystem where members create value for each other, with the brand as facilitator.
2. Value before extraction. Give before you ask. A community that only serves the brand's interests will die. Members must receive clear, tangible value for their participation.
3. Start small and intentional. Launch with 20-50 handpicked members who represent your ideal community member. Grow deliberately, not virally. Quality of early members determines community culture.
4. Culture is set in the first 30 days. The norms established by early members become the community's identity. Be extremely intentional about who you invite first and what behavior you model.
5. Community managers are the most important hire. A community without active management becomes a ghost town or a toxic space. Never launch a community without a dedicated human.
6. Measure engagement depth, not member count. 500 active members beat 5,000 lurkers. Focus on meaningful interactions, not vanity metrics.

Community Types

Type	Purpose	Example	Best Platform
Support community	Peer-to-peer help, reduce support costs	Salesforce Trailblazer Community	Forum, Discourse
Product community	Feature requests, beta testing, feedback	Figma Community, Notion templates	Slack, Discord, dedicated platform
Brand community	Loyalty, identity, lifestyle connection	Harley Owners Group, Peloton	Facebook Groups, app-based
Professional community	Skill development, networking, career growth	Superpath (content marketing), Pavilion	Slack, Circle, LinkedIn Groups
Interest community	Shared passion or hobby, brand-adjacent	Patagonia environmental activism	Reddit, Discord, Facebook Groups

Platform Selection

Decision Framework

Factor	Discord	Slack	Facebook Groups	Circle	Reddit	Forum (Discourse)
Real-time chat	Excellent	Excellent	Limited	Good	Limited	Limited
Async discussion	Good	Poor (messages disappear)	Good	Excellent	Excellent	Excellent
Content organization	Channels + threads	Channels + threads	Post feed	Spaces + threads	Subreddits + threads	Categories + threads
Discovery / SEO	None	None	Moderate (Facebook search)	Limited	Excellent	Excellent
Moderation tools	Strong	Basic	Strong	Moderate	Strong	Excellent
Cost	Free	Free (limited) / Paid	Free	Paid ($39+/mo)	Free	Free (self-hosted) / Paid
Best for	Gaming, dev, young audiences	B2B, professional	B2C, mainstream	Creators, courses, SaaS	Enthusiasts, large-scale	Support, knowledge base
Ownership of data	No	No	No	Yes	No	Yes (self-hosted)

Selection Criteria

1. Where does your audience already hang out? Don't force them to a new platform.
2. Real-time or async? Real-time communities require more moderation but feel more alive. Async communities are better for thoughtful discussion and knowledge building.
3. Data ownership: If community is a strategic asset, own the platform (Circle, Discourse) rather than renting (Slack, Facebook).
4. SEO value: If community content should be discoverable, choose a platform that's indexable (Discourse, Reddit).
5. Integration needs: Does the community need to connect to your product, CRM, or analytics tools?

Community Flywheel

The self-reinforcing cycle that makes communities grow:

Attract

Draw in potential members through:

• Content marketing that demonstrates community value
• Social proof (member count, testimonials, activity screenshots)
• Referral programs (existing members invite peers)
• Gated content or events exclusive to community members
• Partnership with influencers who join and participate

Engage

Activate new members into participants:

• Welcome experience (personal DM, intro thread, orientation)
• Regular programming (weekly threads, AMAs, challenges)
• Prompt responses to questions (under 4 hours)
• Recognition of contributions (shoutouts, badges, features)
• Content that sparks discussion, not just consumption

Activate

Convert participants into contributors:

• Ask for their expertise (answer a question, share their experience)
• Create structured roles (mentors, ambassadors, moderators)
• Give them ownership of initiatives (host an event, lead a thread)
• Provide exclusive access (beta features, founder access, early content)
• Celebrate their contributions publicly

Advocate

Empower contributors to become champions:

• Equip them with shareable content and referral tools
• Feature them in marketing materials (case studies, guest posts, podcasts)
• Create an ambassador or champion program with perks
• Give them a platform (speaking slots, co-created content)
• Connect them with each other (champions build relationships that stick)

Community Roles

Understanding member segmentation is critical for programming:

Role	% of Community	Behavior	Strategy
Lurkers	60-70%	Read but never post	Make it easy to consume. Don't pressure them — they're still getting value. Periodically invite participation with low-barrier prompts.
Participants	20-25%	Occasionally post, react, or comment	Recognize their contributions. Tag them in relevant discussions. Make them feel seen.
Contributors	5-10%	Regularly create posts, answer questions, share resources	Give them special access and recognition. Feature their expertise. Ask for feedback on community direction.
Champions	1-3%	Actively recruit members, moderate, lead initiatives, defend the community	Formalize their role. Give them tools, perks, and status. Treat them as partners, not users.

Onboarding New Members

The first 48 hours determine whether a member becomes active or disappears.

Onboarding Sequence

1. Welcome message (automated, immediate): Welcome them by name, explain what the community is, point to 2-3 things to do first.
2. Introduction prompt (within first hour): Direct them to an intro thread. Provide a template: "Introduce yourself — name, role, what you're working on, one thing you hope to learn here."
3. Personal DM from community manager (within 24 hours): "Hey [Name], welcome! I saw your intro — [personal comment]. If you're interested in [topic], check out [specific thread]. Don't hesitate to ping me if you need anything."
4. First engagement prompt (within 48 hours): Tag them in a relevant discussion or ask a low-barrier question they can answer based on their intro.
5. First week check-in (Day 7): "How's your first week been? Anything you wish was different or are looking for?"

Onboarding Checklist

• Welcome message sent immediately upon joining
• New member pointed to community guidelines
• Introduction posted in intro channel/thread
• At least one personal interaction from a community manager
• Tagged in at least one relevant conversation
• First-week check-in completed

Engagement Programs

Recurring Programs

Program	Frequency	Description	Engagement Level
Weekly discussion thread	Weekly	Themed prompt that invites opinions and experiences	Low barrier
AMA (Ask Me Anything)	Monthly	Expert guest answers community questions live	Medium
Challenge / Sprint	Monthly or quarterly	Structured activity with a goal and deadline	High commitment
Member spotlight	Bi-weekly	Feature a community member's work, story, or expertise	Recognition
Resource share	Weekly	Members share articles, tools, templates they've found useful	Low barrier
Feedback round	Monthly	Share something in-progress for community critique	Medium
Virtual meetup / social	Monthly	Informal video call for networking and relationship building	Medium
Annual event	Yearly	Conference, summit, or retreat (virtual or in-person)	High

Engagement Best Practices

• Ask questions, don't make statements. "What's working for you in Q1?" generates discussion. "Here's our Q1 update" generates silence.
• Respond to every post in the early days. Once the community is self-sustaining, shift to responding strategically.
• Create traditions. "Monday Wins" or "Friday Fails" become rituals people look forward to.
• Use polls and surveys. Low-effort participation builds the habit of engaging.
• Seasonal and cultural moments. Tie programming to industry events, holidays, or trending topics.

Community Metrics

Engagement Metrics

• Daily/Weekly Active Members (DAM/WAM): Members who perform at least one action (post, comment, react) per day/week.
• Engagement Rate: (Active members / Total members) x 100. Healthy: 20-30% monthly, 5-10% daily.
• Posts per Active Member: Content creation density. Healthy: 2-5 posts per active member per month.
• Response Rate: % of questions that receive at least one response. Target: 95%+.
• Time to First Response: How quickly questions get answered. Target: under 4 hours.

Growth Metrics

• Net Member Growth: New members minus churned members per period.
• Invite Rate: % of members who invite at least one new person. Healthy: 5-10%.
• Activation Rate: % of new members who post within 7 days. Target: 30-50%.
• Retention Rate: % of members active in month 1 who are still active in month 3. Target: 40-60%.

Business Impact Metrics

• Support Deflection: % of support questions answered by community vs. support team.
• NPS / CSAT: Community members vs. non-community members.
• Retention Lift: Churn rate of community members vs. non-members.
• Revenue Influence: Deals where community participation was a touchpoint.
• Content Generated: User-generated content, templates, guides created by members.
• Product Feedback: Feature requests, bug reports, and beta test participation from community.

Community-Led Growth

When community becomes a growth engine:

Content Flywheel

Members create content (questions, answers, templates, tutorials) that gets indexed by search engines, drives organic traffic, and attracts new members who then create more content.

Referral Engine

Happy community members invite peers. Each new member increases the value of the community for existing members (network effect). Amplify with referral programs and ambassador perks.

Product-Community Loop

Community feedback shapes the product. Better product creates happier community members. Happier members become advocates. Advocates attract new customers who join the community.

Trust Accelerator

Prospects who see an active community of peers trust the brand faster. Community threads serve as extended social proof. Prospective customers can ask real users questions before buying.

Community Team Structure

Minimum Viable Team (0-1,000 members)

• 1 Community Manager (full-time): Day-to-day engagement, moderation, member relations, content programming, metrics.

Growth Team (1,000-10,000 members)

• 1 Community Lead: Strategy, partnerships, programs, stakeholder management.
• 1-2 Community Managers: Daily operations, moderation, member support.
• Part-time content support: Create community content, repurpose member content.

Scale Team (10,000+ members)

• Head of Community: Strategy, budget, executive reporting.
• 2-4 Community Managers: Segment-specific or geography-specific management.
• Community Programs Manager: Events, challenges, ambassador program.
• Content/Social Manager: Amplify community content across channels.
• Data Analyst: Metrics, member health scoring, reporting.

Community Launch Checklist

Pre-Launch (4-6 weeks before)

• Community purpose and value proposition defined
• Target audience and founding member list identified (20-50 people)
• Platform selected and configured
• Community guidelines written
• Channel/space structure designed (start with fewer channels — expand later)
• Welcome sequence and onboarding flow built
• First 2 weeks of content and programming planned
• Community manager identified and prepared
• Success metrics and reporting cadence defined
• Executive sponsor aligned

Launch Week

• Personal invitations sent to founding members (not a mass email — individual outreach)
• Community manager actively welcoming every new member
• First programmed event or discussion live
• At least 5-10 seed posts/threads to prevent "empty room" syndrome
• Feedback collected from early members after Day 3 and Day 7

Post-Launch (First 90 days)

• Weekly engagement programming running consistently
• Monthly metrics review established
• First AMA or guest event hosted
• Member feedback collected and acted on (at least one visible change based on feedback)
• Champion/ambassador candidates identified
• Community integrated into marketing channels (mentioned in emails, website, social)
• First case study or success story from a community member

Community Content Calendar Template

Week	Monday	Wednesday	Friday
1	Discussion prompt: "[Topic] — what's your take?"	Resource share: "Tools we love this week"	Member spotlight: Feature a contributor
2	Challenge launch: "Try [X] this week and share results"	AMA announcement + question collection	Casual thread: "What are you working on this weekend?"
3	Discussion prompt: "[Industry trend] — opportunity or hype?"	Guest expert Q&A	Week in review: Top threads and insights
4	Challenge results + celebration	Product/feature discussion	Monthly retrospective + what's coming next month

Quality Gate

Before launching or recommending a community strategy:

• The community purpose is clearly defined and distinct from a support channel or marketing newsletter
• The target audience is specific (not "everyone who uses our product")
• The value proposition for members is articulated (what they get, not what the brand gets)
• A platform has been selected based on audience behavior, not internal preference
• A founding member list of 20-50 ideal members has been identified
• Community guidelines exist and set clear expectations
• An onboarding sequence is designed for new members
• At least 4 weeks of engagement programming is planned
• A dedicated community manager is assigned (not a side project for the marketing intern)
• Success metrics are defined with realistic targets
• Executive sponsorship is secured (community needs 6-12 months to show ROI)
• The community is integrated into the broader marketing strategy (not operating in isolation)