Community Launch
Deciding whether to merge, redesign or close a community
Compare merge, redesign and closure against member need, operating capacity and transition risks, then give open questions a clear handoff.
Choose between merging, redesigning and closing a community by checking whether members still need the exchange it promised and whether the organisation can support it responsibly. A quiet space warrants investigation; a harmful or repeatedly unattended space may need a faster decision. Record the effect on members before choosing an option.
Diagnose what is failing
Read recent questions, unresolved cases and member feedback. Ask whether the need has disappeared, the format makes participation difficult, members are split across spaces or the team cannot provide the response it promised. Review operating cost and work still waiting for an owner. Check whether people benefit by reading before treating a low post count as failure.
State the problem plainly. “Members ask the same setup question in two places and staff answer it twice” suggests a different decision from “Members cannot safely discuss account details in either place”. The first may support a merge; the second may call for a private support route.
| Option | It may fit when | Condition to check before committing |
|---|---|---|
| Merge | Two spaces serve substantially the same people and task, and one home would make answers easier to find | Members can reach the new home; permissions, history and ownership can be handled. |
| Redesign | The need remains, but navigation, format, staffing or response rules block useful exchange | The team has a specific change it can resource and evaluate. |
| Close | The need has ended, the space cannot be supported safely or another route can meet it better | Members have a usable route for open questions and material worth preserving. |
These are decision conditions, not automatic thresholds. A merge can import duplicate content and confusing access rules. A redesign can consume more staff time. Closure can strand someone relying on an answer.
Test a bounded change when it can answer the question
If the problem is uncertain and immediate risk is controlled, try a bounded change before a permanent move. Assign an owner, explain the change to members and choose evidence of improvement: more questions receiving usable answers, fewer repeated handoffs or less time maintaining duplicate discussions. Set a review date that lets members use the new route. Initial replies to an announcement do not establish success.
Where a serious conduct, privacy or safety issue is ongoing, follow the organisation’s incident process and limit further harm promptly. A redesign trial does not replace action on exposed private details or an unattended report.
Plan the transition around members
For a merge, choose the current home, decide who can see each discussion and plan how older answers will be labelled or corrected. Check what can actually be moved before promising that posts, accounts or permissions will transfer intact. Give members one clear route for new questions and a way to flag missing material.
For a redesign, say what changes, which problem it addresses and where members can report a difficulty. Keep an owner for old open questions. For closure, stop inviting new activity, identify unresolved requests and give each a handoff.
Tell members what will remain readable, for how long under the approved plan, and where they can get help afterwards. Do not present an archive as current guidance without someone responsible for its accuracy.
Review personal information in posts, exports and backups during the transition. For an organisation covered by the Australian Privacy Principles, APP 11 requires reasonable steps to protect personal information it holds and, subject to exceptions, to destroy or de-identify it when no longer needed for a permitted purpose.
Closure alone does not settle what must be retained or removed; the organisation needs a decision based on its records and circumstances.
Australian Privacy Principle (APP) 11 – Security of Personal Information
- RequirementOrganisations must take reasonable steps to protect personal information they hold
- When no longer neededPersonal information must be destroyed or de-identified, unless an exception applies
- Relevance to community transitionsClosure does not automatically mean data is disposed of—organisations must assess retention needs based on records and circumstances
Record the decision and check the handoff
Record the member need, options considered, evidence, cost and risk of each option, chosen owner and review point. After a merge or redesign, check through the intended member access route that people can find the promised destination and open cases have owners. After closure, confirm that notices, support handoffs and approved record actions are complete. Members should know where their next question belongs.
