Continuing a project usually reflects what has already been spent on it, not its future returns. The sunk cost fallacy describes the tendency to keep an endeavor alive because of money, time, effort, or emotion already committed. Those costs are irrecoverable and fixed whether the project continues or stops, so a forward-looking decision weighs only future costs and benefits.
There is an emotional lever underneath it. Ending something feels like a verdict on the choice to begin it, because the project has become part of how you see yourself.
Several psychological drivers hold the pattern in place. Loss aversion makes a loss hurt roughly twice as much as an equivalent gain feels good, so ending a project registers as a loss while continuing feels like avoiding one. Commitment escalation pushes people to justify prior choices by doubling down. A reluctance to waste what has been put in adds weight of its own. The same bias shows up beyond work, in investments, relationships, and career paths, where the pattern persists.
Annie Duke, a former professional poker champion, argues that grit is admirable, but ignoring a world that is telling you to stop is no longer a virtue; it is folly. The useful distinction is whether a project is hard because it is valuable or hard because it is misjudged.
Persistence earns its keep in the first case. Applied to a wrong bet, it deepens the investment and delays the correction. Duke's point applies at the level of the individual project: the effort is wasted when the feedback says the bet is wrong, not when the work is merely demanding.
The practical reframe is to shed initiatives that are not delivering lasting impact and make room for ones that could. That shift changes what the decision is about: not your toughness, but the allocation of effort. It sits close to the essentialist approach, which sorts work by whether it multiplies impact.
Set the exit conditions before you need them. Kill criteria are explicit triggers, decided in advance, that would justify stopping: a missed adoption target, a date, a cost ceiling, a repeated failed test. A concrete version: if weekly signups stay below 100 by week 12, shut down the beta and move its budget to the next candidate. Written down early, the criterion moves the decision out of a moment when fatigue and ego are voting.
A usable criterion is observable from outside your own head, a number or a date that another person could check, so the call does not fall back to the same tired judgment the criterion was meant to replace. An intention to see how it goes fails that test.
An initiative inventory is a workable starting point. List everything currently running, in plain form, and note what each is supposed to deliver. Seeing the whole set at once makes it easier to name which items deserve a kill criterion and which are already past one. Grouping them side by side also exposes overlaps, where two initiatives chase the same outcome and one can be retired without loss.
A rule you set when you were clear-headed costs far less to act on than a fresh judgment made in the moment when the pressure to continue is strongest. Writing the threshold down also makes it harder to quietly move the goalposts after a bad month.
Treat your commitments as a portfolio and review them periodically, the way you would prune a task list. Some projects survive the review because the evidence supports them. Others end on schedule, because the criterion you wrote months ago now applies. A recurring review keeps that judgment from depending on how you happen to feel that week.
This differs from declining new requests. Saying no protects your calendar at the front door. Strategic quitting addresses commitments you have already made, where the costs are partly sunk and the remaining question is whether to keep paying. That is the process that frees capacity for work worth finishing.
