Sunk cost vs opportunity cost: which costs count in an IT decision
Why money already spent should not decide what to do next, and why the value of the option given up should.
What are sunk cost and opportunity cost?
- Sunk cost: a cost already incurred that no present choice can change or recover: the licences already paid, the consultants' hours already billed, the development already done.
- Opportunity cost: what is given up by choosing one option over the next best one. The analysts assigned to project A cannot work on project B; B's lost benefit is part of the cost of A.
- Relevant (incremental) cost: a future cost that differs between the options. Only these, and the benefits that differ, belong in the comparison.
Sunk costs still matter for other purposes: accounting records them, and the lessons learned from them improve the next decision. They just do not belong in the comparison of what to do from now on.
How does this work on an example?
Made-up figures, for illustration only. A hospital has spent 2 million dollars building its own patient scheduling system. Finishing it would cost another 1.5 million and 18 months. A vendor product that meets the needs would cost 1 million to buy and implement, in six months, with similar running costs.
- The 2 million is sunk: it is spent whether the hospital finishes, buys or stops. It does not belong in the comparison.
- The relevant comparison is 1.5 million and 18 months to finish, against 1 million and six months to buy, plus any difference in fit, risk and support.
- The opportunity cost of finishing includes what the development team could do instead in those 18 months, and a year more without the benefits of a working system.
On these figures buying is the better choice from today, even though it "throws away" the 2 million. That money was lost when it was spent, not when the project stops.
What is the sunk cost fallacy?
The sunk cost fallacy is continuing a course of action because of what has already been invested in it ("we have put too much into this to stop now"), not because of what it will deliver. A closely related pattern in organizations is escalation of commitment: leaders keep adding money to a failing project, often to justify the earlier decision. Research on this goes back to the 1970s (Staw, 1976). Defences include clear go/no-go criteria at each phase gate, reviews by people not tied to the original decision, and a business case that is checked again at each stage against the costs and benefits still to come.
How do the types of cost compare?
| Cost | What it is | In the decision? | Example |
|---|---|---|---|
| Sunk | Already spent and unrecoverable | No | The 2 million already spent on development |
| Opportunity | The benefit of the best alternative given up | Yes | The projects the team cannot do while it finishes this one |
| Relevant (incremental) | A future cost that differs between options | Yes | 1.5 million to finish vs 1 million to buy |
| Common (the same in every option) | A future cost that does not change with the choice | No difference (it cancels out) | The data centre's rent, paid whichever option is chosen |
How are options compared with ROI, payback and NPV?
- Return on investment (ROI) = (benefits − costs) ÷ costs, as a percentage. Simple, but blind to timing.
- Payback period: how long until the accumulated benefits equal the investment. Easy to explain, but it ignores the benefits after payback and, in its simple form, the time value of money.
- Net present value (NPV): the future cash flows of each year discounted to today at the organization's required rate, minus the investment. A positive NPV means the option earns more than that rate; between options, the higher NPV is usually preferred.
- Total cost of ownership (TCO): all costs over the system's life, so that options are compared over the same years.
All of these are calculated on future cash flows from the point of decision: past spending stays out of every one of them.
What do candidates get wrong?
- "We must continue to recover what we spent." Spent money cannot be recovered by spending more; only future results count.
- Choosing the option that has cost the most so far, as if past cost showed value.
- Leaving out the opportunity cost of staff and time, because no invoice shows it.
- Counting costs that are the same in every option. They do not change the choice.
- Judging a long project by ROI or payback alone. NPV accounts for when the money comes.
Summary for revision
- Sunk cost: already spent, unrecoverable, left out of the decision.
- Opportunity cost: the benefit of the best alternative given up, counted.
- Relevant costs are future costs that differ between the options.
- Escalation of commitment is closely related to the sunk cost fallacy; phase gates and fresh reviews guard against it.
- ROI, payback, NPV and TCO all use future cash flows from the point of decision.
Sources
- Managerial accounting: definitions of relevant, sunk and opportunity costs in decision making.
- B. M. Staw, "Knee-deep in the big muddy: a study of escalating commitment to a chosen course of action", Organizational Behavior and Human Performance (1976).
- H. R. Arkes and C. Blumer, "The psychology of sunk cost", Organizational Behavior and Human Decision Processes (1985).
- Project Management Institute, A Guide to the Project Management Body of Knowledge (PMBOK Guide): project selection methods (NPV, payback, ROI).
Related free practice questions
The site files this concept under the domain Management and Leadership.
Try exam-style questions
A 20-question trial exam with an explanation for every option and a score per domain, drawn from 40 free questions. No payment method needed.
Start the trial examQuestions about the exam: CPHIMS guide · What is CPHIMS? · Exam cost · Eligibility · Passing score · Renewal · Exam day · How long to study · Is it worth it? · What is CAHIMS?
Concepts explained: HL7 v2 vs FHIR · Capitation vs fee-for-service · Safe Harbor vs Expert Determination · Incident vs problem vs change · Backup types, RTO and RPO · Privacy Rule vs Security Rule · CDS five rights · Lewin vs Kotter · SDLC and go-live strategies · Testing types · Earned value (SPI, CPI) · Structure, process, outcome · HIE models · Six Sigma vs Lean · Levels of interoperability · Bandwidth vs latency · EMTALA · Risk responses · RACI matrix · Build vs buy · Data governance
The four domains: Healthcare and Technology Environments · Clinical Informatics · Healthcare Information and Systems Management · Management and Leadership
Written by Adel Moustafa, About us
Written and checked against the sources above on 22 October 2026. An independent site, not affiliated with or endorsed by HIMSS. CPHIMS® is a registered trademark of HIMSS.