Clearing the executive’s 800-plus-email backlog

Clearing the executive’s 800-plus-email backlog is a case study in how small processing decisions can transform an overloaded work system. A vice president who had been deferring messages for later worked through his accumulated inbox with David Allen: some emails were discarded, some filed as reference, and many answered immediately because they required less than two minutes. A year later he was current, his inbox no longer exceeded a screenful, and his division experienced the effects of his faster responses.

The backlog and its causes

The vice president worked at a large software company and received about 300 emails a day. He was focused on three key initiatives, while many incoming messages came from people reporting to him who needed his review, comments, or approval to proceed. Because those messages did not concern the initiatives currently in his sights, he left them in the inbox for later. The deferred work accumulated into several thousand messages, and he sometimes spent entire weekends trying to catch up. With young children and no longer willing to spend weekends that way, he sought coaching.

The backlog was not simply a matter of message volume. It reflected a gap between what arrived and what had been decided: emails remained in the inbox without a clear choice about whether to act, file, or discard them. The example gives concrete form to a broader problem of knowledge work, in which projects have no obvious stopping point and vast amounts of potentially relevant information compete for attention. In this case, the queue also carried consequences for other people: staff members needed the vice president’s decisions before their work could move forward.

Processing the inbox

During coaching, the vice president and Allen went through all 800-plus emails then in the inbox. They sorted rather than treating every message as a task to complete later: some could be thrown away, some belonged in reference files, and many needed only a brief reply. Those replies were handled immediately under the Two-Minute Rule, which recommends doing an action when first encountered if it takes two minutes or less. The rule is an efficiency cutoff: for a short response, storing and tracking the message for a later pass may take longer than completing it at once.

The point was not that every message deserved action, or that every action was important. If an item was not worth doing, it could be discarded; if it mattered and would be done eventually, its brevity favored doing it then. This distinction turned a mass of undifferentiated email into separate outcomes—delete, retain as reference, or respond—and prevented simple replies from continuing to occupy the inbox as unresolved work.

Results and significance

The vice president later reported that following the rule gave him an additional hour of quality discretionary time each day. When Allen checked in a year after the coaching, the executive was still current and no longer let email accumulate beyond a screenful. He also said the change had altered the nature of his division: his markedly faster response time helped staff move work forward, and they regarded him as being made of Teflon.

The account links personal processing habits to organizational responsiveness. Allen presents the five-stage workflow method as a chain of collecting, processing, organizing, reviewing, and doing; a weakness at any stage can undermine the choices available for action. The executive’s inbox intervention concentrates on processing, but its effects depended on making decisions about the collected messages and maintaining a manageable system afterward. The story therefore treats the Two-Minute Rule not as a productivity trick in isolation, but as a small, repeatable behavior whose consequences can reach beyond the individual to the people waiting on his decisions.