Create intermediate Works with: Any AI

Slack Channel Structure and Naming Plan for a Growing Team

Table output Has example

• 💬 Slack

Design channels that people can find and that do not multiply without control.

The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.

[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.

Design a Slack channel structure for [ORGANISATION_DESCRIPTION]. Teams and functions: [TEAMS]. Projects and clients: [PROJECTS]. Current channels and their problems (too many, unclear purposes, duplicated topics): [CURRENT_CHANNELS]. People who administer the workspace: [ADMINS]. Inactive days before archiving: [INACTIVE_DAYS].

Return a table with Current channel, Action (keep, merge, rename, archive), New name and Purpose, and the naming rules as a numbered list, using prefixes such as team-, proj-, help-, announce- and social-. Example structure for a 60-person company with fifteen channels: team-engineering, team-sales, proj-checkout-redesign, help-it, help-finance, announce-company, social-random, each with a one-line purpose that would go in the channel description. Count the channels before and after (for example 74 before, 41 after) with the arithmetic. Define which channels are public or private and why, and which are announcement-only. Check that no two channels have the same purpose, every channel has an owner, and the names make sense to someone who joined yesterday. Rules: creating a new channel, archiving after the inactive limit, and five channels every new person joins.

Do not move private conversations into public channels without saying so and asking the people concerned. If the information is not enough to decide about a channel, put it on a questions list. Add a table of archive candidates with evidence, a message announcing the new names with the date of the change and how people will be moved, a plan to keep history when renaming or archiving [VERIFY], and a 30-minute quarterly review run by a named person. Mark features in our plan [VERIFY].

Fill in before use

Optional: type your details and the prompt above updates. Nothing is saved or sent.

Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.

Invented counts: 74 channels before, 41 after. Table rows. old: random2 -> merge into social-random. old: marketing-stuff -> rename team-marketing. old: proj-checkout-2023 -> archive (no posts for 14 months). old: help -> rename help-it (purpose: IT support requests). Rules: prefixes team-, proj-, help-, announce-, social-; every channel has a one-line purpose and an owner; archive after 90 days without posts. Core channels for new people: announce-company, team-name, help-it, social-random, help-hr. Reduction: 33 channels, 44.6 percent. Announcement to staff: 'On Monday we are tidying channels. Old names redirect for a week. Ask in help-it if you cannot find one.' Review: quarterly, 30 minutes.

• slack