Leadership keeps a department running on false urgencies until its people lack the time or energy to plan, scrutinize, or resist a long-term change that moves forward during the noise.
An example
A listed packaging maker was under pressure from an activist fund to close plants, and the director of strategic planning had been asked to build an independent view of the plant network. For three months the planning team never got to it. Each week brought a new urgent request from the chief operating officer's office: a board question that needed a model by Thursday, a customer escalation, a pricing analysis for an investor call. The team's last finished strategic deliverable was fourteen months old. Two weeks before the board vote on closures, the requests doubled. Comparing notes with peers in finance and engineering, the director found the same spike in their calendars, timed to the same decision dates, with every escalation routed through one chief of staff. The director took the calendars to the chief financial officer and asked for two protected weeks before the vote. The board saw two network options instead of one.
Why it works
Exhaustion makes accepting the change look easier: for a team running on fumes, going along costs almost nothing. A critique, or plain planning, looks costlier, because it takes sustained attention and time that the drills consume, and spending a week on planning during a declared emergency looks out of touch. Whoever runs it needs control of the calendar, the alerts, and the label of urgent, and faces no counterweight such as an independent risk function or board oversight. It fails when people compare notes, a senior figure audits the urgency claims, or the manufactured fires cause real damage.
The thinking behind it
Herbert A. Simon Simon's Designing Organizations for an Information-Rich World (1971) argues that information consumes the attention of its recipients, so that a wealth of information creates a poverty of attention. A stream of urgent requests spends the planning team's attention, the one resource a critique requires. Protected deliberation time works because it fences off attention, which no amount of analytical skill can replace.
Daniel Kahneman Kahneman's Thinking, Fast and Slow (2011) describes a deliberate System 2 that engages only when something demands effort, and notes that people under time pressure or overload tend to accept the intuitive answer. A team running on drills is in that condition when the contested decision arrives. The ego-depletion work the book cites has not held up in a large replication, so the explanation here rests on time and overload alone.
Warning signs
Urgency spikes cluster in the weeks before each decision point on a contested change. The same few people control the calendar and decide what counts as urgent. A department's most recent strategic deliverable is more than a year old. Escalations come through channels one office controls. Planning time gets cancelled for emergencies that look ordinary afterward.
How to defend yourself
Compare notes. One team's overload looks like bad luck, and three teams with the same spikes before the same decision dates look like a pattern. If a peer leader openly carves out planning time and suffers nothing for it, follow. That proves the crises are optional.
- Plot urgent requests against decision dates for the contested change.
- Ask a senior figure, such as the chief financial officer or general counsel, to audit the urgency claims.
- Ask when your last strategic deliverable survived a quarter, and present its age as a risk.
- Ask for protected deliberation time before the decision, backed by the board or another outside stakeholder if you can get it.
How a leader shuts it down
Protect deliberation and planning time ahead of major decisions, and make it hard to cancel. Have someone independent audit what gets tagged urgent and who tags it. Track the age of each department's last strategic deliverable as a measure of its health.