A Practical Way to Retire Projects That Will Not End

Nobody wanted to cancel them, so they consumed attention without technically being alive.

A zombie project is paused demand that keeps a claim on future capacity without earning reapproval.

Add a sunset clause

At approval, set a review date or trigger: ninety days paused, sponsor departure, missed evidence threshold, major strategy change, or estimate growth beyond a limit.

Clean the larger queue with how to deal with a chaotic project request backlog. This article owns one species inside it: work that already survived intake, stopped moving, and still refuses to return its chair.

At the trigger, return to the original software project intake record. Ask whether the problem, impact, owner, and strategic alignment still exist.

Require reapproval

Do not restart automatically. Compare the project with current demand and capacity. Record continue, reshape, or stop.

One project surviving three annual plans because it was “already started.” Less than one week of work had been completed. Its largest investment was organizational embarrassment.

Celebrate released capacity

Report the people, budget, meetings, and attention returned by stopping. Cancellation is not lost output when the outcome no longer matters.

Use the free Project Intake Evaluation Worksheet to check whether not-yet decisions and stalled work have a condition for review. Zombies thrive where “later” has no date.