Isa Jain All articles
Strategy

Sunset Clause: A Practical Guide to Retiring Work That Only Inertia Is Funding

Isa Jain
Sunset Clause: A Practical Guide to Retiring Work That Only Inertia Is Funding

Photo: TheAHL, CC BY 2.0, via Wikimedia Commons

Every portfolio review adds. Few subtract. That asymmetry is not a character flaw in the people running the reviews; it is what the incentives produce. Approving something new is optimistic, forward-looking, and easy to attach to a name. Ending something is an admission, a small political event, and a conversation with a sponsor who remembers why it mattered. So the portfolio grows, the calendar fills, and a quiet category of work accumulates that consumes budget, attention, and morale while producing neither value nor learning.

Call it what it is: a zombie project. Not a failed project—failures get closed and mourned. A zombie is work that has ended in substance but continues in form, sustained by sunk cost, by someone's reputation, by the fact that nobody has been assigned the job of asking.

Seven signs that the work has already ended

  1. The milestone moves; the definition of done does not. Dates shift quarter after quarter while success criteria stay vague enough to survive any outcome.
  2. The strongest argument is what has already been spent. When the case for continuing rests on prior investment rather than future value, the decision has already been made emotionally and is waiting for permission.
  3. Nobody can name the decision it informs. If the deliverable would not change a choice anyone is about to make, the deliverable is a document, not a strategy.
  4. Its loudest defender is not on the team. Support from a distance is often about identity or history rather than evidence. Ask the sponsor what they would give up to keep it.
  5. The status meeting is about status. Updates describe activity—meetings held, drafts circulated—rather than movement toward an outcome.
  6. It appears in the budget and in nobody's stated priorities. Work that survives in one document and not the other is being funded by omission.
  7. The people doing it speak in the past tense. Listen carefully in the hallway. Teams usually know months before leadership does.

Four questions that separate 'almost working' from 'already over'

Almost-working work has evidence of a learning curve, a real customer signal, and a credible path with a date attached. Already-over work has narrative. These four questions draw the line.

What decision would we make differently if this succeeded tomorrow? If the answer is vague, the work has no consumer. Work without a consumer is a hobby with a cost center.

If we were starting today, from zero, would we start this? The question sounds sentimental; it is actually a clean way to strip sunk cost out of the room. Ask each person to answer in writing before the meeting. The written answers are usually more honest than the spoken ones.

What would we do with the capacity if we freed it? This is the test that changes minds. Zombie projects rarely lose to the argument that they are bad. They lose to the argument that something else is better, and that the something else has a name, an owner, and a waiting list.

Is there a specific, near-term, falsifiable test that would change our mind? If the team can propose one—a customer commitment, a cost threshold, a technical result by a fixed date—then the project earns one more cycle, defined in advance. If they cannot, the honest conclusion is that no evidence would change the decision. That is not a project. That is a position.

Scripts for closing without casualties

Ending work cleanly is mostly a matter of sequence and specificity. The people who built something deserve to hear it before the organization does, in a room, with the reason stated accurately.

To the sponsor: 'We are closing this on the thirty-first. Here is the value it produced, here is what we are carrying forward, and here is where the team is going.' Lead with what was real. Do not call it a pause. 'Paused indefinitely' is what organizations say when they want the credit for a decision without the conversation.

To the team: 'The work was sound. The portfolio decision changed.' Name the craft you saw, separate the closure from individual performance, and arrive with the next assignment already drafted. People can absorb the end of a project. What they cannot absorb is ambiguity about their own standing.

To the wider organization: a short written note with the decision, the date, the reason, and what replaces it. Silence invites rumor, and rumor is more expensive than the memo.

The mechanics carry more weight than the message

Redeploy people before you announce. A closure announced on a Friday with no destination creates a weekend of anxiety and a Monday of résumés.

Document what was learned in one page. Not a post-mortem of blame—a transfer of knowledge, so the organization gets the return on an investment it has already made.

Recognize the work, not the outcome. Teams that watch careful effort get punished learn to hide their projects rather than improve them.

Measure the freed capacity. Six weeks after closure, ask what the reclaimed hours actually went to. If the answer is 'more meetings,' the portfolio did not shrink; it merely changed shape.

Build the sunset in at approval

Prevention is cheaper than archaeology. Attach a review date to every new initiative at the moment of approval, with a named owner and a stated question: what would have to be true in two quarters for this to continue? Add a standing subtraction item to the quarterly review—one item on the agenda that asks only what should stop. And treat unallocated capacity as a strategic asset rather than a gap to be filled, because an organization with no slack cannot change direction when the evidence says it should.

The discipline is not ruthlessness. It is the recognition that attention is the scarcest resource in any organization, and that every zombie project is being funded by something that might have worked.

All Articles

Related Articles

Six Weeks of Truth: Reading Your Calendar Like a Strategic Document

Six Weeks of Truth: Reading Your Calendar Like a Strategic Document

Compression as Discipline: Why Your Strategy Should Survive One Page

Compression as Discipline: Why Your Strategy Should Survive One Page

Off Autopilot: The 90-Minute Quarterly Review That Questions Direction, Not Just Progress