Skip to main content

Why rational humans make irrational decisions

I always made the assumption that in some way we as humans take rational decisions in a business context. Maybe we do something foolish at home, but at work we weigh options, calculate outcomes, and make logical decisions based on available information. Yes, right?

Then I encountered Daniel Kahneman's Thinking, Fast and Slow, and this comfortable assumption crumbled.

The book reveals a uncomfortable truth: we're far less rational than we'd like to believe. One of the most pervasive examples of our flawed reasoning is the sunk cost fallacy – our tendency to continue investing in failing ventures simply because we've already invested so much.

The blizzard we drive into

Kahneman paints a vivid picture: you've bought expensive concert tickets, but a dangerous blizzard hits on the night of the show. The rational choice is clear – stay home and stay safe. The money is already spent; driving into dangerous conditions won't bring it back. Yet many of us would venture out anyway, unwilling to "waste" the investment.

Created using Bing Image

This same flawed logic plays out at much larger scales. Consider this scenario from the book:

A company has spent $50 million on a struggling project. It's behind schedule, and forecasts look grim. The company can either invest another $60 million to salvage it, or put that money into a promising new project with better returns. What do they choose?

Too often, they choose to "drive into the blizzard" – throwing good money after bad rather than accepting the loss and moving forward strategically.

Why smart people make mistakes

The sunk cost fallacy isn't just about money – it's about psychology. As Kahneman explains, "a rational decision maker is interested only in the future consequences of current investments." But we're not purely rational. We're human.

Several psychological forces conspire against us:

  • Loss aversion: We hate admitting we've made a mistake or wasted resources. The pain of acknowledging a loss often outweighs the logic of cutting our losses.
  • Mental accounting: We create separate mental "accounts" for different investments. Once we've opened an account (bought tickets, started a project, entered a relationship), we feel compelled to see it through.
  • Personal investment: The more we've invested – whether time, money, or reputation – the harder it becomes to walk away. This is especially true when our identity becomes tied to the decision.

The corporate boardroom knows better

Here's a fascinating insight from Kahneman: corporate boards often replace CEOs not because the new CEO is more competent, but because they don't carry the "mental accounts" of past decisions. The outgoing CEO, having championed the failing project, finds it nearly impossible to objectively evaluate whether to continue. The new CEO, unburdened by this history, can make the rational choice to cut losses.

Created using Bing Image

This reveals an important truth: the sunk cost fallacy isn't just a personal failing – it's a systematic bias that affects organizations and institutions.

How sunk costs can trap us

The sunk cost fallacy extends far beyond business decisions. Kahneman notes it "keeps people for too long in poor jobs, unhappy marriages, and unpromising research projects."

Think about your own life:

  • That job no longer interests you, but you're "too far along" to quit
  • The relationship that stopped working years ago, but you've "invested too much" to leave
  • The business venture draining your savings, but you "can't quit now"
  • The hobby or skill you're forcing yourself to continue because of the time already spent

In each case, we're letting past investments dictate future decisions, rather than honestly evaluating our current options.

Breaking free: The antidote to sunk costs

The good news? Research suggests we can overcome this bias, at least partially. Graduate students in economics and business – who explicitly learn about the sunk cost fallacy – are more willing to abandon failing projects than students in other fields.

Here are practical strategies to help you think more clearly:

  • Ask the right question: Instead of "How much have I already invested?" ask "If I were starting fresh today, would I choose this path?"
  • Seek outside perspectives: Find advisors who aren't emotionally invested in your past decisions. They can often see clearly what you cannot.
  • Set decision points: Before starting any significant investment, establish clear criteria for when you'll reevaluate or potentially exit.
  • Reframe "waste": The money, time, or effort you've already spent isn't wasted if you learn from it and make better future decisions.
  • Practice small: Start recognizing sunk cost thinking in low-stakes situations – leaving a boring movie you paid for, abandoning a recipe that's going wrong, or changing plans when the original ones aren't working.

The freedom of walking away

Perhaps the most liberating insight from Kahneman's work is this: you are not obligated to continue something simply because you started it. Your past investments – whether financial, emotional, or temporal – should inform but not imprison your future choices.

The next time you find yourself driving into a blizzard, ask yourself: "Am I making this choice because it's the best path forward, or simply because I can't bear to admit the path I've chosen isn't working?"

Sometimes the most rational decision is to turn around, despite how far you've already traveled. Your future self will thank you for the courage to change course.

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...

A complex system designed from scratch never works

A few years ago, I worked as an architect on a big mainframe rewrite. I still count it as one of my failures. Not because the technology was wrong, but because I couldn't convince the management team to simplify the approach. Years later, the organization is still struggling to get the new system up and running. I left the project at the time, because I couldn't put my name behind an approach that would take very long and cost a lot of money without a working system to show for it along the way. Gall’s Law That memory keeps coming back to me, because it's a textbook case of Gall's Law playing out in real life. Gall's Law , from John Gall's Systemantics , states it plainly: A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works, and it cannot be patched to make it work. You have to start over with a simple system that works. What does that mean in practice,...