The Care and Feeding Playbook: How to Build a Community That Lasts
If you read Communities Fail When They’re Treated Like Features, you already know the problem. Treat community like a feature and it will behave like one: temporary. This is the hands-on playbook. This is the stuff you can use tomorrow.
I wrote this from the inside. I was a community manager, a product manager for products discussed on that community before that, and a member as a customer before everything. I made mistakes. The anecdotes below are real. The fixes are practical. Read the story, then use the rules that follows.
Sample moderation policy and escalation matrix
Moderation is infrastructure. It must be visible, consistent, and fair. Below is a compact sample you can adapt.
Core principles
- Safety first. No tolerance for abuse, harassment, or hate.
- Transparency. Publish rules and enforcement outcomes.
- Proportionality. Sanctions should match the offense.
- Appeals. Provide a clear path to appeal decisions.
Sample rules (short bullets)
- Be respectful. No personal attacks.
- No hate speech or harassment.
- No doxxing or sharing private information.
- No spam or blatant self-promotion.
- Follow posting guidelines for product-specific forums.
Escalation matrix
| Level | Action | Duration | Who acts |
|---|---|---|---|
| 1 | Warning | Immediate | Moderator |
| 2 | Temporary suspension | 7 days | Senior moderator |
| 3 | Extended suspension | 30 days | Community manager |
| 4 | Ban | Permanent | Community manager + legal |
| Appeal | Review request | 14 days | Appeals panel |
Notes on implementation
- Train volunteer moderators or community champions on the matrix and provide scripts for common situations.
- Keep a private log of enforcement actions. Use it to spot repeat offenders.
- Publish a quarterly moderation summary with anonymized stats.
Staffing model and cadence
Communities need a dedicated steward and embedded partners. Each organization should have a community manager whose role is to act as the Product Manager for community. It should not be an additional responsibility added to another role.
Recommended roles & partnerships
- Community Manager. Full-time owner of community health.
- Product liaisons. Rotating PMs and dev leads who monitor forums.
- Volunteer moderators. Trusted members with limited powers.
- Executive sponsor. An EVP or C-level sponsor who reviews health quarterly.
Suggested cadence
- Weekly: moderation queue review and community highlights.
- Monthly: product liaison sync and advocate recognition.
- Quarterly: community health audit and executive review.
- Annual: advocate summit and roadmap alignment.
Scaling rule of thumb Start with one full-time community manager for the first active members, then scale as peer resolution and support deflection grow. Adjust based on support deflection and advocate workload. Note that this rule of thumb only works if you have a single forum/discussion board. Check in with the community managers repeatedly.
Metrics dashboard and how to read it
Track trends, not snapshots. Tie metrics to dollars when you can. Attribution can be tricky, so be sure to have a good mechanism for tracking interest from the community through to the dollars.
Key metrics and definitions
- Peer Resolution Rate: percent of questions answered by members.
- Advocate Retention: percent of early advocates active at 6 and 12 months.
- Feature Idea Conversion: number of community-sourced ideas that reach roadmap or prototype.
- Response Time to First Helpful Reply: median time to a useful answer.
- NPS Lift Among Members: difference in NPS between members and non-members.
- Support Deflection: tickets avoided because of community help.
How to present to execs
- Show month-over-month deltas. Momentum matters.
- Translate support deflection into cost savings. Use average ticket cost times deflected tickets.
- Highlight advocate retention as a retention lever. Losing advocates predicts churn in engagement.
- Use feature idea conversion to show product responsiveness and innovation sourced from community.
Sample dashboard tiles
- Peer Resolution Rate: 72% (MoM +3%)
- Advocate Retention 6mo: 84% (MoM -1%)
- FR Conversion: 6 ideas to prototype this quarter
- Median Response Time: 18 hours (goal < 48 hours)
- Support Deflection: 1,200 tickets avoided this quarter
Refresh and 90-day checklist
If you already have a community, but you need to inject some positive momentum, consider a refresh (visual, organizational, anything) and treat it like a product launch. If you don’t already have a community, this can be used as your launch+90 template.
Before refresh/launch
- Hire a community manager.
- Recruit initial advocates and beta testers.
- Publish guidelines and moderation policy.
- Define KPIs and dashboards.
First 30 days
- Run advocate onboarding.
- Start weekly moderation reviews.
- Launch a small program to create reasons to return.
30 to 90 days
- Automate no-activity reports and route to PMs.
- Run first contest or gamification pilot.
- Hold first product liaison sync.
- Measure early peer resolution and response time.
90-day review
- Audit community health metrics.
- Present results to executive sponsor.
- Iterate on onboarding, moderation, and programming.
That’s it. Those are my recommendations. I could provide more, but this is more than enough to chew on for anyone thinking about building up a community.