The main things we'd aim to improve with our Slack Channel Structure are
If we're consistent in how we use Slack, it becomes easier to use. If there is a sort of standard in place, we can know what to expect. We know what information is available and where to find it. A consistent naming approach or a consistent usage of topics could help us use Slack better.
When you want to find a channel, what do you do? It's not always easy to find what we're looking for. This is even more true for new hires who might be missing out on channels that are relevant to them.
We don't want to have too many channels. But we also don't want channels to have a bloated purpose. Each channel should be relevant and have a clear objective.
We use a standard prefix system to categorize channels in various broad "families" of channels.
The following prefixes are examples
eng- for engineer related topics. Examples: #eng-code-reviews , #eng-random, #eng-core, #eng-all
fun- for non work-related topics. Examples: #fun-cooking, #fun-movies, #fun-random
cph- for Copenhagen related topics. Examples: #cph-office
ldn- for London related topics. Examples: #ldn-office
hire- for hiring related topics. Examples: #hire-people-ops, #hire-frontend-engineer
feat- for temporary channels focused on a specific feature. Example: #feat-french-stock