Slack Is Quietly Killing Your Focus — the Settings That Reclaim Your Day

Slack, like Facebook and TikTok and every other growth-stage consumer or prosumer tool, is built on engagement metrics. The product team at Slack is measured — explicitly — on Daily Active Users, messages per user per day, and session length. This is not evil, but it is a conflict of interest you should be clear about. The defaults are optimised for Slack's success, not yours. The company that pays your salary pays for Slack because they think it makes you more productive. The evidence that it actually does, at the current level of usage, is surprisingly thin.

The research that exists — most of it from the Information Systems journals rather than the popular business press — points at a consistent pattern: Slack reduces the time it takes to ask a simple question, and it dramatically increases the total cognitive cost of being on a team. The net is almost always negative for the individual who receives more Slack than they send. Senior operators, who tend to receive more than they send by a wide margin, are the ones hurt most.

Here are the specific setting changes — most of them buried three levels deep in preference menus — that reclaim the focus Slack defaults have quietly eroded.

The Settings Tier List

Tier 1: Non-negotiable, do these today

These are the settings that account for the majority of the benefit. If you do nothing else, do these.

1. Turn off mobile notifications entirely, except for direct messages and keyword mentions.

Settings > Notifications (mobile). Change "Notify me about" from "All new messages" to "Direct messages, mentions & keywords." This single change eliminates roughly 80% of mobile Slack interruptions. Channels you're in that aren't urgent stop pinging you after-hours. Your evenings come back. Nobody who actually needs you is blocked — they can still DM you.

2. Configure Do Not Disturb for the hours you actually don't want notifications.

Settings > Notifications > Do Not Disturb. Default schedule: 18:30 to 09:00 plus weekends. Slack will automatically mute notifications during these windows. Messages sent during DND are queued and delivered when you return.

The cultural effect is as valuable as the personal one. When your team sees you're in DND, they gradually internalise that sending you Slack at 22:00 won't reach you until morning. Within a month they stop sending at those times. You've reshaped the team's norms by changing one setting.

3. Turn off desktop notifications for the majority of channels.

Click any channel > Notification preferences > Change from default to "Mentions only" for all non-critical channels. Unless a channel is truly where you should be real-time — which is probably two, max — you do not need desktop banners every time someone posts. Mentions only means you're notified when someone @mentions you specifically or @channels the whole group. Everything else waits until you check.

This is the single biggest focus win. Most senior operators have 40 to 100 channels and the default is "Everything pings you." The default is wrong for knowledge work. Mentions-only for 95% of your channels is the correct configuration for anyone doing deep cognitive work.

Tier 2: Meaningful improvements, do these this week

4. Collapse all sidebars except starred channels, DMs, and mentions.

Preferences > Sidebar. Customise the sidebar to show only what you actually need: starred (critical) channels, direct messages, and @mentions. Hide everything else. The sidebar is supposed to be a workspace navigation tool. By default, it's a dashboard of activity that pulls your attention every time something changes.

The counterintuitive result: you'll still find the channels you need, because you can search for them in 2 seconds. The busy sidebar was never helping you navigate; it was making the room feel louder.

5. Use custom statuses to publicly commit to focus blocks.

Set a status like "🎯 Deep work until 11" when you're in a focus block. Slack automatically mutes notifications during custom statuses that include certain keywords. More importantly, it tells your team you're unavailable, in a way that feels polite but clear. People will hold questions until later. The first few days you'll get apologetic DMs from people who forgot. Within a week, they stop sending.

I have three recurring statuses I cycle through: "Deep work until [time]", "In meeting, back [time]", and "Walking, back in 30" for the lunchtime walk. These three cover most of my working week and dramatically reduce casual interruptions.

6. Mute channels you joined once and never read.

Every workspace accumulates channel membership over the years — the short-lived project channel, the team you briefly collaborated with, the social channels you never engage in. Most of these are silently consuming your attention by showing unread counts you'll never clear.

Right-click any channel > Mute. Muted channels don't show unread counts. They're still searchable. You can still post or check them when needed. The visual noise drops dramatically after you mute 20 or 30 channels you'd forgotten you were in.

Tier 3: Advanced, do these next month

7. Schedule messages for receivers' working hours.

Click and hold the send button (on desktop: use the dropdown next to "Send"). You can schedule a message to send later. If you're working late and don't want to interrupt someone's evening, schedule the message for 08:30 the next day. This is a cultural courtesy that senior people should set as a norm — it models the behaviour you want from your team.

The specific discipline: when you're working outside business hours and you finish a message, scheduled-send instead of immediate-send. Ninety percent of the time, there's no reason the recipient needs to see it at 23:17 versus 08:30 the next morning. You reclaim boundary-respect as a team norm.

8. Keyword-specific notifications for genuine priorities.

Preferences > Notifications > My keywords. Add the words that actually represent urgent matters in your domain — your own name (exact spellings and common misspellings), critical project names, specific client names, regulatory terms. You'll now be notified when these words come up anywhere, even in channels you don't actively watch.

This is the inverse of the everything-off default: you're opting into the specific signals that matter and ignoring the general chatter. Set maybe 10 keywords, maximum. More than that and you're back in notification overload.

9. Review and prune memberships quarterly.

Every quarter, look at the channels you're in. Leave the ones you haven't actively contributed to in the last 30 days, unless they're informational channels you actively read. Most of these can go. The specific metric: if you haven't posted in the channel in 90 days and haven't @mentioned yourself-relevant content in it in 60 days, leave. Someone will tell you if you need to rejoin.

The Cultural Move That Matters Most

Settings only get you part of the way. The harder piece is the cultural expectation your team has about Slack responsiveness. In most companies, the implicit norm is that Slack messages deserve a response within an hour during business hours. This norm is insane. It assumes you're continuously monitoring Slack, which means you're not doing deep work for more than an hour at a stretch.

The fix: set and communicate your actual response expectation. Mine is documented in my Slack profile: "I check Slack at 09:30, 13:00, and 16:00. For anything truly urgent, please call or text my mobile."

This sentence accomplishes three things. It tells people when they can actually expect you. It moves genuinely urgent communication to a higher-friction channel (call or text), which filters out most false urgency. And it gives you explicit cover to batch-check Slack rather than continuously monitoring. The few people who actually need you urgently have the escalation path they need.

Senior leaders who can publicly set this expectation for themselves tend to inspire the same behaviour in their teams. If you're senior enough to model it, do so — you're doing your team a favour by signalling that focused work is valued over constant availability.

The Slack-Email-Phone Hierarchy

For any given communication, the sender should be choosing a channel based on urgency and complexity. Most don't. The result is that everything ends up in Slack because it's the lowest-friction channel, and the signal-to-noise ratio in Slack degrades over time.

The hierarchy that works:

• Phone / SMS: genuinely urgent (needs response in next hour) or genuinely sensitive (needs human voice). Use rarely.
• Email: needs to be in writing, needs an audit trail, is longer than three paragraphs, or is directed at more than three people.
• Slack DM: short, informal, quick answer expected within the working day.
• Slack channel: relevant to the group, not time-critical, broadcasting information that others may also want.

Teach this hierarchy, both upward and downward. Call people out gently when they misuse the channels — the stakeholder who Slacks you a seven-paragraph contract question should be redirected to email. Not every time, but often enough to retrain the behaviour.

The Cost of Not Doing This

Researchers at the University of California found that knowledge workers in notification-heavy environments were measurably worse at complex problem-solving than the same workers in notification-controlled environments — by around 40% on some cognitive tasks. The effect wasn't about any single interruption. It was about the ambient cost of anticipating interruptions, which keeps the brain in a low-grade alert state incompatible with deep focus.

Slack is the default notification environment for the modern knowledge worker. Leaving the defaults as they shipped means sustaining an ambient cognitive cost for forty hours a week, five days a week, forty-eight weeks a year. The settings changes above take maybe 90 minutes to configure. The payback is measured in months.

The question isn't whether to configure Slack. It's whether you'll continue paying the default tax. Most people do, quietly, and never realise what it's costing them.