3 ms·

I wrote my 2 cents about this article, in a follow-up Medium post - https://medium.com/@preslavrachev/slack-isn-t-the-problem-we-are-ef422d64cc19#.yygap7p0k htt

I wrote my 2 cents about this article, in a follow-up Medium post - https://medium.com/@preslavrachev/slack-isn-t-the-problem-we-are-ef422d64cc19#.yygap7p0k https://medium.com/@preslavrachev/slack-isn-t-the-problem-we...). Here is a just a relevant comment to this discussion: "[none of the arguments], has to do with the tools themselves, as much as it does with our way of using them. We have come to a point in our development, in which 24/7 availability is perceived as normal and expected behavior. Yet, to blame it on the tools we use, is like blaming it on the hammer for accidentally hitting your finger while trying to hang a picture. Indeed, the tools we use, have certainly made it easier for us to reach this point, but ultimately, it is us who pulled the trigger, not the tools."

tmail21 11y ago
I wrote a follow up to both your article and the original one. https://medium.com/@rnotani/the-different-frustrations-of-slack-and-email-d56cc59ac7ec https://medium.com/@rnotani/the-different-frustrations-of-sl... Here is a relevant quote from the article. "In my opinion both of these posts get it partly right. Both of these articles also have as a subtext an implicit or explicit comparison with email. Both, Slack and email tend towards “communication overload”. However, the generic description of “communication overload” obscures the very different type of overload created by these two technologies. Understanding this distinction also leads us to a possible solution.