A team space with two channels is easy to navigate. A team space with thirty-one channels is a junk drawer with a login screen. Structure is not bureaucracy — it is the difference between a colleague finding last quarter's decision in ten seconds or re-litigating it in a meeting.
The Three Channel Types
- Standard channels are visible to every member of the team. Everything the whole group may see belongs here.
- Private channels inherit the team but restrict membership and content to a subset — useful for sensitive subtopics, but they fragment the archive.
- Shared channels include people from outside the team, even outside the organisation, without making them full members.
Default to standard. Reach for private only when the content genuinely must not be visible to some members; otherwise a private channel is just a standard channel that future members cannot search.
Naming That Survives Growth
Channel names are navigation labels, so write them the way you would label folders in a shared cabinet:
- Use the topic, not the project codename nobody outside the core group knows ("invoices-eu" beats "phoenix").
- Keep a consistent prefix scheme if you run many similar spaces: "help-", "proj-", "soc-".
- Avoid years in names unless the work truly ends ("proj-audit-2025" guarantees a duplicate next year).
- Lowercase, hyphens, no clever punctuation — search and muscle memory both prefer boring.
How Many Channels Is Too Many?
There is no magic number, but there is a reliable symptom: when members post in the wrong channel weekly, the structure is too fine-grained. Merge rather than multiply. A healthy mid-size team usually runs between four and nine channels: one general, one per durable workstream, one for announcements, and one social.
The announcement channel trick
Create a channel where only owners can post. Announcements buried in chatter get missed; a read-only channel trains people to look when something official lands. Pair it with a rule: anything truly org-wide also goes out by email, because not everyone follows every channel.
Following, Hiding, and Leaving
Membership and attention are separate controls. You can belong to a team but follow only three of its channels; the rest stay collapsed and silent until you search them. Hiding an inactive channel is not leaving it — the history stays reachable. Encourage new joiners to follow deliberately in week one rather than inheriting every channel by default.
When to Split a Team
Split when two audiences with different confidentiality needs share one space, or when a workstream outlives its parent project and develops its own membership. Do not split merely because conversations got busy; busy is what a healthy channel looks like.
Structure decisions are cheap to make early and expensive to undo late. Ten minutes agreeing on naming and channel count with your team saves months of "wait, where was that file?" — which is exactly what the files chapter tackles next.
