Inside a leadership coalition, an incumbent slows an ally's signature project through staffing, sponsor attention, and budget timing, so the ally never builds a power base that could threaten the existing order.
An example
Two years after making partner at a strategy consulting firm, a practice leader was two quarters from landing an anchor client in medical devices, a win that would have justified a practice group of her own. The managing partner sat beside her on the strategy committee and praised the pursuit at every meeting. Over the next four months the two strongest associates on the pursuit were pulled onto an urgent engagement in another office, the managing partner missed the client dinner he had promised to attend, and the firm's budget review moved her proposal funding into the next fiscal year. At the final pitch the client asked why the senior team had changed twice. The firm placed second. Afterward a retired partner she still had lunch with laid the three decisions side by side and pointed out that one person had approved all of them.
Why it works
Keeping the coalition's current order costs the incumbent little as long as the ally never becomes a peer rival worth renegotiating with. Each pulled associate and absent sponsor makes the ally's project worse: missed milestones and lukewarm inside references strip it of the prestige that would have turned into an independent base. Every recovery costs the ally time and capital spent on friction they cannot trace. The incumbent needs inside access to the ally's staffing, sponsor calendars, and budget timing, so each setback looks like ordinary friction. Norms of solidarity help by making suspicion of a friend expensive to voice, as does a project complex enough that the real causes of trouble stay ambiguous.
The thinking behind it
Jeffrey Pfeffer In Power in Organizations (1981), Pfeffer argues that power comes largely from structural position: control of resources, information, and the decision process. Friendly fire depends on exactly that position. The incumbent never has to oppose the ally's project, because controlling who staffs it, when the sponsor shows up, and which fiscal year funds it is enough. The same idea explains the defense: reduce dependence on the incumbent's resources and make the decisions about them visible.
Lee Ross Ross named the fundamental attribution error in The Intuitive Psychologist and His Shortcomings: Distortions in the Attribution Process (1977): observers explain other people's behavior by their traits and underestimate the situation they were in. When an ally's project stumbles after its best people are pulled, colleagues, and often the ally, read the trouble as weak leadership or ordinary bad luck. A mentor outside the coalition who looks at the situation, the staffing moves and sponsor absences, supplies the correction.
Warning signs
Trouble arrives at the milestones that matter. The best people are reassigned the week before a deliverable, a sponsor who was enthusiastic misses the key meeting, a budget line slips a quarter, a review that used to be friendly turns skeptical. Nobody opposes the project, and each setback has an ordinary explanation. The pattern is in who made the calls, and in a small coalition they trace back to the same seat.
How to defend yourself
Treat unexplained friction inside your own alliance as information.
- Log every staffing change, sponsor absence, and budget slip with the date and the name of whoever made the call.
- Keep a mentor outside the coalition, someone with no stake in its internal order, and walk them through the log at each milestone. They can see the pattern more easily than you can from inside it.
- Reduce your dependence on the incumbent where you can: staff from people who report to you, get budget commitments in writing ahead of the cycle, and bring the client or the board close enough to see the work directly.
Once the log points to one person, put the dates in front of them privately, and in front of the coalition's other members if the pattern continues.
How a leader shuts it down
Make the inputs to other people's projects visible: publish staffing moves on major pursuits with the reason and the approver, and review sponsor attendance at key milestones. Reward leaders whose allies grow. Treat a run of unexplained setbacks on a rising leader's project as a question for the whole leadership team to answer.