Updated: 2026-02-20
In trading, Sunk cost fallacy is continuing a behavior because you've already invested time or money, even when the original reasons no longer apply. This glossary entry explains why sunk cost fallacy matters, how traders use it, and how to track it with evidence instead of vibes.
Quick definition
Sunk cost fallacy: continuing a behavior because you've already invested time or money, even when the original reasons no longer apply.
Sunk cost fallacy is continuing a behavior because you've already invested time or money, even when the original reasons no longer apply. The practical version is: can you define it as a field you can log and audit later?
Most trading terms become confusing when they are used as vibes instead of variables. Your goal is a definition that helps you decide size, stop, entry timing, or whether to skip the trade.
Traders sometimes confuse Sunk cost fallacy with discipline. Treat them as separate variables in your journal so your reviews stay honest.
Sunk cost thinking turns small losses into large ones. You hold because you already paid fees, already took heat, or already spent time researching, not because the trade still meets criteria.
If Sunk cost fallacy never changes your decision, it is just jargon. The term earns its place when it improves your process consistency under real market pressure.
A useful mental model: plan first (risk and invalidation), execute second (order type and fills), review last (tags and metrics).
Use it to make one decision pre-trade. Example decisions: where the stop goes, whether to take partials, how to scale size, or whether conditions are too thin to trade.
Write the rule in one sentence, then run it consistently for a week. Consistency matters because it creates comparable data for review.
If the rule fails, adjust slowly. Do not rewrite the whole system after one bad session.
In your journal, record why you stayed in the trade after the plan broke. If the reason is 'I've already come this far', flag it as sunk cost behavior.
Use tags so you can slice results by regime and behavior state. The same term behaves differently when volatility changes or when you are fatigued.
Your review question should be binary: did this variable improve outcomes or reduce rule breaks? If not, simplify.
Your thesis is invalidated, but you keep holding because you 'can't' take the loss after spending all day watching the position. The market keeps moving and the loss compounds.
The point of an example is not to predict price. It is to show what you would log before the trade and what you would audit after the trade.
Reframing sunk cost behavior as patience or long-term conviction without evidence.
The fastest way to improve sunk cost fallacy is to remove one failure mode at a time. If you try to fix everything, you will fix nothing.
Sunk cost fallacy is a state, not an identity. The goal is to detect it early and run a short reset that prevents damage.
The strongest psychological edge is a fast stop to the session when behavior degrades. A flat day is a win if it prevents a drawdown day.
Tag the state, apply a guardrail, then review weekly. If you don't tag it, you will rationalize it.
Sunk cost fallacy is continuing a behavior because you've already invested time or money, even when the original reasons no longer apply. In practice, it matters when it changes a concrete decision like size, stop placement, or whether you skip a trade.
They are related but not identical. In your journal, track Sunk cost fallacy as its own variable and treat discipline as a separate context factor so you can audit each cleanly.
In your journal, record why you stayed in the trade after the plan broke. If the reason is 'I've already come this far', flag it as sunk cost behavior.
Reframing sunk cost behavior as patience or long-term conviction without evidence.
See plans and run one weekly review loop with Tiltless: edges, leaks, and enforceable next actions.
