When to Kill a Project: HBR’s Guide to Knowing When to Walk Away

UpTrajectory Review

Harvard Business Review has bundled seven articles into a guide on killing projects: how to spot an initiative that will not pay off and how to walk away without wrecking morale or your budget. The collection draws on research into sunk-cost bias, escalation of commitment, and the organizational politics that keep zombie projects alive long after they stop making sense. HBR sells this as a discipline, not a failure. The guide arrives at a moment when capital costs more than it did two years ago and when boards ask harder questions about every line item.

For a small-business operator, this guide matters more than for a Fortune 500 manager. A big company can absorb a dead project; a small firm cannot. Every dollar and hour sunk into a failing initiative comes straight out of payroll, marketing, or the owner's own compensation. Yet small teams fall into the same trap as large ones: they keep funding a project because they already funded it, because a key employee championed it, or because killing it feels like admitting a mistake in front of people who trusted the call. The guide gives you language and frameworks to make the cut earlier and with less drama.

We agree with the core premise: most businesses do not kill projects too early; they kill them too late. The sunk-cost fallacy is well documented, and the political cost of cancellation often exceeds the financial one. We remain skeptical of one thing the HBR framing tends to underplay. Walking away is not always the brave or correct move. Some projects look dead right before they turn. The harder skill is distinguishing a stalled initiative from a lost cause, and no article collection can fully teach that judgment. Use the guide as a prompt for honest review, not as permission to quit whenever progress feels slow.

The second-order effects of a well-timed kill are real. You free cash and people for work that has a better shot at returning value. You also send a signal: this company reallocates resources based on evidence, not loyalty or pride. That signal can sting. Employees who poured themselves into the dead project may read the decision as a verdict on their effort, not the idea. Handle the kill poorly and your next initiative will struggle to recruit internal champions. Handle it well and you build a culture where people pitch ideas without fearing that one bad bet defines them.

Watch for how your team reacts the first time you apply these frameworks. If people start hiding bad news to avoid triggering a review, you have overcorrected. If they bring you problems earlier because they trust you to respond rationally, the discipline is working. Try this: schedule a quarterly project review where every active initiative must justify its continued budget in one page. Force the conversation before the numbers force it for you. The HBR guide will not make the decision easy, but it can make the decision possible.

Read the full collection if you have ever kept a project alive because you were too proud or too tired to stop it. The articles will not tell you which project to kill next week. They will show you the patterns that keep weak projects breathing and give you a framework for the conversation you have been avoiding. That alone justifies the time.

Takeaway: Schedule a quarterly review where every active project must justify its budget in one page; kill what fails before it drains another quarter.