Why Does Checking Slack Constantly Feel Productive But Leave Me Exhausted?
Written By Aftertone Team
Thursday, May 14, 2026
15 min read
Why Does Checking Slack Constantly Feel Productive But Leave Me Exhausted?
Checking Slack constantly feels productive because responsiveness is immediately rewarded and deep work is not. Every message you send gets a reply. Every question you answer produces visible gratitude. Every thread you close produces a small, measurable sense of completion. Deep work produces none of this. It produces progress that accumulates invisibly over hours, with no feedback until the work is finished. The brain registers the Slack activity as productive because it is producing outputs, however shallow. The exhaustion comes from what that activity is doing to the cognitive architecture underneath.
The variable reward mechanism
Slack is, from a behavioural design standpoint, a variable reward system. Each check might produce something interesting, urgent, or gratifying, or it might produce nothing. This unpredictability is the precise condition that produces the strongest conditioned checking behaviour in behavioural research. B.F. Skinner's operant conditioning work established decades ago that variable ratio reinforcement schedules, where reward arrives unpredictably, sometimes after one check, sometimes after ten, produce more persistent behaviour than fixed schedules where reward is predictable.
This is why Slack is harder to put down than email. Email has a roughly predictable cadence: you know roughly when batches arrive. Slack has genuine unpredictability — something interesting might have appeared in the last three minutes, or might not. The uncertainty drives the checking. The occasional reward reinforces it. The checking behaviour strengthens over time regardless of whether the average check produces anything valuable.
BJ Fogg's behaviour design research is relevant here: behaviour that produces immediate positive feedback strengthens, regardless of whether the long-term outcomes are positive. Each Slack check that produces a response, a reaction, or a resolved thread is immediate positive feedback for the checking behaviour. The long-term cost (depleted attention, shallow output, end-of-day exhaustion) arrives hours later and doesn't register as connected to the checking that caused it.
Why it feels productive: the busyness trap
The feeling of productivity that comes from Slack responsiveness has a specific character. It's the feeling of being needed, being in the loop, keeping things moving. These are genuine contributions in many work environments. Coordination matters, responsiveness is valuable, being the person who keeps threads from dying is a real form of organisational value.
The problem is that this kind of contribution is largely invisible to the cognitive accounting system that evaluates whether a day was well spent. At the end of a day spent primarily on reactive communication, most knowledge workers feel vaguely behind, as if the real work didn't get done, as if there are things waiting that should have been addressed. This feeling is usually accurate. The coordination was real but the deep work wasn't, and the deep work is what the most important outputs require.
Research from the busyness as status symbol literature documents a cultural reinforcement loop: in many professional environments, being visibly busy and responsive is itself a signal of importance and engagement. Checking Slack constantly isn't just personally rewarding. It's professionally legible as engagement in a way that three hours of silent deep work is not. The social reward reinforces the behaviour independently of any individual psychological mechanism.
Cal Newport's framework in Deep Work names this as the busyness proxy: in environments where deep output is hard to measure, visible activity becomes a substitute signal for productivity. Responding quickly to Slack messages is visible and immediate. Writing a complex analysis is neither. The proxy metric, responsiveness, gets optimised at the cost of the actual metric: valuable output. Pseudo-productivity is the more formal name for this pattern.
What it's doing to your attention
The exhaustion at the end of a Slack-heavy day is not incidental. It's the direct output of what continuous checking does to the attentional system across a workday.
Each Slack check is a context switch. You leave whatever you were doing, even partially, even for 20 seconds, to process incoming information. Sophie Leroy's 2009 research on attention residue found that every switch between tasks leaves cognitive residue: partial processing of the prior task that continues running in the background, occupying working memory that the next task needs. A day of constant Slack checking is a day of constant context switching, each generating its own residue, each degrading the quality of whatever comes next.
Kushlev, Proulx, and Dunn's 2016 study measured this effect directly. Participants were randomised into two conditions: one group received phone notifications without restriction (averaging 86 per day), the other checked their phones on a schedule. The unrestricted group reported significantly higher inattention and hyperactivity throughout the day. The notification frequency, not just individual alerts, shaped the cognitive state of the entire workday. Constant checking does not just consume the minutes it takes. It reconfigures the attentional baseline of every hour in between.
The task switching costs research by Rubinstein, Meyer, and Evans (2001) puts a number on the switching overhead itself: up to 40% of productive time lost to switching costs in complex, dissimilar task conditions. A day of alternating between deep work and Slack isn't a day of 60% deep work and 40% Slack. The switching overhead makes the actual deep work fraction significantly smaller, and what does happen in the nominally deep work periods is degraded by the residue from the Slack activity on either side.
The passive cost you're not counting
The exhaustion isn't only from the active checking. There's a passive cost running in parallel that most people don't account for.
Stothart, Tsetsos, and Oberauer (2015) found that receiving a phone notification — without looking at it, without responding — impaired cognitive performance on a sustained attention task to the same degree as actually using the phone. The awareness that messages might be waiting, that Slack might have updated, that something might have been said, this background monitoring consumes attentional resources continuously, even when you're not actively checking.
This is the hidden cost of having Slack open in a background tab. You're not looking at it. You're not being distracted by it in any obvious sense. But part of your attention is tracking it — monitoring the tab for a badge update, processing the possibility that something has arrived. That monitoring process runs on the same attentional substrate you need for the work in front of you. It's not free. It doesn't pause when you're trying to concentrate. It runs throughout the day, depleting the attentional resource steadily, invisibly, until the end of the day when the depletion is total and you can't fully account for where it went.
Baumeister's ego depletion research — the finding that self-regulatory capacity depletes with use across the day, drawing from the same finite cognitive resource — provides the mechanism for why the exhaustion is specifically mental rather than physical. You haven't done hard physical work. You've done hundreds of small acts of attention-switching, impulse-checking, and context-shifting. Each drew from the same pool. The pool is empty. That's the exhaustion.
Why you check even when you know you shouldn't
The checking behaviour persists even when you're consciously aware it's counterproductive. This isn't a failure of knowledge. It's the nature of habitual behaviour that has been reinforced across hundreds or thousands of repetitions.
Phillippa Lally's habit formation research at UCL found that habits take an average of 66 days to form — some as few as 18 days, some as many as 254, and that established habits operate largely automatically, outside conscious deliberation. A checking habit built over months of work in a Slack-driven environment isn't going to be overridden by deciding to stop. The automatic behaviour fires before the deliberate decision has a chance to intervene.
Implementation intentions help here specifically. Gollwitzer's research found that forming a concrete if-then plan — "If I feel the urge to check Slack before 11am, I will write the urge down and return to the current task" — provides a pre-committed decision that the automatic habit encounters before acting. The if-then plan intercepts the behaviour at the triggering moment rather than trying to suppress the habit generally. It's more effective than resolution precisely because it operates at the same automatic level the habit does.
The email batching evidence
The closest experimental research to Slack behaviour comes from studies on email checking, which has a similar variable reward structure and similar attention costs. Kushlev and Dunn's 2015 RCT found that limiting email checking to three times per day (versus checking continuously) reduced daily stress (effect size d=0.45) and reduced distraction (d=0.51), with no significant difference in productivity or responsiveness as measured by the study. The batching reduced the attentional cost without reducing the actual output.
The mechanism is straightforward: batching converts dozens of micro-switches into two or three deliberate switches. Each deliberate switch still has a residue cost, but the total switching overhead for the day is a fraction of the continuous-checking alternative. The email batching research applies directly to Slack: the cost comes from the frequency of switching, not from the medium or the content.
The practical translation: two or three Slack windows per day — specific times when you process all pending messages, respond to what needs responding to, and then close the application — produces the same responsiveness outcomes as continuous checking with a fraction of the attentional cost. The anxiety that you'll miss something urgent is real but, in most environments, empirically unfounded: genuinely urgent communications find another route when people know Slack isn't monitored continuously.
What actually helps
Scheduled Slack windows, not continuous monitoring. Pick two or three times — 9am, 1pm, 4pm is a reasonable starting structure, and process all pending messages at each. Between windows, Slack is closed, not minimised. The badge count is invisible. The passive monitoring cost drops to near zero.
An auto-response that sets expectations. Most of the anxiety about batching Slack comes from the social expectation of responsiveness, not from actual urgency requirements. A status message or auto-response stating when you check messages handles 80% of this: the expectation is set, the monitoring pressure dissipates, and the social cost of not responding immediately is eliminated by the fact that you've communicated your schedule.
A genuine escalation path for actual urgency. The common objection to batching Slack is that occasionally something genuinely urgent arrives. The answer is not continuous monitoring for the rare urgent case — it's a separate, faster-response channel for genuinely urgent communications. Phone call. Direct text. A specific protocol for emergencies that everyone understands. This separates the genuine urgency problem from the habitual checking problem and allows each to be addressed on its own terms.
Protect your cognitive peak hours specifically. The damage from continuous Slack checking is not uniform across the day. Checking during your biological cognitive peak — the hours when deep focus is most available — is the highest-cost checking. Checking during your trough (early afternoon for most people) is lower-cost because the alternative wasn't deep work anyway. If you can only batch Slack for part of the day, batch the morning.
Track what a batching day actually produces versus a checking day. The planned versus actual comparison is the most persuasive evidence available for changing the behaviour, because it makes the cost concrete. Most people don't realise how much output difference exists between a continuously-checked day and a batched day until they've tracked both. The productivity difference is usually significant enough to overcome the social anxiety about responsiveness.
Aftertone's Focus Screen removes Slack from the visual environment during focus sessions as part of a broader principle: the cognitive cost of a visible, potentially-updating communication tool running in parallel with deep work is real enough to be worth eliminating by design. Not by discipline — by removing the stimulus from the environment so the checking impulse doesn't have anything to act on.
Frequently asked questions
Why does checking Slack constantly feel productive?
Because responsiveness is immediately and visibly rewarded in ways that deep work is not. Each message answered produces visible output, gratitude, and a sense of completion. Deep work produces progress that accumulates invisibly over hours, with no feedback until the work is finished. The brain registers the Slack activity as productive because it is producing outputs — just shallow ones. Behavioural research on variable reward schedules explains the checking behaviour itself: unpredictable rewards (something interesting might have appeared) produce stronger and more persistent checking than predictable ones.
Why am I so tired at the end of a day spent on Slack?
Because each Slack check is a context switch, and each switch generates attention residue and consumes self-regulatory capacity. Kushlev et al. (2016) found that 86 notifications per day (roughly the average) produced significantly higher inattention and hyperactivity throughout the day than scheduled checking. Baumeister's ego depletion research explains the exhaustion mechanism: self-regulatory capacity is finite and depletes with each act of attention-switching, impulse-checking, and context-shifting. A day of continuous checking empties that resource. The exhaustion is specifically mental because the resource depleted is specifically cognitive.
Is Slack more addictive than email?
Yes, in the sense that it's more reinforcing. Email has a roughly predictable cadence — batches arrive at intervals you can roughly anticipate. Slack has genuine unpredictability — something interesting might have appeared in the last three minutes. This unpredictability maps directly onto the variable ratio reinforcement schedules that behavioural research identifies as the most behaviour-strengthening. The checking behaviour becomes habitual faster and is harder to interrupt than email checking, for the same reason.
What happens if I batch Slack and miss something urgent?
Kushlev and Dunn's 2015 email batching RCT found no significant difference in productivity or responsiveness between continuous checking and three-times-per-day batching as measured by the study. The anxiety about missing something urgent is real but empirically unfounded in most environments — genuinely urgent communications find another route when people know Slack isn't monitored continuously. The practical solution is a separate escalation channel for actual emergencies (phone call, text message) that everyone understands, separating the genuine urgency case from habitual checking.
How many times a day should I check Slack?
The research on email batching (the closest experimental proxy) found that three times per day reduced stress and distraction significantly with no productivity cost. Two or three Slack windows per day (morning, midday, late afternoon) is a reasonable starting structure for most knowledge workers. The specific times matter less than the principle: between windows, Slack is closed rather than minimised, the badge count is invisible, and the passive monitoring cost drops to near zero.
