Protected projects, processes, and people survive review after review because their sponsor brings a network to their defense, so cutting one carries a cost its numbers alone would not.
Borderline: whether this move is justified depends on the situation, and only the person in it can judge.
An example
For the third year running, the home-automation venture sponsored by the executive vice president of consumer at a telecom carrier would sit near the bottom of the budget director's return ranking, and he knew it. He also believed it was the company's way into a market worth more than the network upgrades ranked above it. Two weeks before the review, he walked the chief technology officer and the head of retail through the venture's customer retention data, asked the retail chain that stocked the product to send the committee a letter on its shelf commitments, and briefed the chief executive on the three missed milestones and why they slipped. At the review, the chief technology officer and the head of retail both spoke for keeping it. The committee kept the venture on a reduced budget with a hard milestone for the next cycle.
Why it works
Defending through a network works by making the alternative, cutting the item, costlier for whoever decides. The company's formal criteria judge the item, but the decision-maker also weighs what a cut would do to relationships with the protector and the allies who spoke up, and to their own standing in the informal hierarchy. A protector's record of past defenses adds weight without anything being said. It works in proportion to the protector's power and the organization's tolerance for political decisions, and it is strongest when the allies bring information the ranking missed.
The thinking behind it
Jeffrey Pfeffer Jeffrey Pfeffer's Power in Organizations (1981) treats organizations as political systems in which important decisions are shaped by power as well as analysis, with power coming from position, control of resources, and centrality in networks of dependence. A protector with a strong network can make a cut costly for the person who decides, whatever the ranking shows. Pfeffer's account explains why formal criteria alone so rarely settle these reviews.
Thomas C. Schelling Thomas Schelling's The Strategy of Conflict (1960) argues that a threat works only if the other side believes it would be carried out. A protector who has defended a project twice before has a record that signals on its own, and a reviewer weighing the cut reads that record. The same idea marks where the move turns dark: once the network implies consequences for the reviewer's career, the defense has become a threat.
When it fits
Sponsors of something whose value the standard review cannot see get the most from it: a long-horizon bet, a capability the numbers undercount, a person whose contribution is real but hard to measure. You need allies with standing who believe in it on their own account, and evidence they can add. It fails when the push to cut comes from outside your reach, such as a new owner or a chief executive with board cover.
How to use it well
Argue the case first and bring the network second. Supply the information the ranking missed: retention, strategic position, the cost of rebuilding later.
- Ask allies to speak only if they believe in it, and give them the facts to do so.
- Bring in outside voices with a real stake, such as customers or channel partners.
- Acknowledge the misses plainly and offer terms: a reduced budget, a hard milestone, a date to revisit.
- Accept the review's authority over the outcome.
Protect sparingly. Each defense spends credibility, and a protector who shields everything stops being believed about anything.
What it costs and where it backfires
Each defense spends credibility with the people who decide, and protected items that keep missing make your judgment the issue. Peers whose programs were cut to fund yours will remember. The organization learns that political capital beats merit, which costs everyone over time. The line is the reviewer's own career. Once the defense carries any hint about the reviewer's promotion, budget, or standing, it has become a threat beyond your authority, and refusing the review's result becomes obstruction.
When it is used on you
Reviewers of a program that keeps being protected should write down what keeping it costs the company each year, in the same terms used for everything else. Ask for the decision to be sponsored from outside the protector's reach, such as by the chief executive with board cover, bring in the peers who would gain from ending it, and require a written reason for every exemption.