During a leadership transition, passed-over candidates and sidelined veterans who hold knowledge no one else has make it costly for the new leader to move past them, through selective cooperation and implied threats.
An example
Her first move as head of payments operations at a regional bank was to consolidate three legacy teams into one platform group and give its lead architectural sign-off. Three long-tenured engineers lost that authority, and one of them had been a finalist for her job. All three still held the only working knowledge of how the wire-transfer system behaved during month-end volume spikes. Within weeks, requests for documentation were taking a week each. In a design review one of them remarked that the last person who changed the batch scheduler had caused a two-day outage, and that he hoped the new team knew what it was doing. The bank's largest corporate clients still called him directly. She delayed the batch change by a quarter and spent the time pairing platform engineers with a retired contractor who had built the system.
Why it works
Moving past the aggrieved veterans looks worse because their resentment, plus what only they know, turns decisive leadership into a gamble: vendor ties, undocumented dependencies, and client trust all sit with them. It looks costlier because each piece of inside knowledge works as a standing threat that the new leader cannot quickly replace. How well it works depends on how indispensable they really are, whether their threats are credible, and how much disruption the organization can bear during the transition. Once the new leader shows their indispensability is overstated, the threat loses force.
The thinking behind it
Oliver E. Williamson The Economic Institutions of Capitalism (1985) explains that investments specialized to one relationship, such as knowledge of one firm's systems, lose value outside it and leave each side exposed to the other. Veterans who alone know how a legacy system fails hold exactly that kind of knowledge, which gives their resentment its force. Documenting systems and spreading relationships before a transition reduces the specificity and the exposure.
Thomas C. Schelling In The Strategy of Conflict (1960), a threat works only if the other side believes it would be carried out. Passed-over veterans rarely threaten openly; the implied threat is that things will break without them. Once the incoming leader shows that the knowledge exists elsewhere, the threat stops being credible, which is why the defense is parallel knowledge and not a confrontation.
Jeffrey Pfeffer The External Control of Organizations: A Resource Dependence Perspective (1978) argues that control of a critical, scarce resource gives power over those who depend on it. During a transition, undocumented knowledge and client relationships are that resource, and the new leader depends on the people who hold them. Reducing the dependence through documentation, pairing, and outside contractors is how the leader recovers freedom of action.
Warning signs
Non-cooperation starts only after the appointment, and only from the people who lost the job or their authority. Requests to them are slow-walked, and documentation is always nearly ready. Remarks in meetings point at past failures and at who knows how to prevent them. Major vendors and clients keep calling the veterans directly, and nobody mentions it until a decision is pending.
How to defend yourself
The durable defense is built before the transition, so the incoming leader should start as early as possible.
- Document critical systems and dependencies, using outside contractors or former staff if insiders slow-walk it.
- Spread vendor and client relationships across more than one person, with introductions made openly.
- Build parallel knowledge by pairing newer staff with the veterans on live work.
- Keep a dated record of requests and responses, in case the pattern needs to go to your own boss.
Treat the veterans as experts with grievances, and talk to them about both. Visible threats push an organization to document and spread what they know, so a calm, steady build of parallel knowledge usually ends it.
How a leader shuts it down
Boards and senior leaders planning a succession should map who holds hard-to-replace knowledge before the decision is announced, and fund its documentation in advance. Plan explicitly for passed-over candidates: a conversation, a role, or a clean exit. Relationships with major clients and vendors should never rest with one person.