OP here. I think the problem is that when tools like Slack are engineered in such a way as to make people dependent on their product, it's unfair to expect users to accept all the responsibility of mitigating against that. Software companies aren't using organizational productivity as a benchmark for their success, just usage statistics. So no, Slack doesn't enforce a single way of working, but it is engineered to consume as much of people's time as possible, for better or worse.
Jason Fried wrote his in his (much more comprehensive) post about group chat pros/cons:
"It’s common in the software industry to blame the users. It’s the user’s fault. They don’t know how to use it. They’re using it wrong. They need to do this or do that. But the reality is that tools encourage specific behaviors. A product is a series of design decisions with a specific outcome in mind. Yes, you can use tools as they weren’t intended, but most people follow the patterns suggested by the design. And so in the end, if people are exhausted and feeling unable to keep up, it’s the tool’s fault, not the user’s fault. If the design leads to stress, it’s a bad design."
Jason Fried wrote his in his (much more comprehensive) post about group chat pros/cons:
"It’s common in the software industry to blame the users. It’s the user’s fault. They don’t know how to use it. They’re using it wrong. They need to do this or do that. But the reality is that tools encourage specific behaviors. A product is a series of design decisions with a specific outcome in mind. Yes, you can use tools as they weren’t intended, but most people follow the patterns suggested by the design. And so in the end, if people are exhausted and feeling unable to keep up, it’s the tool’s fault, not the user’s fault. If the design leads to stress, it’s a bad design."
(https://m.signalvnoise.com/is-group-chat-making-you-sweat-74...)