3 ms·
I agree that Slack is a productivity-minimizer. However, my deeper qualm is how conversations about Slack (and other tools) inevitably end with someone saying,
by wildermuthn 7y ago
I agree that Slack is a productivity-minimizer. However, my deeper qualm is how conversations about Slack (and other tools) inevitably end with someone saying,
“It isn’t the tool, it is how you use it.”
Malarkey. Tools dictate usage. The phrase people need is,
“When all you have is a hammer, every problem looks like a nail.”
Slack is a tool for communication. But it is helpful to define communication and then to ask what kind of communication Slack facilitates (and thus encourages).
Communication is a poor word, because it embeds within the word many slightly different but important meanings. Communication can mean the mere transfer of information. But communication can also mean a successful transfer of information.
So really, we can’t simply define “communication”, but must rather define “good communication”. And its definition is simple: transmitting the right information to the right entity at the right time and in the right manner (i.e., in a way the entity can understand correctly).
Slack facilitates transmitting any information to any person at any time, and (with the use of plugins) in almost any manner. This is almost the definition of bad communication.
Yes, you can try to limit the use of Slack to avoid these problems. But you are working against Slack, not with it. Every tool that facilitates good communication does so by disciplining and focusing the transmission of information. Slack’s mission is the opposite. Slack aims to achieve a riot of information. Slack is information anarchy.
Maybe this helps for work that is by nature anarchic, where information flow is more important than knowledge exchange. But for the rest of us, it is a cursed tool.
- count 7y ago> 'You can try to limit the use of Slack to avoid these problems. But you are working against Slack, not with it'. So, if I have a hammer, I shouldn't try to use that hammer in a constructive manner, but should throw it away and find something that is universal for all of my tool using needs? Rather than using the hammer as a hammer? Sure, any team can screw up communication. I'd argue that many teams ship shit software in shit environments, and that adding slack is like adding 'devops' or 'agile': if your team sucks, it doesn't matter what tool you use, you're gonna suck. Adding new tools may even make you suck worse, because you now have 2 problems: poor comms AND a tool that doesn't fix that which you have to deal with. Slack is a hammer. And I have a shitload of nails to hammer in. I don't have ONLY nails, and Slack isn't my ONLY tool, and it's not appropriate for ALL THE THINGS. But your own argument is that you shouldn't look at it as the solution to everything, but then throw it away because it's not the solution to everything. Is it the tool for you? Apparently not! And that's fine. That doesn't make it a bad tool. Some of us have lots of nails to hammer in, and some of you have screws that need another approach (even if you could hit it hard enough to drive it home...thats probably non-optimal).