Organize your Slack channels by "How Often", not "What"

Why can't slack let me do something in between muting a channel or notifying me of every new message? Like, perhaps for some channels I want to read every message, but it's not time critical, so it would be nice if it only became "unread" once a day if it has new messages since last time.

I organize mine by SCP object class. Safe is anything I can ingore, Euclid is anything I should keep an eye on. If a message means something broke down and requires immediate attention, that's Keter. (If I'm posting that something broke down, then that's Thaumiel.)

I have a bunch of groups from top to bottom:

   - Channels incidents I'm in right now
   - Incidents others are working on. Our Team channel we'll be called out
   - Channels for my team
   - Other monitoring and alert channels to keep an eye on 
   - Announcements from my group, diversion, etc
   - Ongoing Issues. Incident investigation
   - Ongoing Projects
   - Issues from earlier this month (move for the top two group once resolved)
   - 3 groups of issues from 3 previous months
   - Other teams public channels I read when I have time
   - Some random internal channels
   - Other teams channels I ignore but need to join sometimes to ask their help

Slack is dismantling what I've spent decades honing my email filters for and there's no analogue.

I'd sort of roughly approached this technique with my own channel organization over time without thinking about it systematically, but this is a helpful crystallization of what I'd been trying to achieve. I'm glad this was posted.

Definitely agree with others that Slack needs a richer selection of notification mechanisms, both for new content in channels and for mentions. For mentions, there's no level between "I demand immediate attention from this person" and "the characters that make up this person's name happen to be in the text of my message."

I do something similar to the OP, but there's an additional critical hack - you have to sort your Unreads view (cmd-shift-A) by the order of the channels in your groups, which is not the default setting. Then, when you you hit cmd-shift-A, you pay close attention to the initial messages from the channels close to the top (i.e. the stuff that requires your immediate attention) before hitting Escape to mark them read. Eventually the Unreads view starts to show you bullshit that you don't really need to pay attention to, and you can basically spam the Escape key to mark everything read, after maybe skimming it slightly so you see there wasn't anything of interest. Also, be pretty aggressive about muting support channels where you're not among the group of people expected to provide support.

This makes Inbox Zero in Slack easy and I don't understand why it's so difficult for other people to do it.

(currently working in a Fortune 500 with membership in probably thousands of channels, only maybe 20-30 of which are actually relevant to my daily work).

I've arrived at this organisation method on a number of platforms, essentially sorting contacts into a set of priority lists, usually just three: high, medium, low, or A/B/C, whatevs.

I'll often also pin a specific search term of interest for a topic I'm following for the moment, but don't plan on subscribing to.

Most of the time my streams are then the A & B lists plus a topic of interest. Very rarely more than that. If anything vital turns up I'll generally see it one way or another. Every so often (a few times a week/month/year) I'll glance at the lower-priority lists.

I've also made a point of putting highly-voluble sources in their own channel, and then ... ignoring that. This keeps them from dominating other streams, their good stuff (usually infrequent) tends to show up elsewhere through re-shares, and my own QoL is generally improved.

Whenever the experience starts to get too annoying, I start pruning from my high-priority lists. Less is more. No news is good news.

My current slack channel organization:

- Channels I care about: ones where real work gets done every day, eg my team channels, other people I interact with frequently and directly.

- Temporarily important: short lived channels, or project channels that aren't as frequently actionable as the first category. Eg, I am struggling with some build issue so I join the public channel for the team that owns that process until I resolve my issue.

- Channels I need to follow: I don't really care too much about this, but partners or stakeholders are in them and sometimes say things I should know about or ping me or will add me if I leave, so I need to somewhat monitor it.

- Channels not really about me: Broad-based channels about company strategy, etc. In theory I guess they impact me since its about what the org, or my part of it, is up to, but tbh it doesn't actually impact me materially.

- Channels I may leave soon. Basically recycle bin, before I leave channel entirely.

Huh, I never thought of it that way but we sort of have that, just that it's two entries instead of a whole list of frequencies. There's a general chat that you can read whenever~never (participate as much as you want), and one that you are supposed to read (also after a holiday, you're meant to read what was announced). Taking a peek every now and then throughout the day is fine (most days there's 0-2 messages in it). It's basically email whereas the other chat is 'chat'

And of course, if someone needs you specifically, they'll @mention or PM you

Not sure why you would need a four-tiered scheme of frequencies for this

I don't want to organize ... I just want a filter on the channel sidebar!

Feature request:

Disable multi-DMs

If you need to message multiple people, it goes in a public/private channel (existing or new)

I use Teams but I usually just leave on read as a signal to get to it later when I have time. I have notifs muted. But I'm also not pinged so often that I need tactics like this article. Good stuff.

Naturally gravitated to this somewhat over the course of the past six months, but this nails down exactly how I want to approach channel structure.

I'm surprised people are still using work chat like this.

My workplace switched to Teams about 5 years ago. The app is of course janky and slow, but it had the side effect of pushing all the important conversations to emails and scheduled meetings.

Teams integrates with Outlook well enough that I never have to second guess my schedule and all the chatter is now just DMs, informal group chats that I would actually care about, and a bunch of broader group channels that nobody is expected to look at very often (not even every day).

I rarely feel distracted by chat anymore unless it makes sense because something is actually on fire.

Even with OP's kind of sorting, office chat products conceal the priority of any given message to trick you into more participation. The "purpose of a system is what it does" style thinking can get carried away, but more than 99% of the messages in places I will be expected to notice things that require same day attention, don't. The goal is to waste my time.

I rarely have >3 unscheduled conversations in a day that couldn't wait until tomorrow morning. They just never come from the same place.

It's a yappers paradise. They wouldn't include me on an email where they deliberately have to pick participants, but think the serendipity will occur down the road justifies forcefeeding me whatever bullshit they're working on just in case.

Slack was created by Silicon Valley insiders and enjoyed a smooth rise to fame and prominence, so it has led me to ask for years, is it a project of the Church of Subgenius?

Of course, prominent Subgenius adherents may not tend to acknowledge their "faith" outside of pseudonym-based posting on Usenet or other media, but the intersection of irreligious techies working on a project/company named for their central tenet seems too much coincidence to be an accident.

If Slack's chat service sort of destroys productivity and ruins workplace hierarchies and relationships by design, it seems that it is achieving the goals of the formerly "parody religion" and introducing more "Slack" to the world in the process. Mission accomplished, Bob?

[flagged]

It definitely depends on the nature of your work, but the notion of having a channel I need to check hourly makes me ill. If I’m needed I should get a notification, and if I’m involved in an active discussion, I’m there. Otherwise I’ll catch up on a daily basis.