How to name Slack channels
A well-designed channel convention improves team productivity in measurable ways: less time searching for where to ask, smoother onboarding, fewer duplicate channels with the same purpose.
- Prefix by type. #proj-, #team-, #help-, #social-, #ann-. Visually grouped.
- Lowercase and hyphens. #proj-launch-q1, not #ProjLaunchQ1.
- Descriptive and specific. #help-billing beats #help-stuff.
- Short but clear. Aim for 15-25 characters.
- Written convention. Document it in #ann-channel-rules.
Recommended conventions
- #proj-: projects with clear start/end (#proj-mobile-app, #proj-launch-q1).
- #team-: permanent teams (#team-design, #team-engineering).
- #help-: internal support (#help-finance, #help-legal, #help-it).
- #social-: casual (#social-coffee, #social-pets, #social-music).
- #ann-: announcements, read-only for many (#ann-company, #ann-product).
Common mistakes
Most common: no convention at all — the workspace fills with inconsistently named channels and nobody finds anything. Second: cryptic internal names that require context — "#g4-q3-c2" tells a new hire nothing. Third: not archiving dead channels — your active channel list gets noisy.
Operational best practices
- Define the convention before exceeding 30 channels.
- Archive channels with zero messages in 30 days.
- Review channel list every quarter.
- Use clear descriptions and a pinned message with rules.
- Limit who can create channels in large workspaces.