'I'll just check quickly' is one of the most common phrases in modern work, and it's built on an intuition that a brief glance at a notification is low-cost precisely because it's brief. The research discussed elsewhere on this shelf — on context-switching cost and on attention residue specifically — suggests the intuition is wrong in a specific, measurable way: the cost of a check isn't proportional to how long the check itself takes, it's driven largely by the reorientation before and after it, which doesn't shrink much just because the check was fast.
Why a fast check still has a slow cost
Even a two-second glance at a notification requires disengaging from the current task's mental context, processing the new information, deciding whether it needs action, and then re-engaging with the original task — and that re-engagement step is where most of the real cost sits, independent of how quickly the notification itself was read. A notification that turns out to require no action at all still triggers this full cycle, which is why 'just checking' rarely turns out to be free even when the check itself confirms there was nothing to do.
This is compounded by the fact that many notifications are, by design, engineered to be maximally interesting or urgent-seeming regardless of actual importance — a badge count or a preview snippet is built to generate a check, not to reflect the genuine urgency of what's behind it, which means the frequency of 'necessary' checks is often higher than the frequency of genuinely necessary ones. For a practical software example related to how Microsoft Teams tracks activity, visit this page.
Triage as a scheduled activity, not a constant background process
The alternative to constant, ad hoc checking is scheduled triage: designated windows, a few times a day, dedicated specifically to processing notifications and messages, with the explicit expectation that nothing gets checked outside those windows except a small, clearly-defined category of genuinely urgent channels (a phone call, a specific flagged alert). This converts an unpredictable, constant stream of small interruptions into a bounded, predictable cost that happens at a chosen time, rather than whenever the notification happens to arrive.
- Batch notification checking into 2–4 scheduled windows per day rather than responding to each one as it arrives.
- Reserve real-time interruption only for a small, explicitly defined category of true urgency — most channels don't qualify, even if they feel urgent when they arrive.
- Turn off previews and badge counts where possible — the visible hint of new information is often what triggers the urge to check, independent of the notification's actual content.
- Tell frequent contacts about the triage schedule explicitly — an unexplained slower response time reads as unreliability unless the practice is communicated.
The social cost that makes triage hard to adopt
The biggest practical obstacle to scheduled triage isn't the individual's discipline, it's the surrounding culture's expectation of near-instant response, which can make a genuinely well-designed triage schedule feel risky to adopt unilaterally. This is one of the areas where individual focus discipline runs into a team-level problem — discussed in more detail in the team and remote-work section of this shelf — and where the fix often has to be partly social (setting expectations explicitly) rather than purely personal.
Scheduled triage doesn't eliminate the cost of processing notifications — it concentrates that cost into predictable windows instead of spreading it, unpredictably and repeatedly, across every deep-work block the rest of the day was supposed to protect. For additional background on this subject, consult Microsoft Outlook support.