Strategic Apathy

Tactics of Organizational PoliticsResistance and SabotageA tactic to guard against

A senior executive watches a problem grow in a rival's domain and does nothing, letting it become a crisis that discredits the rival, while leaving no trail of having seen it coming.

An example

A general contractor's head of preconstruction sat in the weekly estimating meeting where it became clear that a drywall subcontractor on three of the field operations group's hospital jobs was months behind on payroll. Help between the two groups was routine: preconstruction regularly flagged subcontractor risk and lent estimators to price replacements. This time nothing was flagged. The head of field operations, a rival for the chief operating officer job that would open in the fall, learned of the problem when the subcontractor walked off two sites in May. The jobs overran by $6 million, and the field operations head spent the summer explaining it in weekly cost reviews. Months later, an estimator mentioned the meeting to the chief executive, who asked the head of preconstruction why no warning had gone out. The answer was that it had been outside preconstruction's lane.

Why it works

Doing nothing is nearly free at senior levels: no capital spent, no resources committed, no trail. That makes the actor's path easy. Intervening has little payoff for them, since a rival who recovers gets the credit and public help can look like meddling, so the helpful option looks worse. It also carries real cost, committing their reputation to the rival's problem and spending capital across silos. It requires plausible deniability about having seen the problem, a rival domain that is genuinely fragile, and a board or chief executive who blames failure on the domain owner without looking at systemic causes.

The thinking behind it

Jonathan Baron Omission and Commission in Judgment and Choice (1991), by Spranca, Minsk, and Baron, found that people judge harm from failing to act as less bad than the same harm from acting. A peer who wrecked a rival's projects would be condemned; a peer who simply sent no warning draws little blame, and can say the matter was outside their lane. Asking peers in writing for their view of your risks makes their silence a recorded choice.

Lee Ross Lee Ross's The Intuitive Psychologist and His Shortcomings: Distortions in the Attribution Process (1977) named the fundamental attribution error: observers explain others' behavior by their personal traits and underestimate the situation. When a domain fails, boards tend to blame the person who runs it, and the peer who could have helped stays out of the picture. Presenting the systemic causes, and naming who had the standing to help, puts the situation back into the explanation.

Warning signs

No warning and no resources come from a peer with clear visibility into a deteriorating domain, though help between peers would be routine. The peer later says the problem was outside their lane. The silence coincides with a contest between the two, such as a succession or a budget fight. Over time the same leader is absent from several peers' crises.

How to defend yourself

If you run the domain, widen your own sightlines: build relationships below the peer, with the people who see your risks first, so your information does not depend on one executive choosing to pass it on. Ask peers directly and in writing for their view of your risks at regular intervals; a recorded question makes silence harder to defend later. When a crisis hits, present the systemic causes alongside your own role, and point out who had the standing to help. A pattern of absence from peers' crises becomes visible over time, so keep the dates.

How a leader shuts it down

When a rival's predictable problem unfolds without the usual peer help, ask who had the standing to help, what they would have spent, and what they gained by not doing so. Weigh systemic causes before assigning failure to the domain owner. Make flagging risk across groups an explicit duty, and evaluate it.

Back to the catalog