How One Interruption Ripples Across Your Whole Team

When we add up what an interruption costs, we almost always do the math one person at a time. You get pinged, you lose your place, you spend a few minutes climbing back into the problem. Annoying, but survivable. The trouble is that this tidy accounting hides the real damage, because interruptions don't stay politely contained inside one person's afternoon. They spread.

Think about the last "quick question" you fired into a channel. It didn't just land on one teammate. It pulled them out of their work, sent them digging for an answer, maybe nudged them to ping a third person to confirm, and left a wake of half-finished thoughts behind all of them. That spreading wake is what we'll call the Ping Ripple, and it's the reason a team can feel frantically busy while moving strangely slowly.

One Ping, Many Detours

Here's what actually happens inside the person you interrupt. Researchers Saeed Addas and Alain Pinsonneault describe how a single interrupting message triggers what they call a "chain of diversions," where someone doesn't just handle your message and return to work. They process your ping, then notice two other unread things, then chase those, and the original task drifts further away with each hop.

The field data backs this up. In a workplace study by Gloria Mark and her colleagues, people bounced between distinct "working spheres" roughly every 11 minutes, and before returning to an interrupted task they passed through an average of more than two other tasks first. Your one question doesn't cost a teammate 30 seconds. It scatters their attention across a small pile of unrelated work before they ever find their way back.

Why the Cost Multiplies Instead of Adds

A team isn't a stack of separate workers. It's a web of dependencies, and that's exactly why interruptions ripple instead of staying put. Addas and Pinsonneault make this explicit, noting that interruptions aimed at one individual "can also affect other group members through various ripple effects." When you knock one person off their rhythm, anyone waiting on that person inherits the delay.

Modern chat tools pour fuel on this. A 2025 study led by Lukas Toebben points out that instant messaging "has lowered the barrier for interrupting one's coworkers," so the friction that used to make us think twice about walking to someone's desk is gone. The same research line found that heavy interruption exposure pushes time pressure up sharply, with one study putting the increase around 55 percent. More pings means a more rushed, more stressed team, and rushed teams make the kind of sloppy calls that generate even more pings later.

The Synchronicity Tax

The quietest damage shows up in coordination. Addas and Pinsonneault warn that interruption-heavy environments rack up "excessive coordination overhead," which is a precise way of describing the feeling that your team spends more energy syncing up than actually shipping. When everyone's attention is fractured on a slightly different schedule, the windows where people are genuinely free to think together keep shrinking. Call it the Synchronicity Tax.

It gets worse when work never comes back at all. That same body of research found reorientation after an interruption can run anywhere from about a minute to sixteen minutes, and that more than a quarter of interrupted tasks are simply never resumed. Multiply a few abandoned threads across a whole team and you get the thing nobody can quite name: work that was supposedly "in progress" silently evaporating.

Throwing Smaller Rocks

You can't run a team in total silence, and you shouldn't try. The goal isn't to ban communication. It's to be honest about the size of the rock you're throwing into the pond before you throw it. Most "urgent" pings are neither urgent nor aimed at the right person, and a few seconds of thought on the sender's side saves minutes of scattered attention on everyone else's.

Before you fire off the next interruption, run what I'll call the Ripple Test:

• Does this need an answer in the next hour? If not, it's a comment to leave, not a tap on the shoulder. Write it where they'll see it when they surface.
• Am I aiming at the right person, or the convenient one? Pinging whoever's "green" instead of whoever actually owns the answer just adds an extra hop to the chain.
• Can I batch it? Three small questions sent as one message create one ripple instead of three. Hold your minor asks and release them together.
• Did I give them enough to answer in one pass? A vague ping forces a clarifying reply, which doubles the disruption. Front-load the context.

None of this needs a new policy or another app. It needs you to treat your teammates' attention as a shared resource you can deplete, because that's what it is. The reason your team feels out of sync isn't that people aren't responsive enough. It's that everyone's responding to everything, all the time, and the constant spray of small ripples never lets the surface go still long enough for anyone to see the bottom.

Stop asking how fast your team replies, and start asking how rarely it has to.