3 ms·

It sounds like the cultural norm for how their team is using Slack is synchronous. I'd strongly suggest building a culture that Email and Slack are Asynchronou

• RBerenguel 10y ago
  Our unwritten but seems to be more or less the rule at work is that unless you get an @ (either in a general channel or in a 1-1 chat) anything that goes into slack is as async as email. Maybe a little bit less, but the expectation is that you will get to it at some point and that's it. I don't find it specially disruptive this way. Way less than shouting from one side of the office "hey, check the deploy!"
  • Bartweiss 10y ago
    This is exactly how we've handled Slack. It's sync (to within a minute or two) for @ messages, which are used sparingly. It's async for everything else, and it's faster than email only in that it's a bit more conversational. Within that norm, all of the "Slack is an evil attention vampire" complaints feel deeply unfamiliar to me. I find it less distracting than email because @ makes message priority clear at a glance.
• Bartweiss 10y ago
  Using Slack asynchronously (or rather, using only private messages synchronously), these complaints are totally alien to me. Seeing Slack called "Facebook for work" doesn't feel inflammatory, it feels bizarre. I suspect synchronous culture would change things quite a bit. I've certainly never had the sense that "hey, do this when you can, no rush" meant anything but what it says. Of course, some of this seems to be about configuration approaches. I had forgotten that Slack's dock icon embeds notifications, because my dock minimizes when not in use.