Attention residue: what an interruption actually costs
Executive teams try to protect their people's time, and treat interruption as lost minutes. Research describes something different, and costlier: part of one's attention stays attached to the previous task. The useful question is therefore not 'how long did the interruption last?' but 'in what state do we return to the next task?'.
The mechanism described
Sophie Leroy (2009, Organizational Behavior and Human Decision Processes) named attention residue the fact that part of one's cognitive resources remains engaged with an interrupted task when another one begins. Her experiments show degraded performance on the subsequent task, more pronounced when the first could not be brought to some form of closure. The finding rests on laboratory tasks and short delays: transposing it to a manager's day is an inference, not a measurement.
What field observation adds
Gloria Mark, Daniela Gudith and Ulrich Klocke (2008, CHI) observed that interrupted people completed their task in comparable time, but at the price of higher reported effort and stress. The cost therefore does not appear where it is usually sought — in elapsed time — but in load. An organisation steering on deadlines alone will never see that cost in its indicators.
The managerial temptation to resist
The mechanism is often converted into a simple rule: eliminate interruptions. That is an over-reading. Leslie Perlow (1999, Administrative Science Quarterly) showed in an engineering team that interruption is also the vehicle of mutual help and coordination, and that suppressing it abruptly displaces the problem. What the literature supports is narrower: make interruption intentional rather than permanent.
Why this concerns front-line management first
The front-line manager is simultaneously the most interrupted person and the first source of interruption for the team. Availability is a resource; permanent availability is a source of fragmentation. The issue is not individual discipline, wrongly invoked: it is a team rule, and therefore a managerial responsibility rather than a matter of personal willpower. (our executive and employee training programmes)
Two defensible conditions, and their limits
What current knowledge cautiously supports: allowing even partial closure before switching — noting where one stands and the next step — reduces the residue Leroy describes; and grouping requests into announced windows preserves the mutual help Perlow describes while limiting fragmentation. Neither has been demonstrated in a Swiss managerial context, and neither replaces a genuine decision about workload.
One practical implication, testable internally
Before installing new time-management tooling, it is cheaper to measure one thing: over a week, how many meetings or messages demanded an immediate answer that could have waited four hours. Counting requires no instrumentation. It is the starting point we use with executive teams in Geneva, ahead of any training on priorities. To go further: explore the Frontline Management training in Geneva, or browse our executive and employee training programmes in Switzerland.
In pictures: Frontline Management in Geneva
- frontline management
- Geneva
- research
- training geneva