3 ms·
Well Slack might have not worked for you. It doesn't work for everyone! Probably it works the worst for devs? Here is a story. I was working with a team of coup
by orliesaurus 8y ago
Well Slack might have not worked for you. It doesn't work for everyone! Probably it works the worst for devs? Here is a story. I was working with a team of couple people located in different corners of the city. Everyone is remote except two who share an office. Up until a month ago everything was done over email. Sometimes you would send an email and get a reply in minutes, other times after hours. This was highly inefficient, to the point where I would call people to ask them to open emails... Guess what happened since we installed Slack and a couple of general open channels?
- beberlei 8y agoYes, i don't doubt that Slack works for companies. It doesn't work for our company and our value of trying to maximize uninterrupted work time.
- lmm 8y agoI found the great success of Slack was reducing interruptions. It replaces things that would have otherwise been a "hard" interruption (in-person conversation or phone call) with a "softer" interruption (notification). And it provides a much better way for people who need to speak with "someone from the x team" to talk to whoever happens to be relatively free at the moment, rather than picking someone to interrupt. (Also are you sure minimizing interruptions should be a goal? If you cut off all communications you'll avoid interruptions, but that probably won't be good for your business)
- buckminster 8y agoWhy can't you do something else while you're waiting?
- orliesaurus 8y agoYou can, but the thing is that unlike with emails, with Slack most conversation happen in public and no one has to CC you in email (or rather remember to CC you in these convos) basically slack replaces CC and BCC part of the email really well