What Two Interruptions An Hour Do To A Day Of Work

Nobody on your team thinks they are interrupting anyone. Everybody on your team feels interrupted. Both are true, because each individual interruption is small and the total is not.

Two interruptions an hour is roughly sixteen a day. If each one costs ten minutes of getting back into the work, that is over two and a half hours gone from a working day, before counting the interruption itself. Run that arithmetic with your team's own numbers and the case for changing habits stops being a matter of preference.

Do the sum yourself

Do not use my numbers. Use yours, because arguing about a figure from an article is a way of avoiding the conclusion.

Ask two questions in your next team meeting.

• How many times were you pulled out of a piece of work yesterday.
• How long does it take you to get properly back into it afterwards.

Most people answer the second within a few minutes of accuracy, and the answer is usually longer than managers expect. Multiply the two. Then multiply by five for the week.

Do it out loud, on a whiteboard, with the team watching. The number is more persuasive when everybody helped produce it than when it arrives as a claim.

Why the recovery time is the expensive part

A two minute question does not cost two minutes. It costs two minutes plus however long it takes to rebuild the state you were holding.

That state is real work. Which file you were in, what you had already ruled out, the shape of the thing you were halfway through explaining to yourself. An interruption deletes it, and rebuilding it is slow and tiring.

This also explains why interrupted days feel disproportionately exhausting. You did the hardest part of thinking several times over and got credit for none of it.

The three agreements that buy the time back

You cannot ban interruption and you should not want to. Some questions genuinely need answering now. What you can do is change the default.

One. A protected block, same time every day, for everyone.

Pick a window, two or three hours, and make it a no meeting no message block across the team. The same window for everyone matters, because if everybody protects a different time, everybody is still available to interrupt somebody.

Two things make it hold. Nobody, including the lead, books over it. And it is on the calendar as a real event rather than an understanding. Protecting it sometimes means saying no without sounding difficult.

Two. Ask in writing first, by default.

Most questions do not need an answer within the minute, they need it within the day. Written questions let the receiver answer at a natural break instead of mid thought, and they let a third person answer if they know.

The rule to write down: ask in a channel and wait a working half day. If it is genuinely blocking, say so in the first line and name who you need.

Three. Batch the answering.

The other half of the deal. If people write instead of tapping shoulders, someone has to actually read. Two fixed times a day for clearing questions is enough, and the person answering keeps their own blocks intact. Name a second answerer for the days the first is away, because leave requests and delivery dates are rarely checked against each other.

Without the third agreement the first two collapse, because people learn that writing gets no reply and go back to interrupting.

Interruptions you are doing to yourself

Not all of them come from other people.

• Notifications for every message. Turn them off during blocks, not on principle, just during the block.
• Checking email between tasks, which is where a five minute gap becomes forty.
• Keeping the chat window visible. Peripheral movement is an interruption even when you do not act on it.
• Working on two things at once and calling it efficiency. Three at once is the version where nothing actually ships.

Run the same arithmetic on these. Many people find the self inflicted count is higher than the external one, which is uncomfortable and useful.

What to measure afterwards

Do not measure hours worked. Measure whether things finish.

Before you start, write down how many items your team completed in the last two weeks. After a month of the three agreements, count again. Also ask one subjective question: did last month feel less exhausting. Both numbers matter, and the second one is why people will keep doing it.

Start with one block

If three agreements is too much to introduce at once, introduce the first. Pick tomorrow morning, block two hours for the whole team, and see what gets finished.

One good block a day changes the week more than any tooling decision you are considering.