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.

...

1. general purpose, all-team by topic (#random, #general, #positivity)

2. team-specific by general function (#sales, #engineering, etc)

3. Cross-team by campaign (#adp-integration)

4. Bot reports (#crm-salesforce, #rollbar xyz, #new-lead-notifications)

5. Business-unit specific (#sbi-v2, #sbi-v3)

Formatting

Use an underscore “_” to denote hierarchy, and use a hyphen “-” to replace a space.

So #product_ui-ux allows a multi-word sub-team under the overarching product team.

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.

1. By customer (#cust-)

2. By feature or tool (powerBI, ezVet, ) (#…<tool>)

3. By vendor or bot integration (rollbar, aws, etc.) (#…bot)

4. By campaign (#camp-

How do we use naming to help group these? CS_Title, ENG_Title, etc…

...