Decision Fatigue Doesn't Just Hurt Your Decisions. It Lowers the Bar for How You Make Them.

Read time —
10 Minutes
Last updated
April 22, 2026

I made the wrong call before the conversation even started.

Decision fatigue had already done its work. Simon's reaction told me that immediately. His tone, his language — it wasn't what I expected.

We were supposed to be discussing a price increase. Instead, I was fielding something closer to an attack.

I reacted. Not well.

Reflecting on it afterwards, I could see exactly what had happened. The conversation should have been face-to-face. It was too important for a phone call, and I knew that.

I'd made that judgement somewhere earlier in the day — and then let it slide. By the time I picked up the phone to Simon, I'd already spent hours making decisions.

The bar for what felt acceptable had quietly dropped.

That's the part decision fatigue doesn't tell you about itself. It doesn't announce that your judgement is impaired. It just lowers the standard for what counts as good enough — and you don't notice until you're already in the conversation you shouldn't be having.

Don't Let Fatigue Make This Call for You.

You'll finish the week with a decision — knowing what to do and why.

Work through your decision
One Good Decision — work through the call you've been avoiding

What Decision Fatigue Really Is (And Why the Standard Definition Undersells It)

Decision fatigue is the deterioration of decision quality that follows a sustained period of decision-making. The more decisions you make, the worse your judgement becomes — not because you're less intelligent, but because the mental energy required to engage properly has been spent.

That's the standard definition. It's accurate. But it misses the more damaging mechanism.

Most descriptions of decision fatigue focus on the output — the bad call, the impulsive choice, the defaulted option. What they don't name is what happens before you reach the decision itself. Fatigue doesn't just impair the judgement you apply to a decision — it impairs the judgement you apply to how you set it up.

What a decision actually requires — the right information, the right people, the right format — all of that gets quietly rationed before you're even aware the bar has moved.

It's worth distinguishing decision fatigue from decision overload, because they're related but different problems. Decision overload is too many options in front of you at once. Decision fatigue is depleted capacity from too many decisions already made.

You can experience both simultaneously. But the cause and the fix are different.

The concept has its roots in Roy Baumeister's ego depletion research, which proposed that willpower and self-control draw on a limited cognitive resource that depletes with use. Subsequent research has complicated the glucose-depletion model, and some replication studies have questioned how far the effect extends.

But the underlying observation holds: sustained decision-making degrades decision quality. The degradation begins earlier, and runs deeper, than most leaders recognise.

How Decision Fatigue Actually Works in a Leadership Day

The mechanism sits in the prefrontal cortex — the part of the brain responsible for executive function: weighing options, inhibiting impulse, planning ahead, making considered judgements. It's cognitively expensive. And it tires.

As mental energy depletes, the brain begins to economise. It reaches for shortcuts — ways to reach a conclusion with less cognitive load. Two shortcuts dominate under decision-making fatigue.

The first is status quo bias: a preference for whatever is already in place, because evaluating an alternative requires effort the brain would rather not spend. The second is default bias: accepting whatever option requires the least active choice — the path of least resistance dressed up as a decision.

Neither shortcut feels like fatigue from the inside. Status quo bias feels like consistency. Default bias feels like efficiency.

Both feel like reasonable calls. The fatigued brain is not aware it is economising — it is simply doing what costs least.

There is a third accelerant that most leaders underestimate: the volume of micro-decisions created by constant connectivity.

Every notification that arrives is a decision — reply or ignore, now or later, important or not. Each one is trivial in isolation. But the brain does not distinguish between a trivial micro-decision and a high-stakes one — both draw from the same cognitive resource.

The average person now checks their phone over a hundred times a day. For a leader fielding messages across email, instant messaging, and calls simultaneously, the decision count is far higher than anything their parents' generation faced in the same role.

This is what makes modern decision-making fatigue structurally different from its historical equivalent. It's not just that the day contains difficult decisions. It's that the day contains thousands of small ones, each consuming a fraction of the attention required for the difficult ones, adding up before the difficult ones even arrive.

Steph was one of the busiest managers I'd worked alongside — genuinely admirable in her pace and availability. She was always reachable, always in a meeting, always fielding a question.

Then one of our clients surfaced a problem that needed data and analysis to understand. The general manager assigned it to Steph. It was exactly the kind of task she was capable of handling.

Days passed. Then weeks. The task sat on her list.

The GM grew frustrated as client calls mounted. Steph knew it needed doing — she'd say so. But she couldn't find the mental bandwidth to begin it.

The busyness that looked like high performance had consumed every reserve she had. There was nothing left for a task that required sustained, uninterrupted thinking. She wasn't failing to prioritise it — she was failing to have anything left to give it.

That's what chronic decision fatigue looks like in a leadership context. Not a single bad call at the end of a depleted day. The permanent inability to access the depth of thinking that the role actually requires.

Decision Fatigue Examples: What It Looks Like for Leaders at Work

The clearest research evidence of what decision fatigue does to professional judgement comes from a 2011 study by Shai Danziger and colleagues, examining parole board decisions across more than 1,000 rulings. Judges granted parole to roughly 65% of cases heard at the start of each session. By the end, that figure dropped to near zero.

After a break — food, rest — it reset.

The study has faced methodological scrutiny, with a 2020 reanalysis by Andreas Glöckner suggesting the pattern may partly reflect meal-break scheduling rather than pure cognitive depletion. But the directional finding — that decision quality degrades across a sustained session and recovers with rest — remains one of the most cited observations in decision fatigue research.

Any leader who has sat through a full day of back-to-back meetings will recognise the shape of it.

The decision fatigue examples that matter most for leaders at work are rarely the headline calls. They're the process decisions that precede them.

An executive reviewing proposals late in the afternoon doesn't necessarily approve a bad strategy. She approves a strategy without asking the questions she would have asked at 9am. The cognitive load of the day has raised the cost of rigorous engagement.

The decision gets made. The process that should have surrounded it gets quietly rationed.

A head of operations — managing three competing stakeholder demands, five consecutive meetings, and a deadline that has moved twice — doesn't necessarily make the wrong call on the big decision. She makes the wrong call about how to handle it.

She sends a message when she should have picked up the phone. She defers a conversation she knew needed to happen today. She agrees to something in a meeting because revisiting it would cost more than she has left.

The decision-making fatigue shows up in the margins — in the format choices, the timing choices, the framing choices. Not in the headline decisions that would later be scrutinised.

That's the pattern that makes decision fatigue in business so difficult to detect. The visible decisions often look fine. It's the invisible process decisions surrounding them that degrade first.

Why Decision Fatigue Is a Leadership Problem, Not Just a Personal One

The cost of decision fatigue doesn't stop with the individual making the decisions. It spreads.

When a leader's decision-making process visibly degrades — when they default, defer, or settle — it sends a signal to the team. Not always a conscious signal. But the team notices when questions aren't asked that should be.

They notice when a difficult conversation gets pushed to email. When a decision lands in a meeting that clearly needed more preparation. When the standard for how things get handled quietly shifts downward.

Over time, a leader's tolerance for a lowered process bar becomes the team's tolerance. That's not a performance issue you can address in a one-to-one. It's a cultural drift — gradual, invisible, and expensive.

Poor decision-making at the leadership level — driven by indecision, fatigue, or both — cascades into delayed projects, misaligned priorities, and teams that lose confidence in the direction they're receiving.

The Steph situation illustrates this from the other direction. Her team had constant access to her, but the organisation couldn't get what it actually needed: a leader with enough in reserve to tackle a difficult, ambiguous problem.

Availability and capacity are not the same thing. Decision fatigue collapses the difference between them.

Decision fatigue productivity losses are rarely measured, because the degradation is gradual and the link to individual decisions is invisible. The compounded cost of slightly worse process decisions, made consistently across a leadership team, is significant.

How to Manage Decision Fatigue: Protecting How You Decide, Not Just What You Decide

Most advice on managing decision fatigue focuses on volume — batch decisions, delegate them, eliminate them. That's useful. But it addresses the symptom rather than the mechanism.

If the real damage is to the process bar, the intervention needs to protect how decisions get set up — not just reduce how many there are.

Three approaches follow directly from the mechanism.

Schedule decisions by what they require, not by when they're convenient. High-process decisions — conversations that need to be face-to-face, proposals that need genuine scrutiny, problems that need uninterrupted thinking — belong in the first half of the day. Not because you're smarter then, but because your standard for good enough process is higher.

The fatigued version of you will accept the phone call. The morning version knows it needs to be a meeting. Protecting that distinction requires scheduling by decision type, not by availability.

Had Steph ring-fenced two hours in the morning for the client analysis — before the questions started arriving, before the meetings began — she would have had a different outcome. The task wasn't beyond her. The timing was wrong.

Make the meta-decision a habit. Ask one question before any significant conversation or call: is this the right way to have this decision? Not what should I decide — but how should this decision be made?

Who needs to be in the room? What format does this conversation actually require? How much time does it genuinely need?

That question takes ten seconds. Building it as a reflex — a habit of pausing and reflecting before engaging — protects the process bar that fatigue quietly lowers throughout the day.

It's the single most useful thing that came out of the Simon situation: not a lesson about price conversations, but a trigger question that now runs before any conversation that matters.

Learn to recognise the shortcuts, not just the feeling. The fatigued brain doesn't announce itself as tired. It announces itself through behaviour.

If you find yourself reaching for the familiar option without examining it — that's status quo bias at work. If you're accepting whatever is already in place rather than actively choosing — that's default bias. You won't feel depleted. You'll feel efficient.

The behaviour is the tell, not the subjective experience of tiredness. Knowing which specific shortcuts your brain reaches for under cognitive load is more useful than monitoring how you feel — because by the time you feel it, the decisions have already been made.

For a full framework on building the decision process that protects against these patterns, the Leader's Guide to Decision Making covers the complete approach.

The Question to Sit With

Think back to last week. Not the big decision you made — the one you'd name if someone asked how your week went.

Think instead about a decision you made about how to handle something. A conversation you had by message when you knew it needed more. A call you took at the wrong time of day.

That's where decision fatigue lives. Not in the headlines. In the process choices you made before the headlines arrived.

Which one, last week, did you know at the time wasn't quite right?

FAQs

Is decision fatigue really about making bad decisions?

Not primarily. The more corrosive effect is on the decisions you make about how to decide — the format you choose, the preparation you do, the conversation you set up. By the time you reach the decision itself, the conditions for making it well have already been compromised.

How do I know if decision fatigue is affecting my leadership?

Watch for the shortcuts, not the feeling. If you're reaching for the familiar option without examining it, that's status quo bias. If you're accepting whatever's already in place rather than actively choosing, that's default bias. The fatigued brain doesn't feel tired — it feels efficient.

What's the difference between decision fatigue and decision overload?

Decision overload is too many options in front of you at once. Decision fatigue is depleted capacity from too many decisions already made. You can experience both simultaneously, but they need different fixes. Overload is a structural problem. Fatigue is a timing and recovery problem.

How do I protect my best thinking from decision fatigue?

Ask one question before any significant conversation: is this the right way to have this decision? Not what to decide — but how. Scheduling high-process decisions for the morning, before cognitive load accumulates, is where to start. One Good Decision walks you through it on a real decision you're facing.

How does decision fatigue connect to indecision in leadership?

They often arrive together. Fatigue depletes the mental bandwidth required to push through a difficult call, which creates the conditions for indecision to take hold. The difference is the cause: indecision is often structural, fatigue is cumulative. Addressing one without the other leaves the problem half-solved.

Don't Let Fatigue Make This Call for You.

You'll finish the week with a decision — knowing what to do and why.

Work through your decision
One Good Decision — work through the call you've been avoiding

Written by

Darren Matthews Profile Picture
About
Darren Matthews
After a decade of studying decision-making, I share clear, practical advice to help business professionals make smarter choices.

Your Next Read...