Cost of Workplace Interruptions

A workplace interruption costs far more than the minute it takes to answer, because your attention does not snap back the instant the interruption ends. There is a second cost, the time and effort to rebuild the context you lost, and it lands on every single interruption whether the question took ten seconds or ten minutes. Measure only the reply and you undercount the damage badly.

Here is the frame worth holding onto. This cost is not shared evenly. Some people spend their day getting interrupted with questions, and some people have someone holding those questions for them. The second group looks more focused and more senior. Often the difference is not discipline. It is cover, and cover was never handed out to most people.

The cost is not the minutes

Think about the last time you were deep in something hard and a message pulled you out. Answering took a moment. Getting back to where you were took much longer. You had to reload the problem, remember what you were about to do, and rebuild the fragile thread you were following. That reload is the hidden line item, and it is usually bigger than the interruption itself.

This is why "it was just a quick question" is misleading. The question was quick. The recovery was not. A day full of quick questions is a day where you never actually reach the deep state where hard work happens, because you keep getting knocked back to the shallows. The tally that matters is not the minutes spent answering. It is the good hours you never got to have.

The volume is the real problem

Now put the refocus cost next to the volume. Microsoft has found that knowledge workers face roughly 275 interruptions a day. You do not need any further number to feel the weight of that. If even a fraction carry a real recovery cost, the day is shredded into pieces too small to do anything demanding in.

And a large share of those interruptions are not urgent and not hard. They are people asking something you already know: where a file lives, what you decided, whether they can proceed. Each one is trivial to answer and expensive to absorb, because the cost is in the switch, not the answer. That is the class of interruption worth attacking first, because it is high volume and low value. We wrote about why piling on more tools makes this worse rather than better in status update fatigue.

Who pays this cost, and who does not

Watch who actually eats these interruptions. A senior leader with support does not field the "where does this live" questions, because someone answers them first. Their day is protected precisely at the point where everyone else's day is being chopped up. So the cost of interruptions is not a flat tax. It falls hardest on the people without cover, which is almost everyone.

That is the quiet unfairness in every productivity conversation. We tell people to protect their focus as if focus were purely a matter of willpower. But the people who protect it best usually had help. We pulled that apart in how executives actually protect focus time and in who is allowed to be unavailable. The interruption cost is real for everyone. The cover that offsets it was rationed.

Removing interruptions at the source

You cannot make hard interruptions disappear, and you should not want to. But the high-volume, low-value kind, the ones asking something you already answered, can be removed at the source. If those questions get answered without reaching you, the switch never happens and the recovery cost is never paid.

That is what StandIn does. You write down your standing answers and decisions once. When a teammate needs one of those, they ask your StandIn and get the answer in your words, from your record, whether you are heads-down or offline. When the answer is not written down, it says so instead of guessing, so nobody gets a confident wrong reply. The routine questions stop reaching you, and the good hours you were losing to them come back. If you want to see the shape of your own interruption load, our piece on the timezone tax shows how the same cost compounds across a distributed team.

Common Questions

How much does a single interruption really cost?

More than the time to respond, because refocusing on demanding work takes real effort after every break. The exact recovery time varies by person and task, so the honest answer is that the reply is the small part and the reload is the large part. Counting only the reply understates the cost.

Are all interruptions equally expensive?

No. An urgent, genuinely hard question can be worth the switch. A routine "where does this live" question is almost pure cost, because it is easy to answer and still breaks your focus. The routine, high-volume kind is where the waste concentrates, and it is the kind worth removing first.

How do I actually reduce interruptions?

Cut the ones that ask what you have already answered. If those questions can be answered from a record of your decisions, in your words, without reaching you, the interruption never happens. That leaves only the genuinely new questions, which are the ones worth your attention anyway.

An interruption costs the reply plus the recovery, and with hundreds a day the recovery is where your best hours go. The people who feel it least had cover; most people never did. StandIn removes the routine interruptions at the source: it answers from what you wrote down, in your words, and never guesses. See what the interruptions are costing your team.