Skip to main content
New: Deck Doctor. Upload your deck, get CPO-level feedback. 7-day free trial.
Back to Glossary
StrategyO

Opportunity Cost

What is Opportunity Cost?

Opportunity cost is the value of the next best option you forgo when making a decision. In product management, it means: every engineering sprint you allocate to one initiative is a sprint you cannot allocate to another. The value of that unchosen initiative is your opportunity cost.

This concept is borrowed from economics but is critically relevant to PMs who manage fixed capacity. You never evaluate a feature in isolation. You evaluate it against everything else you could be doing.

Why Opportunity Cost Matters

Teams evaluate features by asking "Is this worth building?" The right question is "Is this the most valuable thing we could build right now?" A feature that generates $50K in value is good in isolation but bad if it displaces a feature that would generate $200K.

Opportunity cost also applies to time. The cost of delay framework quantifies what you lose by shipping later. Building Feature A now and Feature B next quarter means Feature B's value is delayed by 3 months.

How to Use Opportunity Cost in Decisions

List your alternatives. Before committing to any initiative, explicitly identify what else you could do with the same resources. Make the trade-off visible.

Estimate comparative impact. You do not need precise numbers. Rough orders of magnitude work: "Feature A affects 1,000 users, Feature B affects 10,000 users." This reveals when opportunity cost is high.

Consider time sensitivity. Some opportunities have deadlines (seasonal features, competitive responses, regulatory requirements). Missing the window eliminates the option entirely, making the opportunity cost infinite.

Use opportunity cost in stakeholder conversations. When a VP asks why you are not building their request, explain: "Building X means we cannot build Y. Here is why Y is more valuable right now." This reframes the conversation from "why not" to "compared to what."

Opportunity Cost in Practice

Amazon's "two-way door" framework incorporates opportunity cost. Reversible decisions (two-way doors) have low opportunity cost because you can undo them. Irreversible decisions (one-way doors) have high opportunity cost and deserve more analysis.

Netflix's culture memo explicitly acknowledges opportunity cost: "We don't have the luxury of doing everything. We must choose." Their product teams use this principle to kill features that are merely good to focus on features that are great.

Common Pitfalls

  • Invisible costs. The feature you did not build never shows up in a post-mortem. Track what you chose not to do and periodically assess whether the trade-off was right.
  • Sunk cost confusion. Past investment does not justify continued investment. If a better opportunity emerges, the cost already spent is irrelevant.
  • Comparing to zero. Evaluating whether a feature is "worth it" in absolute terms ignores opportunity cost. Always compare against the next best use of resources.
  • Paralysis. Opportunity cost can paralyze decision-making. Set timeboxes for analysis and accept that imperfect decisions made quickly often outperform perfect decisions made slowly.

Opportunity cost is central to prioritization and feature prioritization. The cost of delay framework quantifies the time dimension of opportunity cost. It connects to product strategy for resource allocation decisions. Use the RICE calculator to compare options systematically.

Frequently Asked Questions

How do you calculate opportunity cost in product management?+
Estimate the expected impact of the options you are choosing between. If Feature A will generate $100K in annual revenue and Feature B will generate $200K, the opportunity cost of choosing Feature A is $200K. In practice, these estimates are imprecise, but the exercise forces rigorous comparison.
Why do teams often ignore opportunity cost?+
Because it is invisible. The cost of building Feature A shows up on your sprint board. The cost of not building Feature B is hypothetical and never appears in any report. This asymmetry biases teams toward evaluating what they build rather than what they sacrifice.
Free PDF

Get the PM Toolkit Cheat Sheet

All key PM concepts, tools, and frameworks in a printable 2-page PDF. The reference card for terms like this one.

or use email

Instant PDF download. One email per week after that.

Want full SaaS idea playbooks with market research?

Explore Ideas Pro →

Explore More PM Terms

Browse our complete glossary of 100+ product management terms.