Channel Description Writing
Channel descriptions, naming conventions, archive vs delete, pinned messages, and onboarding
Channel organisation essentials
- Description formula: purpose + what belongs + what does NOT belong + related channels
- Naming conventions: prefix-based (#prod-, #team-, #help-, #proj-) — makes channels searchable and self-organising
- Archive not delete: preserve history for completed projects, resolved incidents, deprecated features
- Pinned messages: operational guide in the channel itself — not a link to the wiki
- #start-here channel for new hires: 8–10 must-join channels with descriptions + notification guidance
Question 0 of 5
Which Slack channel description is most effective for a new team member trying to decide if they should join?
Purpose + what belongs here + what does NOT belong + related channels. Effective channel description formula:
- Purpose: "Backend team daily discussion" — one-line job statement
- Scope: "architecture decisions, code reviews, deployments, technical blockers" — what types of posts belong
- Exclusions: "Post bugs to #backend-bugs" — redirects off-topic traffic
- Related channels: "On-call rotation in #backend-oncall" — helps navigation
- Slack shows the description when someone hovers the channel name in search — it's the first thing newcomers see
- Without a clear description, channels become catch-all dumps — "general team channel" invites everything and signals nothing
- Related channel pointers prevent the same question being asked in multiple channels
A company has 300 Slack channels. An engineer cannot find where to post a question about production database performance. What is the root cause of this problem?
No descriptions + no naming conventions + no directory = unnavigable channel soup. Channel organisation requires three things:
- Naming conventions: prefix-based (e.g., #prod-, #team-, #proj-, #help-) — searchable and self-organising
- Descriptions: every channel should have a one-line purpose + what belongs + related channels
- Channel directory: a pinned or wiki-linked list of the most important channels with their purposes — especially useful for onboarding
#prod-incidents— production incidents only#prod-deployments— deploy status updates#help-databases— database questions across teams#team-backend— backend team daily discussion#proj-auth-rewrite— project-specific temporary channel
When should you archive a Slack channel rather than delete it?
Archive (not delete) when the channel is done but history has value. Archive vs. delete:
- Archive: hides the channel from active lists, preserves all messages, searchable, can be unarchived — use for completed projects, resolved incidents, deprecated feature discussions
- Delete: permanently removes all messages — use only for channels with no meaningful history (accidental duplicates, test channels)
- #proj-auth-rewrite — project shipped, keep for reference
- #incident-2025-03-15 — incident resolved, keep for post-mortem reference
- #feature-old-dashboard — feature removed, keep for context
Which pinned message is most useful at the top of a #prod-incidents channel?
Pinned message = operational guide: what to post, how to post, escalation path. Effective pinned message for an ops channel:
- What to post: "incident title + severity + ETA" — people know the format on first post
- Thread discipline: "use thread for updates" — keeps the channel scannable; main message = incident, thread = progress
- Definition of done: "after resolution, post RCA link" — closes the loop
- Escalation path: "page via PagerDuty" — removes ambiguity in a high-stress moment
- @mention scope: "@here only for P0/P1" — teaches appropriate use of disruptive pings
A new engineer joins and faces a 300-message backlog across 20 channels. Which onboarding channel practice helps most?
#start-here channel: curated must-join list + descriptions + join links + optional extras. New hire channel onboarding structure:
- #start-here (must-read): pinned guide with 8–10 essential channels, each with a one-line description and link to join
- Must-join channels (day 1): #announcements, #team-backend, #prod-incidents, #help-general
- Join as needed: #proj-*, #help-*, #random — described so the new hire can decide relevance
- Mute from the start: #notifications-ci, #bot-alerts — tell them these are high-volume and safe to mute
- Channel naming convention explanation
- Notification guidance (which channels should be loud, which muted)
- When to use DM vs. channel vs. thread
- How to ask for help (include ticket link, error message, what you tried)