Communities Fail When They’re Treated Like Features
Let’s be blunt: building a community and checking boxes look the same on a roadmap. Both get resources assigned, both get line items, both can be marked “done.” But they are not the same thing.
A community is a living system. It grows, it needs food, it gets sick, and it thrives when people care for it. Treat it like a feature – something you ship, measure by a single metric, and forget – and it will behave like a feature: temporary, brittle, and ultimately useless.
I’m a pseudo-active member of at least six online vendor communities. I’ve seen the good and the bad from the customer-side, but there was only one where I got a unique perspective. Most of my anecdotes and recommendations will come from my experience on THWACK, but that community is not unique to the problems I see among online communities.
I’ve made mistakes. Communities make mistakes. Organizations make mistakes. It’s important that we learned from them. That’s kind of the point: communities are messy, human things. They need stewardship, not governance via checkboxes.
All names, likenesses, and links have been changed to protect the innocent.
If you’re an EVP or C‑suite leader reading this, here are three executive moves that actually matter:
- Name a leader and fund them.
Community needs a steward with time and budget, not a side-of-desk owner. - Measure the right things.
Monthly Active Users (MAU) is a headline; peer resolution, advocate retention, and feature/idea conversion are the signals that matter. - Protect trust.
Don’t treat the community as a cold lead pool. If members feel exploited, they leave and all their social capital goes with them.
Below: what I saw, what I learned, and the practical fixes that followed.
What a Healthy Community Looks Like (and Why Advocates Matter)
What I saw
When I first got involved, THWACK was noisy in the best way: members were answering each other’s questions, there were openings to get on UX calls, product managers were in the mix, beta testers were being screened, and members shared the things they built. That energy became the norm. People helped each other, and advocates emerged naturally.
What I learned
New members and advocates are the oxygen of a community. They set the tone, answer questions, bicker over feature requests, and (ultimately) model behavior. If you lose them, you don’t just lose posts. You end up losing the culture that made the community useful.
Tactical takeaway for leaders
Spot the keystone members early. Give them recognition, early access, and a small budget for experiments. Treat them like partners, not data points.
Four ways vendors (and community teams) accidentally kill communities — and how to fix them
Below are four recurring patterns I saw, each followed by the practical fix we used or should have used. I’m not pointing fingers: I was part of the team that lived through these, so I own my share of the blame.
Screaming into the void
What I saw: A feature request submitted in February 2017 gathered over 1,300 upvotes by 2021. Status: still “open.” No product replies. Members felt ignored.
Why it matters: Votes without visible movement become a trust tax. People stop believing their input matters.
Fix: Track FR signals. Votes are important, but they don’t exist in a vacuum. Track month‑over‑month deltas to spot surges. Make statuses meaningful: “under review,” “on the roadmap,” “in design,” or “won’t fix,” and update them. Make FR reviews a regular part of vNext planning for PMs. Even a short update (“we’re evaluating tradeoffs”) keeps trust intact.
The lingering silence
What I saw: Small communities can be kept alive by a few people. Eventually, you’ll need to support multiple products or split forums. Questions go unanswered for weeks. Members post “anyone?” after 30 days.
Why it matters: Silence signals neglect. It kills participation faster than bad UX.
Fix: Make participation a responsibility for PMs and dev leads — not to answer every question instantly, but to monitor and engage. Automate a “no activity” report: flag posts with zero replies after X days (7 days is a good starting point for small communities) and route them to the responsible product owner. Use platform features like “suggested” and “verified” answers to let the community self‑police while keeping product teams visible.
Everything reads like marketing
What I saw: New posts felt like campaigns: buy, upgrade, license more. Honest replies went unanswered. Members stopped returning.
Why it matters: Communities are two‑way streets. If every lane is a billboard, people stop driving through.
Fix: Give people reasons to come back that aren’t transactional. Run contests, gamify helpful behavior, offer branded swag for top contributors, and fund member‑led events. The organization pays; members build. That’s how you turn users into fans.
Change without management
What I saw: We archived forums, renamed products, and reorganized menus — sometimes without warning. Participation dipped. People said “the community isn’t worth it anymore.”
Why it matters: Members treat the community like a neighborhood. You don’t move the park overnight without telling people.
Fix: Announce early and often. Beta test changes with community champions. Provide migration guides and a clear timeline. Monitor activity after the change and be ready to iterate.
A sidebar on moderation:
zero tolerance for abuse, consistent enforcement
When abuse or intolerance is tolerated or when enforcement is inconsistent), tone degrades and people leave. Moderation isn’t a “nice to have.” It’s infrastructure.
Practical rules: publish clear community guidelines, train volunteer moderators or appoint community champions, create an escalation matrix (warning → temporary suspension → ban), and publish periodic moderation summaries so members see that rules are enforced fairly.
Quick executive checklist
- Hire a named community lead with budget and expectations, not KPIs (to start). Let them translate how business needs convert to community KPIs.
- Require product participation (structured, not reactive).
- Track the right metrics: peer resolution, advocate participation/retention, feature request conversion, response time, NPS lift, support deflection.
- Never use the community as a cold lead pool. Consent first.
- Make moderation visible and consistent.
Communities need care, not checkboxes. If you want someone to help you stop the slow leak and start building real momentum, I can help. I’ll consult, audit your metrics, or help design an advocate program that actually works. The follow-up to this drops tomorrow and it is the hands-on playbook: checklists, sample moderation rules, and the dashboard you should be showing to your execs.
