Winding down a well-loved legacy program over several budget cycles, without ever staging a cancellation, moves its resources to growth and gives its defenders no single event to rally around.
Borderline: whether this move is justified depends on the situation, and only the person in it can judge.
An example
The mechanical pressure gauge line had founded the instruments company, and several board members had started their careers on it. It had lost money for six years. The general manager who took over the division judged that its engineers and floor space belonged to the digital sensor line, which was growing 20 percent a year. He did not propose closing the gauges. In his first budget he cut the line's marketing to its distributor price list and moved two of its five engineers to sensors, each change justified in the plan by return on spending. When the gauge line's veteran plant supervisor retired, he merged the role into sensors. Over three cycles the gauge line went from a third of the plant to a corner. When a long-serving engineer asked him at a town hall whether the gauges were being phased out, he said yes, gave the numbers, and said he expected the line to end within two years.
Why it works
Spreading the withdrawal across cycles makes accepting it easy at each step, since no single change is large enough to fight. It also removes what defenders need most: a clean cancellation that rallies loyalty and makes a martyr. Without that event there is nothing to protest. Each attempt at resistance means escalating over a minor budget item, which looks disproportionate and makes resisting costly. Patience across several cycles is required, along with a real business reason for each individual cut and cuts spaced far enough apart that they read as management and never as a campaign.
The thinking behind it
Thomas C. Schelling Schelling's Arms and Influence (1966) describes salami tactics, crossing a line in slices too small to justify a response. Sunsetting moves resources out of a legacy program the same way, so no single budget presents its defenders with a cut worth fighting. The approach holds while the slices stay small and spaced, and it collapses into a single event when someone forces the question in a forum that demands an answer.
Mancur Olson Olson's The Logic of Collective Action: Public Goods and the Theory of Groups (1965) shows that diffuse groups find it hard to organize because each member bears the cost of acting and shares the benefit. A program's defenders are usually a diffuse group of loyalists. A cancellation event would give them a common cause and a moment to act together, while gradual withdrawal keeps the cost of organizing high and the reason to start low.
When it fits
It fits when a legacy program has real loyalty but no longer earns its resources, when you are confident those resources will do more elsewhere, and when you control its budget and staffing across several cycles. It suits patient leaders in organizations where an outright cancellation would bring protest, departures, or board pressure out of proportion to the program's size.
How to use it well
Decide the end state first, and tell your own manager and the board what it is, privately and early.
- Justify every cut on its own business grounds, such as returns, shifting priorities, or a vacancy left unfilled. If a cut has no real reason, do not make it.
- Move people toward work they can grow into, so the program's staff have somewhere to go.
- Keep the program's commitments to customers until they can be met another way.
When someone asks directly whether the program is being wound down, answer truthfully and give the reasons. By then the program is small, and the honest answer costs little. Expect to be asked, and decide in advance what you will say.
What it costs and where it backfires
It takes years, and during them you carry a program you believe should end. A defender who forces the question in a forum that demands an answer, an insider who leaks the plan, or budget cycles that bunch the cuts together can turn the gradual path into the very event you avoided, with your motives questioned. Deception is the line: denying the plan when asked, or inventing reasons for cuts, turns sequencing into a lie, and the defenders' story of betrayal becomes true.
When it is used on you
On the receiving end, the signs are a program's budget and headcount shrinking every cycle, departures left unreplaced, a routine reason for each cut, and no cancellation decision recorded anywhere. Ask in a forum that requires an answer whether the program is being wound down. Lay the cuts side by side across cycles, so they read as one decision someone has to own.