There are two ways to lose the ability to stop projects. The first is a company where nothing is ever closed: failed initiatives shrink slowly, keep their budgets and their status, and the organization quietly fills with work nobody believes in. The second is a company where closing a project is a public execution — and within a quarter, proposals stop arriving, because the lesson was learned: initiating is dangerous. Both organizations fail at the same skill, from opposite directions. Closing a project well is a discipline, and it has working parts.
A project closed by criteria that were written at launch dies by its own terms rather than by someone's verdict. «We said in the plan that if we did not reach a signed pilot with this segment by the end of the quarter, we stop» is a decision that was made once, calmly, before emotions had anything invested. The review then compares evidence to criteria instead of person to person. This is prioritization's mirror image: ranking what starts and defining what ends are the same discipline applied at different moments.
Most projects that deserve closure were reasonable bets at the moment they were made. The review should ask whether the premise was sound at launch and what the project taught — separating a disproven hypothesis from negligent execution. A stopped project whose premise was honestly tested is a completed project: it bought information the company needed. Treating it as a failure teaches people to hide premises they doubt, which is how the dangerous projects survive the screening. The distinction between a good decision and a good outcome is worked through in good decisions, bad outcomes; a review process that respects it keeps the honest proposals coming.
For the team, the loudest part of the closure is what happens to its members. A project dies cleanly when its people are released to work the organization visibly respects — not scattered into whatever was short-handed that month. The strongest possible signal about whether initiative survives is watching the person who ran the stopped project get a good assignment two weeks later.
A short factual close-out: what was tried, what the premise was, what was learned, what changed because of it. Without ceremony, without blame, and without the opposite sin — inflating a closure into a victory narrative nobody believes. One honest paragraph in the company's own voice is worth more than either.
The alternative to this discipline is slow strangulation: projects nobody closes and nobody funds properly, consuming attention while the market moves. That quiet version of failure is the most expensive one, and resource allocation is where its bill eventually arrives.
We use cookies to analyse traffic and improve the site. Analytics is enabled only with your consent. Cookie Policy