The real cost of context switching in operations

An operations team rarely loses a whole hour at once. It loses time in fragments: a message that pulls someone off a task, a lookup in another system, a colleague asking for a status that is not visible anywhere. Each of these feels trivial. The research on interrupted work suggests otherwise.

In a widely cited field study, Gloria Mark and colleagues found that after an interruption, workers took an average of about 23 minutes and 15 seconds to return to the original task. The interruption itself is only the visible part. The tail, the time spent re-establishing context, is where most of the cost hides.

A single interruption is manageable. The problem in an under-designed operation is volume. When status lives in spreadsheets, chat threads, and inboxes rather than in one system, every question becomes an interruption for someone else. The same study found that interrupted work was often completed faster, because people compensated by working harder, but at a measurable cost in stress, frustration, time pressure, and effort.

Multiply that across a team and the pattern becomes structural. The operation is not slow because the people are slow. It is slow because its tools force a constant exchange of interruptions just to keep everyone informed.

The remedy is not to ask people to focus harder. It is to remove the reasons they interrupt each other. When status is visible in a shared system, most status questions never get asked. When handoffs are structured rather than improvised, the receiving person is not pulled off their work to reconstruct context.

This is the quiet return on operational software that most business cases miss. The headline is fewer clicks. The real gain is fewer interruptions, and the recovered attention that comes with them.