Pet Loyalty Slack & Communications Guide
...
Once a channel or team gets big enough, it’s great to have thread discipline, meaning, formatting channel posts as announcements with discussions to follow underneath. In many cases, I recommend making a channel for leadership announcements where only admins can post to the channel and follow up conversations must be threaded.
Content Channels
Note: It is not advisable to have channels dedicated to types of posts. If I’m a marketer, I want to report to #marketing or #revenue to see marketing-related messages, not have to check a separate channel for “marketing meeting attendance.” If you cannot make the marketing meeting, the relevant parties are all already checking #marketing, so there’s no need to spread information thin across more channels here.
Another example is #good-to-knows. If there’s a good-to-know piece of information relevant to sales, it should be posted in #sales. Why spread it out?
Channel naming conventions [Temporary Heading]
Channels serve a handful purposes:
general purpose, all-team by topic (#random, #general, #positivity)
team-specific by general function (#sales, #engineering, etc)
Cross-team by campaign (#adp-integration)
Bot reports (#crm-salesforce, #rollbar xyz, #new-lead-notifications)
Business-unit specific (#sbi-v2, #sbi-v3)
Notes: I want to label campaign- and problem-specific channels so that they don’t roll into the fold. What are the types of channels I’m seeing arise? I also want to roll automated notifications into similar channels.
By customer
By feature or tool (powerBI, ezVet, )
By vendor or bot integration (rollbar, aws, etc.)
How do we use naming to help group these? CS_Title, ENG_Title, etc…
Expand |
---|
Policy: Creating a Slack Channel
|
DMs (direct messages)
DMs are for fun side chats and work-related chats that are private.
...