Rival leaders are weakened through their teams: senior subordinates lose resources, responsibilities, and access in separate, routine-looking decisions until the leader's power base is gone.
An example
Everyone at a mid-size airline expected the chief operating officer's successor to come from either maintenance or flight operations, and the vice president of flight operations sat on the talent allocation council. Over fourteen months the council moved the maintenance department's two most senior engineers into a fleet-transition program, cut its training budget in an efficiency review, transferred its planning analysts to a shared services group, and ended its access to the scheduling system in a security cleanup. Each decision had its own memo. The vice president of maintenance protested the first two and was told in a staff meeting that he sounded like he was building an empire. He stopped protesting. When the operating chief retired, the board chose the head of flight operations, citing his deeper bench.
Why it works
Each move is designed to look routine, so letting any single one go seems cheap, which makes accepting the losses easy. Defending the team looks worse, because it means many small fights, each unwinnable alone, and a reputation as a complainer or an empire-builder. Defending becomes costlier with every fight: political capital spent, unwanted attention, and the sound of paranoia when naming the pattern. Control over allocation decisions that touch the rival's team is the precondition, along with six to eighteen months, deniable cover for each move, and a rival who cannot defend every front at once.
The thinking behind it
Thomas C. Schelling Schelling's Arms and Influence (1966) describes salami tactics: a line drawn as a threat can be defeated by crossing it in slices, each too small to justify carrying the threat out. Each loss to the rival's team is such a slice, too small and too routine to fight alone. Escalation triggers agreed in advance with a sponsor turn the slices back into a line that is visibly crossed.
Jeffrey Pfeffer Pfeffer's Power in Organizations (1981) traces power to control of resources and centrality in networks of dependence. A leader's power base is the team's headcount, budget, access, and senior people. Draining those leaves the title intact and the power gone, which is why reviewing allocation decisions by their cumulative effect on each team is the governance answer.
Warning signs
Over six to eighteen months, one leader's team loses headcount, budget, system access, and senior people through separate decisions, each explained as reorganization, efficiency, or a development rotation. The decisions come through a body where a rival has a seat. Each protest is met with a remark about empire-building. The leader's own title and role are never touched.
How to defend yourself
By the time you see the pattern, the moment to defend was several reassignments ago, so set the trigger in advance.
- Agree with your sponsor on escalation triggers: for example, any reassignment of a top-five team member leads to an automatic joint review.
- Keep a running list of every loss to your team, with dates and the stated reasons.
- Have your team raise the losses together, since defending each move alone looks like empire-building.
- If your sponsor has the authority, ask for a freeze on allocation changes affecting your team until a review is done.
How a leader shuts it down
Review allocation decisions quarterly by their cumulative effect on each team. Keep people with a stake in a succession contest off the bodies that move their rivals' staff, or require them to recuse. When a leader's bench thins through routine decisions, ask who made the decisions before judging the leader's depth.