"Group Chat: The Best Way to Stress Out Your Team"

What Chat system are you using? - "one line at a time" -- what?? No chat system I use works like this. You get a paragraph, even a whole page, with notes, images, etc.. all at once. - 'must constantly watch the channel' -- what? No you do not have to do this. Mark yourself as away, and get back to the Slack (etc.) conversation later.

It's a nice article on balance, but you definitely have some "contrive" negatives there.

- "Implied consensus" again, wrong. I mean, it's possible that "some people" might discuss a topic and then go off and do it, but generally, anything that requires "consensus" would be left until.. there was consensus. That's an easy one to fix.

- 'Knew Jerk Response' - again, complete bollucks. Nothing "scrolls away", you have a huge or infinite history, and the tools show what has not be read, so just read it when you have time. I've never been in a conversation where there is some "urgency" to read this right away and respond.. who are you talking to??

Item 7 - Yeah, I can see that one occasionally, but not the people I generally work with. On "shared internet" channels, yeah, but internal work channels.. almost never.

Some of the other items seem more real, and things I've experienced. Some seem like minor, nit-picky things though. 25 used to be 1... yeah, occasionally a conversation can drag on --- but so can an email chain.. and, don't get me started about how many "Meetings" ramble on long after the main point has been (or should have been) made.

Some key points I might make -- it's better t have many smaller conversations, with specific individuals, rather than "a small number" of truly "pile on everyone in the organization is in this channel" conversations. Maybe you need to better organize the groups of people in a particular discussion?? Just a thought.

Item 14 -- it's called search, and yeah, it works really well. It might be a great "long term reference" but then, is email? is a meeting? Is a zoom call (or equiv)? I mean, if you need something for long term -- document it for pete's sake (sorry Pete).

#15 - Yeah, that does happen..

#16 - this can be true, but, I don't hesitate to just ignore something I have to. maybe that's a "company policy" that can be implemented?? Maybe not..

My key point here would be - While Chat "seems" like it should be immediate, it is also possible to treat it as "asynchronous", where an answer is NOT required immediately. You have some good points, but I think you "stretch" the negatives to sell your overall point just a bit too much.

My $0.02