Inbox Flood and Drought

Tactics of Organizational PoliticsInformation and NarrativeA tactic to guard against

Someone controls the timing and volume of email around a decision, burying an opponent in trivia before a deadline or leaving them off the threads where the decision is actually made.

An example

Choosing between its core-network vendor and a cheaper rival, a mobile carrier set a Friday procurement deadline. The director of network engineering had written a four-page objection about migration risk. In the two weeks before it, she was added to fourteen distribution lists: weekly vendor status notes, a facilities move, a holiday-coverage roster, daily automated test reports. More than 900 messages arrived. The thread where procurement and the chief technology officer settled the shortlist did not include her. A question asking whether she had 'any remaining concerns before Friday' went out at 6:10 on Thursday evening inside a digest of routine updates. She saw it on Monday. The minutes recorded that engineering had raised no further objection, and the switch was approved.

Why it works

Nothing in the move touches the merits of the preferred position; it works on the opponent's ability to object. Under the flood, a correct rebuttal arrives late, partial, or buried, so it carries less weight. Under the drought, the opponent lacks the facts to make one. Either way objecting costs more, and a hard deadline turns that delay into lost ground. It depends on control of distribution lists, a norm that silence on email means consent, and no informal route the opponent can use to reach the decision.

The thinking behind it

Herbert A. Simon In Designing Organizations for an Information-Rich World (1971), Herbert Simon argued that a wealth of information creates a poverty of attention. The flood half of this tactic applies his point directly: hundreds of low-priority messages consume the attention the target needs for the one that matters. Standalone messages to the decision-maker, with the decision named in the subject line, work because they stand outside the flood.

George A. Akerlof George Akerlof's The Market for "Lemons": Quality Uncertainty and the Market Mechanism (1970) showed the power of whoever holds information the other side cannot check. The drought half of the tactic creates that gap on purpose: the threads that carry the decision leave the opponent off, so the side that controls distribution knows what the other does not. Informal routes to the decision-maker are the defense because they restore the missing information.

Warning signs

You are copied on large volumes of low-priority material while the threads that carry the decision leave you off. Distribution lists change shortly before a deadline. Questions that need your answer arrive late in the day, bundled with routine updates. Later, your silence on one buried message is cited as agreement. Peers seem to know things about the decision that never reached you.

How to defend yourself

Keep routes to the decision that do not depend on email.

  • Talk directly to the decision-maker or their staff on anything with a deadline; side conversations bypass a managed inbox.
  • When material arrives late, ask for a deadline extension as a matter of course, and say why in writing.
  • State your position in a standalone message to the decision-maker, with a subject line that names the decision, so it cannot sink into a digest.
  • Keep a dated log of what reached you and what didn't.

If the pattern repeats, take the asymmetry to a senior leader: who was on which thread, and when. Wins that keep coinciding with a rival's procedural breakdowns get noticed once someone lays them side by side.

How a leader shuts it down

Require that material relevant to a decision goes to everyone it affects, and stop treating silence on email as consent. Notice when one person's victories line up with their rivals' missed threads. Give decisions with deadlines a named list of the people whose sign-off or objection is required.

Back to the catalog