Gloria Mark, a researcher at UC Irvine, spent years following knowledge workers around offices with a stopwatch. What she found was uncomfortable: after a single interruption, the average person takes 23 minutes to return to their original task. Not 2 minutes. Not 5. Twenty-three.

Now consider how many times the average team member is interrupted in a day. Slack messages. Email notifications. Someone asking a quick question. A meeting that ran over. A Jira ticket that just came in. Most teams we talked to estimated 10–15 interruptions per day. The research suggests it's closer to 50.

Why this doesn't feel true

The reason context-switching costs are so easy to ignore is that they're invisible. You don't see lost focus time on a Jira board. It doesn't show up in a sprint retrospective as a line item. What you see instead are the symptoms: tasks that take longer than estimated, sprint health that mysteriously drops, engineers who seem busy all day but ship less than expected.

Context-switching is a silent tax on every hour your team works. The more tools you use, the more channels you monitor, the more meetings you have, the higher the tax rate — and nobody is tracking it.

The compounding problem

Single interruptions are bad. Cascading interruptions are catastrophic. Every time someone switches contexts, there's a chance they don't fully return to the original task. Instead, they partially return — keeping one eye on the new thing, one eye on the old thing, and neither eye on actually finishing either.

This is what causes the peculiar feeling of being very busy while producing very little. You're technically working constantly. But you're never in the deep focus state where hard problems get solved and real work gets shipped.

What actually helps

The research is clear: the only thing that reliably reduces context-switching damage is structural protection of focus time. Not willpower. Not better habits. Not asking people to check Slack less. Structural protection — making it organizationally, tooling-wise, and culturally harder to interrupt deep work than to respect it.

In practice, this means three things:

• Designated focus blocks — periods of time during the day where interruptions are explicitly off-limits for everyone

• Single-task commitment — one task per focus session, surfaced prominently, with everything else hidden

• Async by default — anything that can wait should wait, answered in batch rather than immediately

How Focusly approaches this

We built the focus session feature specifically to address this problem. When you start a focus session in Focusly, the app surfaces exactly one task — your top priority — and nothing else. The timer creates a commitment device: you've started, the clock is running, and the psychological cost of switching is high enough that most people don't.

It's not magic. It's friction, placed in exactly the right spot — between you and the distraction.

Teams that run daily morning focus sessions before opening communication tools report feeling less reactive, shipping more, and finishing sprints with noticeably higher health scores. The math explains why. Protecting even 90 minutes of morning focus time per person, per day, eliminates dozens of interruption recovery cycles before they start.