Shutting Things Down Is a Leadership Skill

Every organization carries a set of products, programs, reports, and processes that no longer earn their cost. They persist not because anyone defends them but because stopping requires a decision and continuing does not.

The cumulative cost is substantial and mostly invisible: capable people maintaining things nobody uses, attention divided across too many commitments, and a slow erosion of the belief that priorities mean anything.

Make the default a review, not continuation

Anything that continues by default will continue past its usefulness. Attach a review date to programs and reports at the point of creation, and hold the review as a real decision with a genuine option to stop.

A simple, effective practice: every recurring report has an owner and an annual question — who reads this, what decision does it inform, what would happen if it stopped. A meaningful share of them will not survive that question honestly asked.

Separate the sunk cost from the decision

The conversation about stopping is almost always contaminated by what has been invested. Two years of work, a public commitment, a leader's reputation.

Ask the counterfactual instead: knowing what we know now, would we start this today? If the answer is no, the remaining question is how to stop well, not whether to. Naming the sunk cost explicitly, out loud, is what allows the group to set it aside.

The strongest predictor of whether an organization can stop something is whether the person who started it can say so without losing standing.

Protect the people before you announce

The reason teams resist shutdowns is rarely attachment to the work. It is uncertainty about what happens to them. Decide the destinations first — roles, projects, reporting lines — and communicate the shutdown and the destinations together.

Handled this way, sunsets become routine. Handled the other way, every one of them generates a month of anxiety across the organization and teaches people to hide the weakness of their programs.

Say why, and say what it funds

A shutdown explained as cost reduction reads as retreat. The same decision explained as reallocation — we are stopping this to fully fund that — reads as a choice, and it is usually the truth.

Then actually reallocate, visibly. If the freed resources disappear into general overhead, the next shutdown will be resisted much harder.

Plan the customer and dependency exit properly

Most reputational damage from sunsets comes from poor execution rather than the decision. Map who depends on the thing, internally and externally, give realistic notice, provide a migration path, and honor existing commitments.

A well-run wind-down over six months does more for a brand than continuing a neglected product for two more years, which is the alternative most organizations choose by default.

Celebrate the stop

Leaders who publicly credit a team for retiring something well change what the organization believes about its own priorities. The message that lands is that finishing and stopping are both respected work — which is, in the end, the only way a portfolio stays sharp.