The 10 a.m. team and the 4 p.m. team are not the same people
Think of a decision your team made carefully — someone laid out the trade-offs, two people pushed back, a third asked the awkward question everyone was avoiding, and the choice that emerged was better for the friction. Now think of a decision that just sort of happened. Someone said, "Let's go with that for now," nobody objected, and it was on the calendar as settled before anyone had really weighed it.
There's a decent chance the first meeting was in the morning and the second was late in the afternoon. Not because the afternoon team was lazier or less capable. They were the same people. They were just further into their day, and the day had been quietly spending something you can't see on a calendar: their capacity to decide well.
This is decision fatigue, and it's one of the most underrated forces shaping what your meetings actually produce.
What decision fatigue actually is
The idea comes out of research by psychologist Roy Baumeister and colleagues, who studied what they called ego depletion — the observation that after people exert deliberate self-control or work through a series of effortful choices, they tend to do worse on the next task that also demands effort. Kathleen Vohs and collaborators extended this specifically to decision-making: the act of choosing, over and over, seemed to leave people less willing or able to choose carefully afterward.
It's worth being honest about the science here, because it's more contested than the pop-psychology version admits. The strong claim — that willpower is a literal fuel tank that empties — has taken real hits; a large multi-lab replication in 2016 found the effect much smaller and shakier than the original studies suggested. So treat "your brain runs out of gas" as a metaphor, not a mechanism.
But the softer, more robust observation survives all of that: as decisions pile up, people don't keep deciding with the same care. They start taking shortcuts. And in a meeting, those shortcuts have very specific, recognizable shapes.
The three shortcuts a tired room reaches for
When deliberation gets expensive, the mind doesn't announce it's cutting corners. It just quietly swaps effortful thinking for something cheaper. Watch for three moves.
Defaulting to the status quo. The easiest decision is the one that requires no change. A fresh team will interrogate whether the current process is still worth keeping. A depleted one keeps it, not because it's best but because keeping it costs nothing right now. "Let's leave it as is for this cycle" is often decision fatigue wearing the costume of prudence.
Deferring. "Let's take this offline." "Let's revisit next week." "Let's get more data first." Sometimes these are genuinely wise. But late in a long day they multiply, and they're frequently a way of not deciding while feeling like you've made progress. The decision doesn't get better in the interval — it just gets re-litigated by an equally tired room next time.
Deciding by shortcut cue. When weighing the actual merits feels too effortful, people lean on a proxy: whoever spoke most confidently, whoever's most senior, whichever option was mentioned first. The reasoning gets outsourced to a signal that's easy to read. This is where decision fatigue quietly hands the room over to other biases — authority, anchoring, loudness — that a rested team would have resisted.
None of these feel like fatigue from the inside. They feel like reasonable, even efficient, meeting behavior. That's exactly what makes them hard to catch.
The parole board that got hungry
The most cited illustration of this comes from a 2011 study of an Israeli parole board, published by Shai Danziger and colleagues. The researchers tracked thousands of rulings and found that the share of favorable decisions was high at the start of a session and declined as the session wore on — then jumped back up right after the judges took a food break, before drifting down again.
The tidy interpretation was decision fatigue: a favorable ruling is the effortful, individualized choice, and a denial is the safe default, so tired judges defaulted more. It's a genuinely striking pattern, and it's stuck in the popular imagination for good reason.
It's also fair to note the debate. Later critics argued the cases may not have been ordered randomly — prisoners with representation were often scheduled earlier, for instance — which could explain part of the curve without invoking fatigue at all. The truth is probably somewhere in between. But even skeptics don't dispute the shape most of us recognize from our own calendars: the caliber of judgment a group brings to a decision is not a fixed trait. It bends over the course of a day.
Why meetings are especially exposed
A meeting concentrates decisions the way almost nothing else in a workday does. In an hour, a room might settle a budget line, resolve a hiring debate, pick between two roadmaps, and approve a launch date — each one a real choice, stacked back to back with no recovery time.
And meetings tend to cluster in exactly the way that compounds the problem. The person walking into a 4 p.m. decision meeting has often already spent the day in five earlier ones, each demanding attention, judgment, and the small effortful choices of when to speak and when to concede. They arrive at the moment that matters most already having spent the most.
There's a second trap: the important decision is frequently saved for last. Teams warm up on logistics and status and put the hard call at the end of the agenda, reasoning that it deserves the most time. But it gets the most depleted time — the tail of the meeting, at the tail of the day, when the room is most likely to default, defer, or follow the loudest voice.
Scheduling as a design choice
The useful thing about decision fatigue is that, unlike most cognitive biases, its main lever is embarrassingly practical: when.
Put the decisions that matter early. Not just early in the day, but early in the meeting, before the room has spent itself on things that don't matter as much. If a single choice will shape the next quarter, it should not be item seven.
Protect the morning for judgment, not just for focus work. The instinct to schedule "quick syncs" first thing and save the big call for the afternoon has it backwards. Trade them.
Use breaks deliberately. The parole study's most reliable feature wasn't the decline — it was the rebound after a pause. A ten-minute break before a consequential decision isn't slack; it's a reset that changes the quality of what follows.
And separate deciding from everything else. A meeting that reviews status, brainstorms, and decides asks the room to switch modes repeatedly, and each switch costs something. Pulling the decision into its own short, well-placed slot — with a rested room and a clear question — often beats an hour of everything-at-once.
Finally, notice the tells. When you hear a run of "let's circle back" and "leave it for now" and "whatever you think is best," that's not necessarily consensus. It may be a room that has run out of the appetite to decide, and the honest move is to stop and finish the real choices tomorrow morning.
The decision you can't see on the calendar
What makes decision fatigue slippery is that it never shows up in the meeting notes. The notes say a decision was made. They don't say it was made at 4:40 p.m. by people who'd already decided forty things that day, or that the same group, fresh, might have chosen differently. The cost is invisible precisely because a decision did get reached — it just wasn't the one careful thinking would have produced.
That invisibility is the whole problem, and it's what meetingmortem is built to make visible. By capturing when decisions actually happen — the time of day, the position in a stacked calendar, the pattern of choices that get deferred versus resolved — it surfaces the quiet drift that no single meeting reveals on its own, so you can move the choices that matter to the hours when your team can actually make them.
If you've ever suspected your best decisions and your worst ones are separated less by the problem and more by the clock, it's worth seeing the pattern for yourself: https://meetingmortem.lumenlabs.works