Decision Fatigue: Why Your Best Work Has to Happen First

It’s 3pm. You’ve been productive all day — answered emails, helped a teammate debug a weird CSS issue, picked a restaurant for lunch, reviewed two PRs, replied to a thread about the sprint scope. Now you finally sit down to design that new API. And your brain just… won’t cooperate.

You stare at the screen. You know what needs to happen. But choosing between approaches feels weirdly exhausting. So you check Slack instead. Then you refactor something that didn’t need refactoring. The hard thinking never happens.

This isn’t laziness. It’s decision fatigue. And once I understood it, it changed how I structure my entire day.

Your Brain Has a Daily Budget

In the late 1990s, psychologist Roy Baumeister ran a now-famous experiment. He put two groups of people in a room with freshly baked cookies and radishes. One group could eat the cookies. The other had to resist the cookies and eat only radishes. Afterward, both groups were given a difficult puzzle.

The radish group gave up almost twice as fast.

Not because they were worse at puzzles. Because they’d already spent willpower resisting the cookies. Baumeister called this “ego depletion” — the idea that self-control and decision-making draw from the same limited pool of mental energy. Use it up on one thing, and you have less for everything else.

Think of it like a rate-limited API. You start the day with a generous quota. Every decision — big or small — costs a request. Choosing what to wear, deciding what to eat for breakfast, answering “should I reply to this message now or later,” figuring out which task to start with. Each one counts. And once you hit the limit, every subsequent call takes longer, returns worse results, or just times out.

The Judge Study That Makes It Real

There’s a study by Danziger, Levav and Avnaim-Pesso that looked at over 1,100 parole decisions made by Israeli judges across 50 days. Each judge reviewed around 14 to 35 cases per session.

The pattern was striking. At the start of the day, judges approved parole roughly 65% of the time. By the end of a session, that rate dropped to nearly zero. After a food break, it jumped right back to 65%.

Same judges. Same types of cases. Completely different outcomes based on when the case was heard. As the judges made more decisions, they defaulted to the easiest option — deny parole, maintain the status quo. Making a thoughtful, reasoned choice to grant parole required more mental effort. And they’d run out.

If decision fatigue can affect literal life-and-freedom outcomes, imagine what it does to your code quality at 4pm.

Why Developers Get Hit Especially Hard

Here’s the thing most productivity advice misses: programming is almost entirely decision-making.

Every line of code is a choice. What should this variable be named? Should this be a function or a method? Do I handle this error here or let it bubble up? Should this be a separate component? Is this abstraction worth it?

A typical coding session involves hundreds of these micro-decisions. And they’re not trivial — each one affects readability, performance, and maintainability down the line. Your brain treats them the same way it treats deciding what to have for lunch. They all pull from the same pool.

That’s why you can feel completely drained after a day of coding even though you never left your chair. You haven’t done any physical work. But you’ve made more decisions in eight hours than most people make in a week.

See the problem? By the time you get to the decisions that actually matter — the architectural choices, the design trade-offs — you’ve already burned through half your budget on things that didn’t matter at all.

The Same Outfit Every Day

This is why Steve Jobs wore the same black turtleneck and jeans every day. Why Mark Zuckerberg wore the same grey t-shirt. Why Obama said he only wore blue or grey suits.

It’s not a fashion statement. It’s a willpower strategy.

Obama put it clearly in a 2012 interview: “I’m trying to pare down decisions. I don’t want to make decisions about what I’m eating or wearing. Because I have too many other decisions to make.”

These are people whose entire days are filled with high-stakes decisions. They figured out that wasting mental energy on “which shirt today?” is an expense they can’t afford. So they eliminated the choice entirely.

You don’t have to go full uniform. But the principle is powerful: every trivial decision you can remove or automate frees up capacity for the decisions that actually matter.

What to Actually Do About It

Knowing about decision fatigue is useful. But knowing alone doesn’t fix anything. Here’s what’s worked for me.

Do the hard thing first

This is the most important change. Whatever your most demanding task is — the complex feature, the tricky bug, the system design — do it first thing in the morning. Before email. Before Slack. Before standup if you can manage it.

Your willpower tank is fullest when you wake up. That’s when you have the most capacity for difficult, creative thinking. Don’t waste it on inbox triage.

Automate the trivial decisions

Lay out your clothes the night before. Better yet, have a few go-to outfits you rotate without thinking. Meal prep on Sunday or eat the same breakfast every day. Set a default route to work. Have a default lunch spot.

Each of these saves a tiny amount of willpower. But they add up. It’s like optimizing a hot path in your code — the individual gains are small, but they compound.

Build decision-free routines

My morning is almost entirely automated. Wake up, same breakfast, same clothes rotation, same commute. I don’t make a single real decision until I sit down at my desk. And that first decision is always “open the editor and work on what I left off yesterday.”

The routine is the point. Not because routines are exciting, but because they eliminate the need to decide.

Use “if-then” rules

Instead of deciding in the moment, pre-decide. “If it’s Monday, I do code reviews at 2pm.” “If a Slack message isn’t urgent, I respond at 3pm.” “If I’m stuck on a problem for 30 minutes, I take a walk.”

These rules remove the decision entirely. The situation triggers the action. No willpower required.

Eat. Seriously.

Baumeister’s research found a link between blood glucose levels and self-control. When glucose drops, decision-making gets worse. This isn’t about sugar rushes — it’s about your brain literally needing fuel to make choices.

Don’t skip meals. Don’t try to power through on coffee alone. Have a snack mid-morning. Eat a real lunch. Your afternoon self will thank you.

The Deep Work Connection

Cal Newport’s concept of “deep work” fits perfectly with this. Your best, most creative, most architecturally sound thinking happens when you have plenty of willpower left. That’s why morning deep work sessions feel almost effortless compared to trying the same work at 4pm.

It’s not that you’re a “morning person.” It’s that you haven’t spent 200 API calls on trivial decisions yet.

Protecting your morning isn’t about discipline. It’s about math. You have a finite resource. Spend it where it counts.

Start Small

You don’t need to overhaul your life. Pick one thing.

Tomorrow morning, do your hardest task before you check any messages. That’s it. One change. See how it feels. See what you produce compared to a normal day where you ease in with email and Slack.

If it works — and it probably will — then start removing one trivial decision at a time. Same breakfast Monday through Friday. Clothes laid out the night before. A fixed time for email.

Not because it’s glamorous. Because your willpower is too valuable to spend on things that don’t matter.

Sources:

• Ego Depletion — Roy Baumeister et al. — the original 1998 willpower experiment
• Extraneous Factors in Judicial Decisions — Danziger, Levav, Avnaim-Pesso — the Israeli parole decisions study
• Deep Work by Cal Newport — on the connection between willpower and deep focus
• Vanity Fair Obama Interview, 2012 — Obama’s quote on decision reduction