# Sunk Cost: What It Means at Work, and When to Walk Away Canonical URL: https://headwayskills.com/knowledge/decision-making/sunk-cost/ Markdown URL: https://headwayskills.com/knowledge/decision-making/sunk-cost.md Entity type: Article Last updated: 2026-07-07 Language: en Primary audience: professionals improving decision-making at work Owner: Headway Skills Contact: https://headwayskills.com/contact/ ## Short answer A sunk cost is money, time, or effort you can't get back - and it shouldn't decide what you do next. How to spot the trap and know when to stop. ## Key facts - Title: Sunk Cost: What It Means at Work, and When to Walk Away - Category: Decision Making - Primary skill: Decision-Making - Related skills: Building Resilience, Building Self-Awareness - Primary keyword: sunk cost - Source page: https://headwayskills.com/knowledge/decision-making/sunk-cost/ ## What this page covers - A sunk cost is money, time, or effort you can't get back - and it shouldn't decide what you do next. How to spot the trap and know when to stop. - Practical guidance for sunk cost - How this topic connects to Decision-Making ## Detailed explanation A sunk cost is money, time, or effort you have already spent and cannot get back. Because it is gone whichever way you choose next, it should carry no weight in the decision in front of you — only the costs and benefits still ahead are relevant to that choice. Business and product glossaries state it plainly, and almost everyone agrees on first reading. The trouble starts when it is your budget and your six months. Then the logic that looked obvious turns into a knot: walking away feels like conceding the whole thing was wasted, and carrying on feels like at least giving it a chance. The questions below are the ones people actually ask once they are inside that knot. ## What is a sunk cost? A sunk cost is any expense already incurred that no future decision can recover. Corporate Finance Institute and the product glossaries at ProductPlan and airfocus all draw the same line: a cost is only *relevant* to a decision if it will change depending on what you choose. Sunk costs will not change, so they drop out of the calculation entirely. Indeed's career guide uses a ten-dollar movie ticket: once bought, the money is gone whether you sit through a film you are not enjoying or walk out. At work the same shape shows up with bigger numbers: research and development already spent, a software license already paid for, months of salary already invested in a hire who is not working out. None of it comes back, so none of it belongs in the question *what should we do now?* ## What's the difference between a sunk cost and the sunk cost fallacy? The two get used interchangeably, but they are not the same thing. A sunk cost is a neutral fact of doing anything at all — every organization has them, and having them is not a mistake. The sunk cost fallacy, as Scribbr's explainer frames it, is what happens when that unrecoverable spend is let into a decision it has no business being in: you continue an endeavor because abandoning it would mean the investment was for nothing. That distinction matters more than it sounds. Treat sunk costs themselves as the problem and you end up regretting spending you cannot change. Treat it as a reasoning error in the present tense and the fix is available immediately, in the next decision you make. ## Why is it so hard to walk away from something I've already put so much into? Two forces, and they stack. The first is loss aversion. Kahneman and Tversky's prospect theory established that losses register far more strongly than equivalent gains — roughly twice as painful as the same-sized gain is pleasant. So abandoning a project does not feel neutral; it feels like taking a hit. While the project continues, the loss stays theoretical. Stopping makes it real. Continuing is, in a narrow emotional sense, a way of not yet paying. The second is specific to work: accountability. Stopping a project invites questions about who approved it, who let the overruns through, and who argued for one more quarter — and behavioral-design writing on sunk costs at work describes carrying on as a way of deferring that reckoning. Acuity Training's piece on projects that should have died puts the manager's version bluntly: the fear of walking into the room empty-handed and having to say six months were wasted. Recognizing the pull in the abstract is the easy part; catching it while you are inside it is a habit rather than a piece of knowledge — and habits can be checked, so it is worth knowing [which decision habits serve you](https://assessment.headwayskills.com/) before the next expensive call lands on your desk. ## How do I know when to quit and when to push through? One question does most of the work, and it recurs across nearly every serious treatment of the topic: *if I had not started this yet, knowing what I know now, would I start it today?* If the answer is no, that is your answer. The question strips the past out by construction — it only asks you about the future. Two adjustments make it more reliable. Ask it about the remaining work rather than the whole project: what is on the table is whether the next three months are worth spending, not the last nine. And if you are too close to answer honestly, hand the question to [someone with nothing invested](/knowledge/decision-making/getting-a-second-opinion/). A colleague or manager outside the project sees the situation without the pull, which is precisely why their read is worth more than yours at that moment. ## Is the sunk cost fallacy the same as escalation of commitment? Related, not identical. [Escalation of commitment](/knowledge/decision-making/escalation-of-commitment/) is the broader pattern — the pull to stay consistent with what you have already done, or already said in public that you would do. Sunk cost reasoning is one of its engines, but not the only one: self-justification, social pressure, protecting your role, and ordinary organizational politics all feed the same behavior. The practical difference is where you look for the grip. If it is sunk cost, what holds you is the spend itself. If it is escalation, it is often something you said in a meeting six weeks ago, in front of people whose opinion matters. Different grip, different thing to loosen. ## Isn't quitting just giving up? This is usually the real objection sitting under the question, and it deserves a straight answer rather than a reframe. Persistence is genuinely valuable, and workplaces do reward people who finish what they take on. But persistence is a means, not a virtue in its own right. Continuing to spend on something you would not choose to start today is not perseverance — it is paying to postpone a feeling. The version that holds up is narrower: keep going while the remaining work still looks worth it, stop when it does not, and treat *which* things you stop as the skill rather than whether you stop at all. People who are good at this quit regularly; they are just selective about what. ## How do I tell my manager a project should stop without looking bad? The fear here is real, and it is the main reason dead projects survive: [reporting a failure](/knowledge/confidence/learn-from-mistakes/) feels uncomfortably close to confessing to one. Three moves change how the conversation lands. Lead with the forward-looking case. "Here is what the remaining spend buys us, and here is what the same spend buys somewhere else" is a resourcing argument; "this has not worked" is an admission. Then name what the work actually produced — the thing you learned, the option you ruled out, the research or code that transfers to something else. A stop is far easier to approve when it is framed as redeploying rather than abandoning. Finally, bring a recommendation rather than only a problem: arrive with the [alternative use](/knowledge/decision-making/how-to-calculate-opportunity-cost/) of the time and money already worked out. None of that requires seniority. It requires having done the thinking before you walk in. ## How do I stop this from happening on the next project? Decide the exit conditions before you are invested, which in practice means at the start. Acuity Training's recommendation is to set explicit termination triggers up front — a budget overrun past a defined percentage, or goals missed by a set date — because a rule written while you were neutral is much easier to apply than a judgment made when you are not. Two habits reinforce it. Write the case for continuing in terms of future costs and benefits only, with the spend-to-date deliberately kept out of the document. And put the review in the calendar with someone outside the project, rather than promising yourself you will be objective when the moment arrives. You will not be — that is the point of the trap. ## The skills that make letting go easier Read back through those answers and notice how little of the difficulty is analytical. The arithmetic of a sunk cost takes about a minute to understand. What takes practice is running a clear-eyed process while something in you argues for one more push — and that draws on a few habits that reach well beyond this one trap. **Decision-Making** is where the trap is actually named. It belongs to the same family as confirmation bias, overconfidence, and anchoring: predictable ways a decision goes wrong that you can learn to watch for. Its counter-moves are unglamorous and they work — get another opinion, deliberately including from someone likely to disagree with you; slow down when you notice you are rushed or emotional; decide from hard facts rather than the story you have been telling about the project; and accept a good-enough outcome instead of spending more to chase the one you first pictured. Knowing whether the call is even yours to make is part of it too. **Building Resilience** supplies the mechanism for actually letting go. The central move is separating what you can control from what you cannot, and the months already spent sit as far outside your control as anything ever does — which makes the energy you give them wasted by definition. It also names the thinking that keeps the trap shut: the all-or-nothing read that stopping renders everything worthless, the filtering that lets the encouraging signals through and not the discouraging ones, and the leap to conclusions about how colleagues will judge a reversal you have not even made yet. **Building Self-Awareness** explains why understanding the arithmetic does not rescue you. Underneath the reasoning there is usually a belief you have never examined — that you must finish what you start, or that enough effort turns anything around. Beliefs like those run quietly and drive the overreaction to the idea of stopping. You will rarely catch your own; someone with no stake in the project tends to name it in a sentence, which is one more reason asking is worth the discomfort. A free self-assessment covers those three alongside nine others — **twelve work skills in total**, none of them fixed traits — and since the useful question is not whether you have them but which one is currently the bottleneck, it is worth seeing [where your skills sit today](https://assessment.headwayskills.com/). Some of this probably already describes how you work: the pause before committing more, the instinct to run it past someone with no stake in the outcome. Those are the same behaviors, just unnamed. The parts that do not come naturally yet are learnable, and building them does not ask you to become a different kind of person — it asks for a different move at one specific moment. These calls also get harder to dodge rather than easier: the further you go, the more of your work is deciding what deserves to keep being funded with other people's time. You have already done the part most people skip. You went looking for the concept instead of quietly hoping the project would turn itself around — which is the same instinct the rest of this needs, pointed at yourself for a few minutes. ## Find out where your own decision-making stands The only thing left is to learn which of these habits are already yours. The **free** Job Skills Test is a short self-assessment of your work skills: it scores you across all twelve — the decision-making, resilience, and self-awareness habits behind everything above among them — and shows you which one will make the biggest difference to the calls you are making right now. It takes about 7 minutes, and you finish with a specific place to start rather than a vague sense that you ought to be better at this. **[Take the skills test](https://assessment.headwayskills.com/)** *Free, takes about 7 minutes, and your results appear on screen as soon as you finish.* ## Who this is for - Professionals building practical workplace skills - Readers looking for specific, usable work advice - Managers, educators, and coaches supporting career readiness ## Common questions ### What is this guide about? A sunk cost is money, time, or effort you can't get back - and it shouldn't decide what you do next. How to spot the trap and know when to stop. ### Which Headway skill does this connect to? This guide connects primarily to Decision-Making. It also relates to Building Resilience, Building Self-Awareness. ### What is the recommended next step? Use the free Work Skills Test to reflect on which work skill to improve next. ## Related pages - https://headwayskills.com/knowledge.md - https://headwayskills.com/knowledge/decision-making.md - https://headwayskills.com/knowledge/resilience.md - https://headwayskills.com/knowledge/self-awareness.md - https://headwayskills.com/work-skills-test.md ## Citation guidance Use the canonical page when citing this content: https://headwayskills.com/knowledge/decision-making/sunk-cost/ Preferred summary: "A sunk cost is money, time, or effort you can't get back - and it shouldn't decide what you do next. How to spot the trap and know when to stop." ## Change log - 2026-07-07: Content collection version published.