Slack Channel Management

img

What kind of “things” do we engage in?

  • Activities (actv-): Daily, weekly, monthly, ad-hoc, and fun activities.
    • Hour reporting and collection, invoicing, etc...
  • Projects (proj-):
    • 250P, 247P, 262P, etc...
  • Initiatives (init-):
    • Marketing, process improvement, opportunities, etc…
  • Customers and account management (acct-):
    • Amazon, HBO, Walmart, etc...
  • Internal and external support requests (supp-):
    • Zendesk, IT, onboarding, automation, etc….

Other Considerations

  • Other base channels we can use if/when needed.
    • team- : dev/ops/exec/design/etc...
    • orgn- : corp/hr/finc/etc...
    • tool- : asan/enhr/outl/slck/etc...
    • vend- : exla/hlpw/etc...
    • loca- : ukm/germ/inda/virg/etc... (used for notifications).
  • Prefixes and suffixes for special channels
    • extn- : prefix for channels that have customers on them (like extn-proj-ls-247-ses).
    • intg- : suffix for channels that have integrations associated to them (like supp-blt-intg).
  • Channel permissions options
    • Continue with current usage of individual users.
    • Utilize Slack Group arranged similar to Google groups.
  • House keeping
    • Creating channels - careful consideration should be given to creating channels to ensure it is the appropriate time (usually when comm’s have grown great enough that it is polluting an existing channel).
    • Archiving channels - when in doubt--ARCHIVE! Anything business related should be archived. Archived projects can be reopened, but loses users previously subscribed.
    • Deleting channels - when in doubt--ARCHIVE! Anything not related to business can be deleted. For instance, #actv-fun-picnic2020 can be deleted after the event, unless someone believes it contains information/contacts/discussions useful to reference prior to next year’s picnic. For instance, I wish I knew what beer distributor we used for last year’s picnic.
    • User and group maintenance needs to be included in onboarding/offboarding procedures.