Live data from Hacker News

Ask HN: What to do when Slack gets too disruptive?

news.ycombinator.com

21–30 of 45 posts

Re: Ask HN: What to do when Slack gets too disruptive?

#22
post #12

Earlier quoted context omitted.

Did you install slack on your phone? Never install slack on your phone. Uninstall slack from your phone. It's a matter of life or death and I am not even kidding.

Could you elaborate? I'm particularly interested in the matter of life or death bit :).

There is a poison dart in your phone, a la. Raiders of the Lost Arc. Every time you open the slack app, there is a 1 in 10^16 chance of that arrow shooting out and killing you. I think it's in the speaker grill and it usually points downward, if you know what I mean.

Re: Ask HN: What to do when Slack gets too disruptive?

#24
post #5

I'm finding this more and more during my off hours. I wish there was a way to opt out of all @channel announcements on my phone app and still get notifications for when someone tags me directly (when I'm actually needed). Probably not a helpful answer to your question, but I feel your pain, at any rate.

You can ignore @channel and @here on a per channel basic. It's under Notification Preferences in a channel. I think it applies to both desktop and phone though.

> I think it applies to both desktop and phone though.

Yeah, unfortunately that's the problem. It's probably worth doing what you suggest for multi-day vacations though (and un-doing when I'm back to my desk).

Re: Ask HN: What to do when Slack gets too disruptive?

#25

I have it set to only notify me on direct messages or mentions for all channels. It's significantly reduced the number of distractions on a daily basis.

This. Also, I've muted all channels that I read to generally stay abreast of what's going on in the company but rarely to never need to actively participate in. And #random.

If you (or you and a group of allies) have the ability to influence your company's Slack culture, the following can help.

1) No one should ever @channel unless they absolutely positively need everybody's attention immediately that very moment. "The website is down! All hands on deck!" "There's a rabid raccoon loose in the office! Evacuate!" @here is slightly less awful but should still be used sparingly.

2) If you need someone's attention, @mention them. If you do require a group's attention, @here the appropriate channel. If you do this consistently, people can disable notifications for non-mentions and assume that any channel that has unreads but no mentions may be read at their leisure - instead of having to constantly keep up with dozens of conversations.

3) Use and teach people to use highlight words so they can get notifications of conversation topics that require their presence, and ignore other unread channels.

4) Set aside a channel or two for global or large-group announcements that aren't necessarily urgent. "We're ordering t-shirts. Tell the office manager what size you want." "Our phone system has a scheduled outage next Tuesday from 2-4pm."

5) The larger your organization and the busier your Slack, the more granular you need your channels to be. For instance, in a company of 5-10, you might have a single channel for all discussions of product, and another for sales, marketing, and partnerships. In a larger company you'll need to separate out channels for client vs server engineering; for engineering vs design; for engineering and design vs QA, and more. Don't make your designers try to filter out what content is relevant for them in a combined design and engineering channel or force your QA folks to ignore a whole bunch of technobabble in order to find the discussions that are relevant to them. Don't be afraid to break out project-specific channels too. If a conversation crosses boundaries, only then bring it to a more general channel.

Re: Ask HN: What to do when Slack gets too disruptive?

#26

Try Twist: https://blog.doist.com/why-were-betting-against-real-time-te...

Looks cool although I think the article is overblowing the negatives of Slack-esque communication and underselling the benefits. Especially considering he was highlighting more about communication issues his team is facing that probably could have been addressed without switching tools.

Re: Ask HN: What to do when Slack gets too disruptive?

#27
post #11

Your best bet might be to be less responsive on Slack — not only by not responding to everyone immediately, but by not responding to some Slack messages at all. If it's important, the person who pinged you can submit their request via another medium, hopefully in a longer form format like email or bug report that's more thoughtfully considered and thoroughly researched, and which you can reply/fix quickly without spe…

Deep Work is absolutely fantastic! I can already feel the difference in productivity just one week into practicing its strategies. I did three things to Slack after reading it:

1. Mute channels aggressively.

2. Snooze notifications often during the day.

3. Disable the red dot badge icon in the Slack app for any new messages (including the ones not addressed to you). This was the biggest source of distraction for me in Slack.

Re: Ask HN: What to do when Slack gets too disruptive?

#29
post #23

CMD + Q. Try it sometime. It's an effective shortcut.

Snarky answer does not take mobile devices into account.

Turn off all Slack notifications for mobile and make it a "Pull" interaction with the service vs. a "Push" interaction.

It's what I do with a lot of services these days. I'm selective about what services can actually push to me.

Examples of services that are important enough to push to me include iMessage (large group chats muted), Uber/UberEats, Lyft, Instacart, etc. Basically notifications that are immediately actionable or important in the moment. Lots of delivery services fall into this category.

Re: Ask HN: What to do when Slack gets too disruptive?

#30
post #26

Try Twist: https://blog.doist.com/why-were-betting-against-real-time-te...

Looks cool although I think the article is overblowing the negatives of Slack-esque communication and underselling the benefits. Especially considering he was highlighting more about communication issues his team is facing that probably could have been addressed without switching tools.

There is no communication issue that cannot be addressed with Slack, because Slack imposes almost no structure on its users. That doesn't mean you want to use it for issue tracking. I think of Slack as UDP for humans - it's very powerful, but it's something you have to make work. If a higher-level communication protocol already exists that fits your needs, might as well use it.
Post reply on HN