Community engagement

Community Engagement

Traffic without engagement is a leaky bucket. Developers join products when they see real people having real conversations — not an empty forum and a bot saying "welcome." This skill turns sign-ups into active members who come back, invite peers, and give feedback.

Chains from [[growth-strategy]] (ICP, channels) and [[social-distribution]] (drive people in). Feeds [[content-marketing]] with user stories and [[growth-strategy]] with qualitative insights.

When to Use

• Community space is empty or quiet (Discord, Slack, forum, in-app feed)
• Need welcome/onboarding for new members
• Planning an AMA, office hours, or engagement challenge
• Collecting user feedback and testimonials
• Moderation guidelines and community rules
• Turning lurkers into contributors

Skip when the product has no community surface yet — define one first or use [[social-distribution]] for audience-only channels.

Process

1. Define the community home

Pick one primary home (don't split early):

Surface	Best when
In-app feed / profiles	Product IS the network (e.g. developer-connection)
Discord	Real-time chat, events, support
Slack	B2B teams, private beta
GitHub Discussions	Open-source, technical Q&A
Forum (Discourse)	Long-form threads, searchable archive

Document:

• URL / invite link
• Purpose — support, networking, feedback, showcase
• Who it's for — same ICP as [[growth-strategy]]
• Success metric — DAU, posts/week, % new users who post within 7 days

2. Community rules and tone

Write short, clear rules:

1. Be respectful — no harassment, spam, or unsolicited DMs for sales
2. Stay on topic — dev networking, careers, collaboration (adjust to product)
3. No pure self-promo — share work in designated channels
4. Help others before asking — give value first
5. Report problems to mods — don't flame

Tone: Welcoming, peer-to-peer, moderator light-touch. Developers hate corporate-speak in community spaces.

Pin rules in the primary channel. Add #introductions, #help, #showcase (or equivalents).

3. Welcome and activation flow

New member journey:

Sign up → Welcome message (email + in-app)
       → Profile prompt ("Add stack, goal, location")
       → Suggested first action ("Introduce yourself" / "Find 1 connection")
       → Day 1 nudge if inactive
       → Day 7 check-in with tip or event invite

Draft copy for each touchpoint. First action within 24h is the activation metric.

For developer-connection products specifically:

• Prompt: "What are you building or learning?"
• Prompt: "Who would you like to meet — mentor, collaborator, hiring manager?"
• Suggest 3 profiles to connect with (algorithm or manual curation early on)

4. Engagement programming (weekly rhythm)

Plan recurring activities:

Activity	Frequency	Goal
Introduction thread	Weekly	Lower barrier to first post
AMA / office hours	Bi-weekly	Expert draw + live engagement
Showcase Friday	Weekly	User-generated content
Challenge ("Connect with 3 devs this week")	Monthly	Activation
Feedback thread	Monthly	Product input + feeling heard

Calendar 4 weeks ahead. Assign facilitator (you or power user).

5. Seed content — don't launch empty

Before driving traffic:

• 10+ seed posts (team + friendly beta users) — intros, tips, questions
• 3 showcase examples — projects, career wins
• 1 pinned "Start here" guide — how to get value in 5 minutes
• Mods identified — response SLA ≤4h in launch week

Empty communities die on first visit. Seed authentically — real team intros, not fake personas.

6. Outreach to existing communities

Don't spam. Add value first:

1. Identify 5 communities where ICP already gathers (subreddits, Discords, Slack groups)
2. Participate genuinely for 1–2 weeks before mentioning product
3. Share useful content (from [[content-marketing]]) without link first; link when relevant
4. Offer exclusive invite or early access to community members
5. Partner with micro-influencers (dev YouTubers, newsletter authors) for co-events

Track which communities convert — double down on two, drop the rest.

7. Feedback → product loop

Weekly community digest for product team:

• Top 3 questions asked (→ FAQ, docs, or feature)
• Top 3 pain points (→ backlog input for product-manager)
• Wins / testimonials (→ [[content-marketing]] case studies)
• Churn signals — "why I left" threads, inactive cohorts

Use [[decision-docs]] if community feedback drives product decisions.

8. Moderation and crisis

• Spam — warn → remove → ban; document pattern
• Heated debates — redirect to DMs; don't pick sides in public
• Bug reports in community — acknowledge, link to status, route to support
• Negative viral post — respond once publicly with facts + invite to DM; don't dogpile

Common Rationalizations

• "Build it and they will come" — Empty community + ads = bounce. Seed first.
• "We don't need rules yet" — Small communities go toxic fast without norms.
• "Engagement is marketing's job only" — Founders and engineers must show up early.
• "More members = success" — Active members matter; 100 engaged beats 10k lurkers.

Red Flags

• Zero posts in 7 days after launch push
• Only team members posting
• New users never complete profile or first connection
• Promo spam unchecked
• Feedback collected but never acknowledged
• Community link broken or invite expired in marketing posts

Verification

Community work is done when:

• Primary community home defined with purpose and metric
• Rules pinned; channels structured (#intro, #help, #showcase)
• Welcome + Day 1 + Day 7 flows drafted
• 4-week engagement calendar with activities
• Seed content plan (10+ posts) executed or scheduled
• Outreach list of 5 external communities with participation plan
• Weekly feedback digest template ready for product team