It's not just real-time, it's real-time plus async/archival. Best of both worlds if done right.
To borrow your "cavemen" analogy: email and undocumented verbal conversations strike me as prehistoric / uncivilized, in comparison.
(That's leaving aside the benefits of having a single hub for ~everything, which Slack is ~uniquely suited for given all the integrations.)
The original post nails some important issues: companies really need topic focused discussions, intentional, thoughtful writing, not just chat, more asynch so there is time for deep work and time for more thoughtful discussion and replies, and much better, topic-based search.
I believe in the impact of this problem so deeply that a team of us have been working on an open source solution to it for a couple years now. https://github.com/open-company
What we're trying to build is a place for companies to have focused, asynch discussions about the things that really matter, outside the stream of chat. The UI we've come up with isn't "Reddit-like" really, but it's an attempt to supplement Slack with what's missing, and it will evolve as we learn more.
If anyone is interested in trying it out, you can sign up for early access (we'll get you in very quickly) at: https://carrot.io/
The best conversations in Slack should really be a conversation in an issue tracker. Unfortunately, nobody will see those comments when they look at the issue. One issue I see with the carrot UI is that there's not really enough room to have a real conversation in the comments side-panel.
When I work from home, I explain to my colleagues that I mute slack and check it once in a while. If something is really critical, they call, otherwise they'll get an answer later. If I wouldn't communicate about this, people would expect me to be online, but I communicated about this, so they understand why I'm not.
No, you don't.
It's fair to be frustrated by defaults or how your org uses Slack (or any other tool), but these discussions often cross the line to FUD by exaggerating annoyances.
I'm fairly sure you can set do-not-disturb times as well.
/dnd, per-channel notif muting, and "away" status combine for reasonably fine-grained control
Simple group-posting is stupid – groups are muted or annoying, or induces a fear to ask questions. But the absense of group/topic alarm can also turn into inconvenience.
/never used slack, know nothing about it
> A good alternative to Slack would be a Reddit-like interface with threads and an asynchronous model.
You're describing Twist -- twistapp.com.
From the article:
> Remote work culture is a defense mechanism against the distracting open office, and slack is the end run around that defense mechanism.
Slack kills off any benefit there is of being remote, because it is immediate: you need to be online all the time, and you need to answer / participate / chat instantly.
A good alternative to Slack would be a Reddit-like interface with threads and an asynchronous model. That's also the superiority of email over any chat solution. I don't understand why people and organizations get so excited about real-time conversations.
We always had real time. Cavemen had real time. Writing was invented to free us from real time, to transfer information in non-real time and to future generations.
But now it seems the cavemen are back, with a vengeance.