How to Know When to Quit a Project

There is a version of persistence that is genuinely admirable, and there is a version that is just avoidance of a difficult decision dressed up as commitment. Telling them apart is harder than it sounds because the discomfort of a struggling project and the discomfort of a project that is genuinely not worth continuing feel very similar from the inside.

The cost of not distinguishing between them is high in both directions. Quitting something too soon wastes the investment already made and the learning still available. Continuing something past the point of sense wastes the resources that could be going into something better, and extends a low-grade drain on attention and energy that compounds over time.

Separate difficulty from wrongness

The most common reason people quit things they should continue is that the work gets hard. Most meaningful projects have a difficult middle. The novelty of starting has passed. The satisfaction of finishing is not yet in sight. The work itself requires more than it did at the beginning. This is not a sign that the project is wrong. It is a sign that it is at the stage where most projects stall.

A useful question at this point: if you could fast-forward past the current difficulty to the completed outcome, would you still want it? If the answer is yes, the difficulty is probably not a reason to stop. It is a reason to get through it.

Check whether the original goal still makes sense

Projects often outlive the reasoning behind them. The market changed. The assumptions turned out to be wrong. The person who started it is no longer the person who would start it now. A project that made complete sense twelve months ago can become genuinely misaligned with current priorities without anyone consciously deciding to continue it.

The question to ask is not whether this was a good idea when it started. It is whether you would start it today, knowing what you know now. If the honest answer is no, the case for continuing needs to rest on something more than past commitment.

Name the sunk cost and set it aside

Time and money already spent are gone regardless of what you decide. The decision in front of you is only about the future: what will continuing cost, what might it produce, and how does that compare to using those same resources elsewhere. The past investment is not a reason to continue. It is a fact about history that has no bearing on what the right next move is.

This is easier to understand in theory than to apply in practice, which is why naming it explicitly is useful. Writing down the decision you would make if the time already spent did not exist is often clarifying. If the answer is different from the decision you are actually making, sunk cost is probably doing the work.

Stop deliberately, not quietly

The projects that leave the most residue are the ones that were never formally closed. They drift into inactivity without a clear decision, and they sit in the background as a vague open loop. Making the decision explicitly, writing down what was learned, and acknowledging what the project produced even if it did not reach its original goal, turns a project into a conclusion rather than a failure.

Related: How to finish what you start · How to set priorities · How to review your week