Slack Summit Notes

slack-summit.md

• Keep eyes peeled for potential of threading!
• Machine learning is coming.
• Slack has single chanel collaboration with external agencies - could potentially be used for authors? Although I envision that becoming complicated
• Don't be afraid to police chanels. If something seems off-topic for a chanel, direct the user to a more appropriate discussion place (courteously!). Lopp calls this :racoon:ing
• Devs release to web 40 times per day
• They suggest a 'no internal email' day to get staff on board
• Staff need to understand why we use slack before they begin to use it...the more onboarded onto slack earlier means as the company grows theres a better position to handle future change
• Words like: 'transparent behaviours', 'key champions to guide people'
• Questions:
  • What's our active daily user engagement?
  • Should we use private chanels (opposed to DMs) for tracking one-on-ones and actions within them?
  • Should we have thorough training documentation for first time slack users? More and more staff are using slack because of newslists so I think this could be a good idea
  • Implement a #slack-help channel for specific assistance related to slack. Have a FAQ too.
  • Implement channel naming conventions, which we have kind of begun to do with all our dev channels
  • What is our goal in using slack? They really plugged the 'less meetings' angle today, but there were plenty of coporate companies there. For us it's probalby more 'team-to-team' collaboration and transparency between regions and dev/editorial e.c.t