The Sunk Cost Fallacy: Why You Overvalue What You Paid For
The Sunk Cost Fallacy
The sunk cost fallacy is letting what a player cost you — a high draft pick, a lopsided trade, a big FAAB bid — inflate how you value him now. But that cost is gone whether you keep him or cut him. The only thing that should drive a keep-or-cut, start-or-sit, hold-or-trade decision is a player’s future value. What you paid is history.
| The sunk cost | The trap it creates | The correct question |
|---|---|---|
| A high draft pick | “I can’t cut my 2nd-rounder” | Is he worth a roster spot now? |
| A big trade | “I gave up too much to sell him” | What’s his value going forward? |
| A large FAAB bid | “I spent 60% of my budget on him” | Does he help my lineup this week? |
| Years of loyalty | “I’ve had him since his rookie year” | Would I acquire him today at his price? |
The sunk cost fallacy is one of the most expensive biases in fantasy football because it feels like discipline — “I invested in this guy, I should be patient.” But patience and stubbornness look identical from the inside, and the fallacy is what turns one into the other. Understanding it frees you to make the cold, correct roster decisions that winning requires.
What a Sunk Cost Actually Is
A sunk cost is a resource you’ve already spent and cannot recover. In fantasy, it’s the draft pick you used, the players you traded away, the FAAB you bid, the roster spot-months you’ve held someone. Once spent, that cost is gone — it exists in the past and does not change based on what you do next.
Here’s the key logical point: because a sunk cost is unrecoverable, it should have zero influence on your current decision. Whether you keep a player or cut him, the pick you spent to draft him is equally gone. The only thing your decision affects is the future — what this roster spot does for you from here on. So the only rational input is the player’s forward-looking value, never his acquisition cost.
How It Shows Up in Fantasy
Draft capital attachment. You spent a second-round pick on a running back who’s now buried in a committee and barely usable. Cutting him feels like admitting the pick was wasted — so you hold him for weeks, taking up a roster spot a better player could use. But the pick was “wasted” the moment he busted; holding him doesn’t recover it, it just compounds the loss with a dead roster spot.
Trade regret. You traded a nice package for a player who’s underperformed. You refuse to sell him for what he’s now worth because “I gave up too much” — so you ride him down further instead of recouping something. The assets you traded away are gone regardless; your only choice now is whether to salvage present value or keep bleeding.
FAAB anchoring. You blew 60% of your waiver budget on a breakout who fizzled. You keep starting him to “justify” the spend. The budget is gone; starting a player who doesn’t deserve it just adds a bad lineup decision on top of a bad bid.
Loyalty to old favorites. You’ve rostered a player since his rookie year and can’t bring yourself to move on as he declines. Sentiment and history aren’t value — the years you’ve held him are the definition of a sunk cost.
The Test That Cuts Through It
There’s a simple mental trick that neutralizes the fallacy: ask whether you’d acquire the player today at his current price, ignoring what you paid.
- If a free agent with this exact outlook were available, would you use a roster spot on him? If not, cut your “expensive” bust — the draft pick is irrelevant.
- If someone offered you this player straight up in a trade, would you take him? If not, his acquisition cost shouldn’t stop you from selling.
- If he were on waivers this week, would you start him? If not, bench him regardless of the FAAB you spent.
Reframing the decision as “acquire him fresh, today” strips out the sunk cost entirely and leaves only what matters: his value going forward.
Worked Example: The Second-Round Bust
You drafted a running back in the second round. Ten weeks in, he’s lost his job to a committee and hasn’t been startable in a month. A genuinely useful player — a pass-catching back trending up — sits on waivers, but adding him means cutting your second-rounder.
Sunk cost says: “I can’t drop a second-round pick.” So you hold the dead player and pass on the useful one. But run the test — if that second-rounder were a free agent today with his current outlook, you wouldn’t roster him for a second. The pick you spent is gone either way; the only live question is which player helps you going forward, and it’s clearly the waiver back. Cutting the bust doesn’t waste your pick — the pick was already spent. Holding him wastes a roster spot on top of it.
Common mistake: factoring what a player cost you into whether to keep, start, or trade him. Draft picks, trade packages, and FAAB are sunk the moment they’re spent — they’re gone whether you hold the player or move on, so they should carry exactly zero weight in the decision. Evaluate every player only on his value from here forward, and use the “would I acquire him today?” test to strip out the emotional pull of what you paid.
The Bottom Line
The sunk cost fallacy dresses up stubbornness as patience and costs you roster spots, lineup points, and trade value. What a player cost to acquire is unrecoverable history; it cannot improve by holding on. Judge every keep-or-cut, start-or-sit, and hold-or-trade decision purely on future value, and when the acquisition cost tugs at you, ask whether you’d take the player fresh today at his current price. Let go of what’s already spent, and you’ll make the cold, correct decisions that stubborn managers can’t.
For more on decision-making, roster management, and biases, continue with loss aversion, trade evaluation, and rest-of-season value.