Ask people to file tickets, create chatbots that automate filing tickets, create a service cookbook, and so on.īut there are few ways how one can help with solving the issue in the Slack itself. The strategy here is to funnel interruptions into an increasingly small area, and then automate that area as much as possible. The second most effective time thief that I've found is ad hoc interruptions: getting pinged on HipChat or Slack, taps on the shoulder, alerts from your on-call system, high-volume email lists, and so on. How to Set Up Your Slack AppĮlegant Puzzle by Will Larson lists ad-hoc interruptions as the second most "effective" time killer in any company: Please read Slack Etiquette Guide, which is an excellent overview of the key concepts for sustainable Slack. There are channels for casual conversations, sharing interesting links etc. We tend to use Slack as a type of “social network”.Please don't send information which should be captured as Jira ticket or Confluence page only to Slack.Basically, if you are writing something what is longer than 3 sentences, that should probably go to email or ticket. Person on the other side, will either need to put effort into understanding your question/comment and/or she will need to put effort into responding.You don’t require “immediate” response.Please, don’t sent messages, which really should go via email.People will probably overlook messages in channels, when they get back from vacation. Slack is treated as strictly best-effort communication platform. Nobody is required to response on Slack.We are using Slack for non-urgent semi real-time, simple communication.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |