How to Split a Large Discord Community Into Smaller Groups: A Map of What Breaks at Each Size

Find the group first, then build its room

A small community runs well on one main chat, and a larger one outgrows it. The chat speeds up until nobody can follow it, members with a shared interest lose each other in the scroll, and the regulars who gave the room its character post less and less. Breaking the community into smaller interest groups solves this on one condition: the group has to exist in the chat already. A channel created for a group that the team hopes will form stays empty.

The whole method fits in one line of work. Spot a topic that the same members keep bringing up, hand those members a channel and a host chosen from among them, and decide in advance when you will check whether the channel is still alive.

Some terms, defined once:

Channel is a room in a server. It appears in the sidebar with a hash before its name.

Role is a label attached to a member. It can control which channels they see, and staff can notify every holder of a role together.

Thread is a titled side discussion attached to a channel.

Onboarding is the join flow Discord offers Community servers. New members answer multiple choice questions, and their answers can assign roles and channels.

Subgroup means an interest group inside a single server: one channel, one role, one host.

The needs of a server shift as it gets bigger, and I plan around four rough sizes: about 100 members, about 1,000, about 10,000 and about 100,000. They are markers for planning, and a given server may meet each problem sooner or later than the number says.

Stage one, about 100 members: leave it as one chat

Everybody in a server this size recognizes everybody else. Someone posts about a narrow interest, the handful of people who share it reply in the main chat, and the rest of the room reads along happily. No problem exists here that a subgroup would solve.

What is worth doing is keeping a weekly note of topics that came up more than once, with the names of the members who raised them. A few minutes a week is enough. When the server reaches the next stage, that note tells you which groups are real. Teams that skip it end up guessing, and a guessed group is usually an empty one.

Stage two, about 1,000 members: the chat outruns its readers

The failure at this size is easy to miss, because a fast chat looks like a healthy one to the team running it.

From a member's side it looks different. They open the server after a day away and cannot catch up. Several topics overlap. A question is buried within minutes by an unrelated discussion. The members who used to carry the room say less, since whatever they care about keeps sliding off the screen.

Five signs tell you it is time to look for groups:

1. Replies between two members are separated by stretches of unrelated messages.
2. A subject returns week after week from the same members.
3. A member asks if there is somewhere for a certain topic.
4. A regular falls silent and, when asked, says the chat moves too fast.
5. Others begin to complain that a single topic has taken over.

Expect two or three interest groups to become visible at this point. Each one is visible in the chat, as a set of people already talking to each other, before it has any channel. The channel only gives them more room.

The three checks that justify a channel

Take the last four weeks of main chat history and test the topic against each line.

A channel is justified only when all three boxes are ticked. Partial results point to something else.

Weekly, same people, nobody crowded out. This group is part of what keeps the main chat lively. Leave it alone and look again in a month.

Weekly and crowding, with the people changing each time. The subject belongs to everyone. Give it a standing thread inside the main chat.

Same people, one intense week, then nothing. That was an event. Wait.

Write the outcome down in the same form every time:

Topic ............................
Weeks seen out of the last four ..
Names of the members driving it ..
What it is pushing aside .........
Requested by a member? ...........
Decision (channel, thread, wait) .
Host .............................
Review date ......................

The reason team invented groups stay empty is plain once you have run the test a few times. An invented group opens with nobody in it who already talks to anybody else. Staff post an opening question, a couple of members reply, and a week later the channel is silent. A group that passed the three checks brings its members and its habit of talking with it.

There is one condition underneath the test. Interests only surface in a main chat that has room for them. When most messages are basic product questions, the chat is working as a help desk and the topic that recurs will be a support problem. Members who arrive already understanding the product ask fewer basic questions, and the space that frees up is where subgroups come from. A main chat full of basic questions is a sign to work on what members learn as they join, beginning with a clear #start-here channel and a single home for common answers, before looking for groups at all.

Who hosts, and what the host is asked to do

A subgroup has a host before it has a channel.

If no member of the group will take on one thread a week, treat that as the answer. The group stays in the main chat and you ask again in a month.

Hosts move on. When one steps back, ask the group to name a replacement before the weekly thread stops, because a group that has been silent for several weeks is hard to restart.

Stage three, about 10,000 members: descriptions and a door

With several subgroups running, the thing that breaks is discovery. A channel name that was obvious to early members says nothing to a person who joined this morning. Newcomers settle in the main chat, never come across the group that would have held them, and go. This is also the size at which a host can vanish without anyone noticing.

A description that works follows this pattern:

For members who [do what]. [Host name] starts a new thread every [day].

The onboarding question can be as simple as this:

"What are you here to do?"   (several answers allowed)

Share work and get feedback ..... feedback group role
Learn the advanced features ..... advanced group role
Find people to work with ........ partners group role
Just looking around for now ..... no group role

A member who picks an answer arrives already attached to a group, and the host has someone new to welcome. Members can revisit their choices later on the server's Channels and Roles page.

Keep one rule for the door: a group earns its answer in the onboarding question only after passing the three checks and gaining a host. A new member should never be offered a room with nobody in it.

For a program built around creators, partners or ambassadors, the groups worth watching for form around what members make or how they work, such as a format several of them produce or a goal they share.

Stage four, about 100,000 members: moderators and a standing review

Subgroups at this size are large enough to have their own trouble, and two things give way.

Moderation. Disputes, spam and off topic floods happen inside a busy group, out of sight of general moderators who are watching the main chat. Assign each active group a named moderator whose job includes reading it, plus a second person for cover. Keep the host and the moderator as separate people:

• The host is a member. They start the weekly thread and flag problems to staff.
• The moderator is staff or a trusted volunteer. They read the group, remove spam and settle disputes.
• The program owner is accountable for the server. They run the review and decide which groups stay.

Build up. Groups accumulate. Some go quiet, and without a schedule nobody checks which ones.

Reviewing groups and closing the quiet ones openly

The first review date is set on the day the group opens and written into its record. Use one period for every group. My preference is a short first period for a new group, thirty days for example, followed by a review of all groups together once a quarter.

1. Did the host start a thread in most weeks?
2. Did anyone besides the host post?
3. Would any member ask for the group back if it closed?

Each group leaves the review in one of three states: kept as it is, kept with a new host, or archived.

To archive a group, move its channel into a category at the bottom of the sidebar and make it read only. The history remains and posting stops. Then tell people, in the channel itself and in the main chat:

We are archiving this group on [date]. It has been quiet for [period], and we want the list of groups to stay short and active. The history stays readable. If you want it back, tell a staff member and bring two other people who will post in it.

An archived group costs less than an empty one left on display. A newcomer who opens a group and sees that the latest message is months old draws a conclusion about the entire server. Announcing a closure has a second effect: members can see that someone looks after the list, so the groups that remain are easier to trust.

Three things the lasting groups have in common

A group about a subject members merely like gives them something to read. A group about something they do gives them a reason to return, and after a year that second kind is the one still active.

The system around the groups

Interest subgroups belong to role and channel architecture and engagement rhythm. Onboarding, moderation, documentation and reporting sit beside them. Onboarding determines whether members arrive understanding the product. Moderation covers the groups once they are busy. Documentation keeps basic answers out of the main chat. Reporting shows which groups are active. The decisions covered here, which are when to create a group, who hosts it and when to close it, can be put into practice without changing those other layers, each of which is its own piece of work.

Members form groups on their own schedule. A team that reads the main chat closely will see each one coming and can have a channel, a host and a review date ready when it arrives. More at danieljeong.org.