Opportunity Cost: The Value of the Road Not Taken
Opportunity cost is the value of the best alternative you forgo when making a choice. It's used to prioritize projects when resources are scarce, like choosing a new feature over a refactor. The footgun is ignoring non-monetary costs like lost time or utility.
WHY IT EXISTS: Resources like time, money, and people are always limited. You can't do everything. Opportunity cost provides a framework for making rational choices between mutually exclusive alternatives by forcing you to consider not just what you gain, but also what you give up.
THE MENTAL MODEL: Every choice has a 'shadow price' — the value of the best option you didn't take. If you choose to spend an afternoon refactoring code, the opportunity cost isn't zero; it's the value of the new feature you could have built in that same time. It forces the question: "What is the best alternative use of these resources?"
HOW IT WORKS: To find the opportunity cost, you identify the value of your chosen path and subtract the value of the next-best alternative. The 'value' isn't just money. It can be time saved, pleasure gained, or any other useful benefit (utility). The cost includes both explicit, out-of-pocket expenses and implicit, non-monetary benefits you're forgoing.
WHEN TO USE IT: Use this concept when making decisions with scarce resources. This applies to high-level strategy, like choosing which market to enter, and daily engineering work, like deciding whether to fix tech debt or ship a new feature. It's a tool for prioritization and ensuring you're using resources efficiently.
WHEN NOT TO USE IT: The concept is less useful for choices that are not mutually exclusive (where you can do both) or when the value of alternatives is impossible to estimate meaningfully. It is a forward-looking tool for decision-making, not a backward-looking analysis of past expenses.
ONE CANONICAL EXAMPLE: An engineering team has the capacity to work on one of two projects. Project A is a new feature projected to generate 150k in new revenue. Project B is a database migration projected to save 80k in operational costs. The team chooses Project A. While they gain 150k, their opportunity cost is the 80k in savings they gave up by not choosing Project B.
Read the original → en.wikipedia.org
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.