Live data from Hacker News

Why we’re betting against real-time team messaging

blog.doist.com

31–40 of 220 posts

Re: Why we’re betting against real-time team messaging

#31

I worked at a Slack shop for several years, and share the author's opinion. I can't think of any five minute period during my entire tenure where the Slack tab didn't have a little red circle telling me that I absolutely needed to check it right this second. There was no way to filter notifications beyond "Everything", so that little bubble would go up every time anybody in the company pressed a key. And heaven forbi…

More granular controls really would fix this problem. For instance, per-channel settings to have the channel highlighted in the sidebar when it has new messages, but without badging the tab/dock. That way you could reserve the badges for the channels you really need to monitor closely, but not have to check every single other channel explicitly to see if there are new messages.

Man, that would be amazing. It would be sweet if there was a third party slack notifier that could do that kind of thing. Basically you just run the notifier and quit the main slack app, until the notifier tells you to pull it up. Then you interact with it, and when you're done, quit it again.

Re: Why we’re betting against real-time team messaging

#32

TL;DR they made a modernised version of an nntp client and server ;-)

I mean, isn't Dropbox just prettier rsync?

And Slack is a modern version of IRC :)

It keep being surprised by how much a fresh coat of CSS and a mobile app can reinvigorate these old ideas. Who knew how important adding gifs and emoticons would be?

Re: Why we’re betting against real-time team messaging

#33

Earlier quoted context omitted.

It's called Facebook Workplace. Balance of Messenger for immediate communication, groups for threaded conversations, and feed for discovery.

I don't think I've really heard much about that product since the announcement. Is it good? And are accounts tied to Facebook proper? That would turn me off completely.

Disclaimer: Workplace Partner @ Job

I was cynical about it to begin with, when it was just 'Facebook at Work' but I do believe it addresses a lot of the issues brought up in the blog post and the Workplace team are executing very well.

Accounts are completely separate from Facebook, no crossover at all.

I don't think it's a Slack killer, as they both solve different problems in different ways, and Workplace is very much a 'big co, top down' approach.

I do think other existing collaboration tools have a lot to be worried about between Slack & Workplace though.

Last stat I heard was there is over 14k companies using it.

Re: Why we’re betting against real-time team messaging

#34

I worked at a Slack shop for several years, and share the author's opinion. I can't think of any five minute period during my entire tenure where the Slack tab didn't have a little red circle telling me that I absolutely needed to check it right this second. There was no way to filter notifications beyond "Everything", so that little bubble would go up every time anybody in the company pressed a key. And heaven forbi…

We've left the "social" era and have entered the era of interruptions. All the innovation this decade is in interruptions no longer human-interconnections.

My smart watch for example post dates the social era so it has only minimal social features, but its deep in the interruption zone and spams me mercilessly until I block apps and if I block enough apps I may as well have a cheap dumb watch.

Another way to look at it is we no longer have 100 people shallowly liking us, we now focus on 100 apps shallowly claiming our attention is vital because we are important and we must be interrupted now.

Some of this is probably cultural backlash against automation and bureaucracy and general economic decline. If more people than ever are in fact not useful or important at all, then a communication style focused primarily around telling people they're important, is going to be very popular.

Under that analysis Slack is a post-social communications media, and it constantly rewarding you with endless micro doses of "your attention is valuable" is not a bug, its the whole philosophy of its existence as an app. You can see why curmudgeons see Slack as something negative, like the intrusion of participation trophy culture, because thats pretty much what it is.

The purpose of Slack is to constantly interrupt you with a narrative that you're important. There are incidental side effects that make it semi-useful. Companies spend a lot of money on "make employees feel special" and Slack is merely a modern example of the genre.

This philosophical analysis of Slack is probably extendible past Slack into startups. Don't try to market something as interconnectedness, not in 2017. Try to sell something that symbolically, or whatever, tells people they're important.

Re: Why we’re betting against real-time team messaging

#35
I think that Slack (or any other IM client for work, really) is just a tool, not a solution. Meaning that it requires some organization and thought, rather than installing and hoping for the best. At least to some extent (i.e. have no idea about companies with hundreds of engineers online), it works. Equally important it is to acknowledge what is suitable for doing on IM and what is not.

If you want to discuss some large changes, sure, IM is a bad place. Conversation will probably get interrupted, derailed, etc. That's where, in my opinion, things like Google Docs or plain simple GH Issues shine. The format forces into better thought out, longer messages.

For other things, you need to organize the chat rooms. If you have 10+ people and 2 chat rooms (I think slack defaults to #general and #random) then yes, sounds bad. But instead having quite a few chat rooms with "Always on", I believe, comes not from the IM itself but from the culture of the company. I know places where everything is e-mail only and people constantly refresh it. Equally, IM is mostly ghost town outside working hours at other places. And Slack has decent notification settings to make sure that you don't go crazy.

So, IM has it's place and provides value if you are willing to make it work. It's just not a 'it just works' solution, which is hardly surprising.

Re: Why we’re betting against real-time team messaging

#36

so how is the end solution different/better than email?

Easier to give / remove participants and automatically give them access to previous messages in the thread, without having to quote all previous messages just to give some context.

Re: Why we’re betting against real-time team messaging

#38
post #17
post #11

A small, but impactful design choice we made in creating Twist was to leave out the online presence indicator. I imagine you could address this in Slack by just having everyone set themselves to 'Away' by default. One of the things that I've found useful in Slack is turning off the "Someone is typing" message (the option is in the Display Options). I used to wait for someone to post if I knew a message was coming. No…

It sounds like you kind of ended up with e-mail :)

I would like to see a meaningful discussion of the tipping points between various forms of communication.

ie: Phone call when you need immediate, high-bandwith dialog; IM when want to chat, but don't need instant responses; email when you want persistent communications, etc

Those are very brief, single faceted views, and there are a lot more factors.

Re: Why we’re betting against real-time team messaging

#39
post #11

A small, but impactful design choice we made in creating Twist was to leave out the online presence indicator. I imagine you could address this in Slack by just having everyone set themselves to 'Away' by default. One of the things that I've found useful in Slack is turning off the "Someone is typing" message (the option is in the Display Options). I used to wait for someone to post if I knew a message was coming. No…

I would agree that culture is a major factor - we briefly implemented Slack a few years back at a company before I left, and I watched it drive our Senior Programmer nuts, as we didn't really have good solid rules or behavioral standards for Slack. I'm not talking about a tome of laws and regulations, but just a few simple things like "Don't spam chats with non-work related items", "Don't spam looking to get someone's attention", etc. The Senior in question was an older guy who had a lot on his plate and and a bit of a short fuse. It absolutely ended up driving him nuts as now instead of relatively quiet and ignorable chat messages, he was getting spammed and pinged by absolutely everyone at once, and those in the office with less on their plate definitely treated Slack like their own IRC channel for shitposting.

Poor support from our management in general, and a poor delineation between private channels and public channels resulted in a lot of private rants being exposed publicly (not just from the Senior), and the end result was Slack was shelved for the time being and the Senior Programmer left the company.

My new place of employment utilized a multi-tiered approach, using Skype for quicker questions (with rooms dedicated to specific topics or aspects of the work), and anything requiring more than a sentence or two of background being regulated to an internal message board system. Our management is quick to shut down too much spam, and everyone in general is taught about the expected etiquete of the chat.

Without such precautions, I think it's too easy to fall into the more casual "shitposting" that is common for message boards and the chatrooms of old. Workplace chats are meant for very narrow and specific purposes, and it needs to be enforced that these are not the places to be spamming the latest gif you found on reddit/imgur.

Re: Why we’re betting against real-time team messaging

#40
I cant help but draw parallels between this and NNTP. This is essentially a really nice skin over newgroups, and thats not a bad thing at all. We have seen just how successful a modern UX can be on a old protocol with slack providing a UX to IRC. It is funny that we are slowly reworking the tools of the early computing community in slick modern ways.

It is also interesting that we as a community have completely sold out federated independent operators with a common standards defined protocol for soloed tooling.

Post reply on HN