Strategy
Part of A community strategy that connects one member need to staffing, channels and evidence
Community management strategy mistakes to avoid
Explore ten community management strategy mistakes, from platform-first planning to unclear moderation, data collection and measures of success.
Most weak strategies fail before the posting calendar begins. The eight mistakes below concern decisions an English community owner can inspect in a draft plan. They are included because each one breaks the link between a member need and a service the organisation can responsibly operate.
What to take away
- Define activity, access, records, moderation and exit before testing any platform product.
- Engagement measures describe workload but cannot show whether member outcomes improved.
- List daily work, incidents, administration and cover before assuming software replaces labour.
- Set who removes material, how errors are raised and what follows repeated behaviour.
- Trace one person from invitation to outcome, plus a complaint and a departure.
1. Treating an audience as a community
Followers, subscribers and event attendees do not necessarily need to interact with one another. Investigate a shared task and willingness to participate. If broadcast information solves the problem, use it without manufacturing discussion.
2. Starting with the platform
A demonstration can make available features feel like requirements. Define the activity, access, records, moderation and exit first. Then test products, such as Discourse, Circle and Mighty Networks, against that boundary. Otherwise, the service inherits a supplier's assumptions before members have been heard.
Define before choosing a platform
- Define the member activity
- Define access and records
- Define moderation and exit
- Test products against that boundary
3. Promising engagement without an outcome
More posts may indicate useful exchange, confusion, conflict or spam. State what should improve for members and what evidence would distinguish those interpretations. An activity measure can describe workload, but it cannot substitute for quality.
4. Designing only for enthusiastic contributors
Early advocates can explain why participation works for them. They cannot speak for people who stay silent, leave after a poor experience or need an adjustment.
Government Digital Service guidance on finding research participants covers recruiting disabled people and others who may need support. Written for public services, its warning against guessing at their needs applies to commercial research.
5. Hiding labour behind software
Tools do not welcome a nervous member, judge context or obtain an expert answer. List daily work, irregular incidents, administration and cover. A plan that names one community manager but relies on unallocated time from support, legal and product teams is under-resourced.
6. Writing rules without an appeals route
Published standards help members and moderators understand boundaries, but difficult decisions still need context, records and review. Specify who can remove material, how a member raises an error or appeals a decision, and what happens after repeated behaviour. Keep a moderation decision log recording the decision, reason and review. For a service in scope of the Online Safety Act 2023, check the applicable Ofcom guidance and duties before setting the process.
7. Collecting data because the platform permits it
Profile fields, activity scores and integrations can expand the record without improving the member service. The Information Commissioner's Office explains the data minimisation principle: personal data should be adequate, relevant and limited to what is necessary for the purpose. Before enabling a field or export, identify and document a lawful basis under UK GDPR, define a retention period, and establish how to handle subject access requests.
8. Treating launch as the final decision
The early community changes the assumptions. Some activities will need more facilitation, risks will appear in practice and member needs may divide. Schedule a review with evidence, decision rights and stop conditions. Continuous change without an accountable review is not learning; it is drift.
9. Assuming one tone fits every situation
A friendly voice cannot resolve unclear authority. Routine welcomes, technical corrections, rule enforcement and serious incidents need different information and approval. Give operators examples and escalation boundaries rather than a list of brand adjectives. Members benefit more from a clear, timely explanation than from forced cheerfulness during a difficult case.
10. Copying an external benchmark
Participation rates from another platform may use different denominators, audiences and time periods. Build a baseline from the organisation's own defined activity. External examples can suggest questions, but they should not become targets until their method and relevance are known.
Test a strategy draft
Trace one eligible person from invitation to useful outcome, then trace a complaint, an unanswered request and departure. Ask who acts, what information they need and which promise applies. Any gap belongs in the strategy before the delivery plan.
Finally, remove sentences that could describe any online group. A specific plan names the people, job, activity, operating boundary and evidence. If those choices remain vague, a longer document will not make the strategy more credible.
Before you act
- Define the member activity before choosing a platform.
- State what should improve for members and the evidence.
- Recruit participants beyond enthusiastic early contributors.
- List daily work, incidents, administration and cover.
- Set an appeals route for moderation decisions.
- Establish the data purpose before enabling a field.
Common questions
Why is starting with the platform a mistake?
A demonstration can make available features feel like requirements. The article says to define the activity, access, records, moderation and exit first, then test products against that boundary. Otherwise the service inherits a supplier's assumptions before members have been heard.
How should a community measure engagement?
More posts may indicate useful exchange, confusion, conflict or spam. The article says to state what should improve for members and what evidence would distinguish those interpretations. An activity measure can describe workload, but it cannot substitute for quality.
What should a strategy draft be tested against?
Follow one eligible person from invite through to a useful result, then follow a complaint, an ignored request and someone leaving. Check who acts, what they need and which promise applies.
