I want to say something that's going to sound ungrateful,
because Slack genuinely is a better product than what it
replaced.
But here it is anyway: Slack may be the single most
expensive productivity tool your company pays for and
not in the way the invoice shows.
A brief history of how we got here
Email had a problem. Everyone agreed on this. Email was slow,
threaded replies were chaos, searching was terrible, and the
formality of it created unnecessary friction for quick
questions. Slack arrived and fixed all of that. Channels
replaced inboxes. Threads replaced reply-all hell.
Search actually worked. Messages felt lightweight.
And then, quietly, something shifted.
The thing that made Slack feel better than email, the
real-time, always-on, instant-response nature of it, turned
out to also be the thing that made it dangerous. Email's
slowness was annoying. But it also created natural gaps.
You sent something. You waited. The other person had time
to think. You got a considered response.
Slack collapsed those gaps entirely. And in doing so, it
quietly established a new norm: if you're online, you're
available. If you're available, you should respond. If you
don't respond quickly, something must be wrong.
Most dev teams didn't decide on this norm. It just... formed.
And now it's load-bearing.
What Slack actually costs per interruption
Let me be specific, because this is where the conversation
usually stays vague and shouldn't.
The research on interruption recovery in knowledge work is
fairly consistent: after an interruption, a notification,
a tap on the shoulder, a Slack ping, it takes an average
of 20 to 25 minutes to return to the same level of
cognitive engagement you were at before it happened.
Twenty-five minutes. For one ping.
Now think about a typical developer workday. How many Slack
Do notifications arrive between 9 am and 6 pm? For most people
On active teams, it's somewhere between 30 and 80. Even if
You only look at a fraction of them, even if you have
notifications muted, and you only check voluntarily the
ambient awareness that messages are arriving, that your
name might have been mentioned, that something might need
You are a persistent low-level pull on your attention that
doesn't fully let you settle.
You never get the 25 minutes back. You get approximations
of focus, interrupted before they deepen into the real thing.
// What your calendar shows:
9:00 am - 12:00 pm: Focus time (3 hours)
// What actually happened:
9:00 → started reviewing PR
9:07 → Slack ping, glanced at it, "not urgent"
9:09 → tried to find a place in PR again
9:14 → actually back in it
9:23 → Slack ping, channel message, responded quickly
9:26 → back to PR, forgot the comment I was about to leave
9:31 → finally back in flow
9:38 → standup reminder notification
...
// Actual focused work in that "3-hour block": ~40 minutes
This isn't exaggerated. This is Tuesday.
The async illusion
Here's the thing that makes this particularly hard to fix:
Slack is technically an async tool. You're supposed to
be able to respond in your own time. Nothing is forcing you
to answer immediately. The notification can wait.
And yet almost nobody treats it that way in practice,
because the culture around the tool doesn't match the
tool's intended design.
When your team lead sends a message at 10 am, and you don't
respond until 2 pm, something happens. Maybe nothing explicit. No one says anything. But there's a friction. A vague
sense that you were "offline" or "unresponsive." In enough
teams, that friction quietly shapes behaviour until
"checking Slack regularly throughout the day" stops feeling
like a choice and starts feeling like a professional
obligation.
The async tool became a synchronous expectation.
The synchronous expectation became a constant interruption.
The constant interruption became the default work environment
for a generation of developers who wonder why they can't
focus.
The senior dev paradox
Here's something I've noticed that doesn't get talked about
enough: the developers who seem most productive on high-
Functioning teams are often the least responsive on Slack.
Not because they're antisocial. Not because they don't care
about their teammates. But because at some point, usually
after getting burned enough times, they made a quiet,
A deliberate decision to treat Slack the way it was supposed
to work: asynchronously, in batches, on their schedule.
They check it twice a day. They respond thoughtfully. They
miss some real-time conversation. They ship more code than
almost anyone else on the team.
The junior developers, trying to demonstrate availability
and engagement, have Slack open in a pinned tab all day.
They respond to everything within minutes. They're
"always there." And they wonder why their focus sessions
never feel real, why the complex ticket always takes longer
than it should, and why they leave work exhausted but feel like
they didn't get much done.
This is not a coincidence. It's cause and effect.
What actually helps (without quitting your job or burning your laptop)
I'm not going to tell you to delete Slack. That's not your
call to make unilaterally, and the tool itself isn't the
problem, the culture around it is.
But there are things within your control:
Close the tab. Actually, close it.
Not minimise. Not mute. Close. When you're in a focus
session, Slack should not be a running process competing
for your peripheral attention. It will be there when you
get back. Your teammates will survive 90 minutes without
an acknowledgment emoji from you.
Set visible status messages and use them seriously.
"🎯 Focus until 11 am, will check messages then" is
not antisocial. It's information. It tells your team
what to expect so they don't interpret silence as absence.
Most people never bother with this and then wonder why
people assume they're always available.
Batch your Slack sessions like you batch your deploys.
Two or three defined windows per day where you read and
respond to everything that has accumulated. Outside those
windows, the tab is closed (see above). This feels
radical for about three days and then becomes the most
normal thing in the world.
Have the conversation with your team explicitly.
The norm that everyone must be responsive didn't
Get established through a meeting. But it can be
challenged through one. "Hey, I'm experimenting with
checking Slack at 10, 1, and 4, if something's urgent
use @here or message my phone" is a sentence that, said
Once, changes the dynamic more than any personal
A productivity system can operate on its own.
And finally, this is the one I find most useful: the change that happens when you open a new tab during a focus session. The Slack-checking impulse almost always starts with opening a new tab, which then goes to Slack, which was already loaded. I ended up building Ashdeck partly for this reason; it replaces the new tab with a focus workspace, so the automatic "open a new tab to check something" reflex lands on your current task and Pomodoro timer instead of Slack. The reflex still fires. But what it lands on has changed.
The thing worth saying out loud, Slack didn't make you less focused. The expectations that formed around Slack did. Unlike the tool itself, those expectations are at least partially within your influence to change.
The most focused developers I know didn't find a way to
work harder despite constant interruptions. They just
quietly stopped accepting constant interruption as a
given. They pushed back. They set norms. They let some
things wait.
Their work improved. Their stress dropped. Their teammates
adjusted. The culture is not as fixed as it feels from the inside, but you have to actually push on it to find that out.
If this resonated, follow along. I write about productivity,
focus and attention, usually after embarrassing myself
first. I'm the founder of Ashdeck.com, which transforms your new tab into a personalized workspace to block distractions and structure your work sessions.
Top comments (0)