News for hackers. Stuff that matters.
Re:Why we’re betting against real-time team messaging by jasonkester on Monday June 19, 2017 @09:12AM (#14586646)
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 forbid somebody typed "Good morning, @channel" (which happened 20 times per morning per timezone), because then you'd get the dreaded Red Exclamation Mark in the tab.

I can't fathom how anybody would have been able to work if they had gone as far as allowing notifications to be turned on and make noises at them every time Slack thought something Important Enough To Interrupt You had happened.

Re:Why we’re betting against real-time team messaging by VLM on Monday June 19, 2017 @09:34AM (#14586770)
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 by SyneRyder on Monday June 19, 2017 @10:14AM (#14587108)
> My smart watch ... spams me mercilessly until I block apps and if I block enough apps I may as well have a cheap dumb watch.

Definitely block the spammy apps. It makes a huge different to the smartwatch experience if it's only buzzing for things that really are urgent. Once you tune the notifications, it's actually calming - not only because you're not being interrupted as often, but also because you're not constantly thinking "is there something that needs my attention". If there is, the watch will let you know.

Re:Why we’re betting against real-time team messaging by icebraining on Monday June 19, 2017 @11:04AM (#14587499)
To me, that doesn't make much sense; the whole point of a smartwatch seems to be making the reading of notifications more efficient and unobtrusive. If you disable all except the rare urgent ones, what's the point of the smartwatch?
Re:Why we’re betting against real-time team messaging by Jtsummers on Monday June 19, 2017 @12:04PM (#14587955)
Notifications are inherently intrusive. You have to pare it down to the set of notifications you care about most so that you aren't constantly interrupted. I made the mistake, recently, of letting the News app on iOS notify me, no sound but near constant visual noise when some big news item comes up. All I care about is: chats and calls from girlfriend, family, friends (in that order), a couple chess games, calendar/todo notifications to keep me on schedule (particularly on busy days). Everything else, I can check at my leisure. If I had a smartwatch, it'd be convenient to have those on my wrist. But I certainly wouldn't want all those news notifications there, though I may still want them on my iPhone or iPad.
Re:Why we’re betting against real-time team messaging by hackmiester on Monday June 19, 2017 @11:40AM (#14587763)
Well, personally, I use it to let me know there is an urgent notification.

I've never felt the point was for all my notifications to show up.

Re:Why we’re betting against real-time team messaging by XorNot on Monday June 19, 2017 @10:51AM (#14587406)
This is a problem even with email at the moment. I spent about 2 hours today trying to get my email filters to a state where my Inbox would only contain email that was (1) generated by a human and (2) specifically addressed to me.

Github Enterprise is so far the worst offender - I can't find a non-heuristic way to filter user merge messages (which contain the user name) from actual user comments.

Re:Why we’re betting against real-time team messaging by majewsky on Tuesday June 20, 2017 @05:25AM (#14593163)
Aren't these sent from [email protected]?

In our team, some mails are not delivered because Outlook sometimes accidentally autocompletes `John Doe <[email protected]>` instead of `John Doe <[email protected]>`.

Re:Why we’re betting against real-time team messaging by onion2k on Monday June 19, 2017 @09:19AM (#14586684)
And heaven forbid somebody typed "Good morning, @channel" (which happened 20 times per morning per timezone), because then you'd get the dreaded Red Exclamation Mark in the tab.

That isn't a problem with Slack. That's a problem with the way people are using Slack. If the only workable fix is to use a different tool you have a far bigger problem at your company.

I can't fathom how anybody would have been able to work if they had gone as far as allowing notifications to be turned on and make noises at them every time Slack thought something Important Enough To Interrupt You had happened.

All the notifications and noises can be switched off, and the @channel and @here notifications can be ignored on a per channel basis.

Re:Why we’re betting against real-time team messaging by wpietri on Monday June 19, 2017 @09:58AM (#14586979)
> That isn't a problem with Slack. That's a problem with the way people are using Slack.

The notion that tools exist in some sort of vacuum away from users baffles me. Since Slack's only purpose is talking with other people, I don't how one can even theoretically evaluate it separate from usage.

This is a very common thing that happens with Slack. If it were just one team struggling to use it well, you might have a point. But past a certain size, I've only ever seen Slacks that a) have a problem with @channel, or b) have a carefully developed and enforced culture of controlling use of @channel.

I think the sophisticated version of this argument is "only experts should use use complex/difficult/dangerous tools". Which is a reasonable argument when talking about, say, wiring up detonators. But Slack's purpose is to connect everybody in a company. Suggesting that Slack is only for experts is to limit its market to a very small segment.

Re:Why we’re betting against real-time team messaging by onion2k on Monday June 19, 2017 @10:16AM (#14587123)
Imagine your company has a mailing list that goes to everyone (it probably does; most organisations do). In a small company it's fine for anyone to send to it but it's quite annoying and unnecessary so the use of it is discouraged by company culture. As the organisation grows there's a point where the email administrator restricts who can send to it because it would be actively damaging to the email infrastructure if too many people used it, and it'd annoy a lot of people.

Very few people abandon email because their organisation has a mailing list.

Slack's @channel is exactly the same thing albeit on a smaller scale. If it gets too distracting just tell people not to use it so much.

Re:Why we’re betting against real-time team messaging by majewsky on Tuesday June 20, 2017 @05:30AM (#14593184)
I saw this at $work some years ago. Someone sent a mail to a weird mailinglist that I'd never seen before, which for some reason had 98,000 subscribers. Cue the "what is this list, please unsubscribe me" replies, which are of course sent to the mailinglist rather than the original poster.

I don't know the innards of Exchange, but from what I've heard, when Exchange receives a mail for a mailinglist, it makes a copy in each recipient's mailbox. That small thread with maybe 30 "please unsubscribe me" replies brought down the entire company mail system for about half a day. (Well, it didn't really bring it down; it was just busy shuffling copies of mails around.)

Re:Why we’re betting against real-time team messaging by wpietri on Tuesday June 20, 2017 @11:28AM (#14595331)
Sure. And email is circa 50 years old. At this point, given how distributed it is, it's basically impossible to change. It was not designed for the modern environment, so people have compensated with culture.

Slack, however, is new, centrally controlled, relatively easy to change, and frequently updated. So the email analogy doesn't apply at all.

Re:Why we’re betting against real-time team messaging by s_kilk on Monday June 19, 2017 @10:44AM (#14587334)
> The notion that tools exist in some sort of vacuum away from users baffles me

This x1000

Software is developed and used in a social context. We can't disavow responsibility for the effects our Software cause.

Re:Why we’re betting against real-time team messaging by mrisoli on Monday June 19, 2017 @01:37PM (#14588745)
The thing about software is that it enables us to do things we do well faster and more consistently by a large factor, it also causes the things we don't do well to multiply their damage.

My previous workplace everyone had tight deadlines and goals to meet, they were pressured both internally and externally to act in their best interest, this means that everyone believes their problem is top priority even when it's not a priority at all, and Slack makes communication a billion times faster so they bother whoever they can on Slack.

This usually means one of two things, either going to someone directly or blasting everyone on the channels that contain the entire company, this became the default for us and it was hell, at some point people would notify the entire channel because they couldn't find their mug.

IMO what Slack does, in this case, is expose much bigger issues within the structure of the company, these can't be fixed by switching chat apps.

My current company the communication channels and prioritization are very clear, Slack is not a problem, it is a helping tool.

Re:Why we’re betting against real-time team messaging by chrisdbaldwin on Monday June 19, 2017 @10:59AM (#14587456)
Here's why someone may disagree:

Your company has hammers and screw drivers as your tools. If your employees only know how to use hammers, they are going to hammer screws. If your team only knows how to use screw drivers, they will shrug at nails. Hence, the tool is not always at fault for end user error.

Learning how and when it is appropriate to use the tools at hand is important.

Re:Why we’re betting against real-time team messaging by emodendroket on Monday June 19, 2017 @11:27AM (#14587651)
Nobody actually hammers screws because it's obvious how the tools are intended to be used and that isn't it.
Re:Why we’re betting against real-time team messaging by chrisdbaldwin on Wednesday June 21, 2017 @02:59PM (#14606887)
Counter-point: percentage of emails marked as urgent that are actually urgent.
Re:Why we’re betting against real-time team messaging by Karunamon on Monday June 19, 2017 @10:52AM (#14587408)
I don't think anyone said that Slack is only for experts, but a training session or two wouldn't be remiss. Here's how you handle notification preferences, slash commands, and such. Especially for wide deployments among people of varying tech literacy.
Re:Why we’re betting against real-time team messaging by jasonkester on Monday June 19, 2017 @09:23AM (#14586702)
All the notifications and noises can be switched off, and the @channel and @here notifications can be ignored on a per channel basis.

Sounds like a feature that was added in the last 18 months since I last used it. At the time, your options were "every notification about everything, ever" or "no 'notifications' ever, but we'll still helpfully flash the favicon at you all day".

Glad to see there is at least a tiny drip of sanity making its way into the product.

Re:Why we’re betting against real-time team messaging by twobyfour on Monday June 19, 2017 @09:17AM (#14586675)
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.
Re:Why we’re betting against real-time team messaging by mikepurvis on Monday June 19, 2017 @09:30AM (#14586748)
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 by dasil003 on Monday June 19, 2017 @11:04AM (#14587496)
Take a look at the Channel List under Preferences -> Advanced to only show unreads, then combine that with individually muted channels. That's how I have most channels set up so I can passively aware of activity with badges.
Re:Why we’re betting against real-time team messaging by twobyfour on Monday June 19, 2017 @01:08PM (#14588516)
The problem is that instead of having to check every single one of my dozens of muted channels once or twice a day, I'd like them to be highlighted in the sidebar (but not badged!) when unread. Plus it'd be nice to still get notifications of mentions and highlight words in said channels.
Re:Why we’re betting against real-time team messaging by dasil003 on Monday June 19, 2017 @02:21PM (#14589114)
By hiding the ones with unused messages you implicitly tell which ones have new messages because those are the only ones that are visible. It works quite well and enabled me to passively track dozens of channels without being overwhelmed.

As to mentions and highlight words, I don't think there's a solution for that for muted channels. When I developed this technique I would have liked targetted mentions, but not @here or @channel, which, at the time was indistinguishable. However Slack added a per-channel option to Ignore notifications for @channel & @here, which means I might try the above technique without muting the channel.

Play around with it, you might find the settings can be combined in an optimal way once you understand how they all interact.

Re:Why we’re betting against real-time team messaging by twobyfour on Monday June 19, 2017 @05:15PM (#14590525)
But then if you want to start a conversation in a channel with no unreads, you have to go digging for it.
Re:Why we’re betting against real-time team messaging by dasil003 on Monday June 19, 2017 @07:04PM (#14591076)
Command-K
Re:Why we’re betting against real-time team messaging by smileysteve on Monday June 19, 2017 @09:15AM (#14586664)
Half of my team has audio notifications on and nobody seems to n read the @channel warning.