For the first several years of my leadership career, I wore availability as a badge of professionalism. If a team member needed a call to unblock a decision, I said yes. If a senior stakeholder wanted to walk through a proposal at five in the afternoon, I made myself present. If two different people needed my input simultaneously, I prioritized whoever had the more urgent need and absorbed the cognitive cost of context-switching as an acceptable part of the job.
What I was doing, I eventually realized, was systematically degrading the quality of my most consequential decisions while feeling virtuous about my commitment to the team. The decision I made at four in the afternoon — after a day of back-to-back calls, approvals, and small judgments — was not the same quality as the decision I made at nine in the morning, even when the subject matter was equally important to me. Not because I was less intelligent at four than at nine. Because decision-making is cognitively expensive, and cognitive resources are finite in a way that's more like a battery than a reservoir.
The battery metaphor matters because it implies something the reservoir metaphor doesn't: depletion. A depleted decision-maker doesn't make decisions as well as a rested one. The degradation is systematic and predictable, it operates below the threshold of awareness, and it produces specific, identifiable failure modes that are different from just "making bad decisions."
The research on this is older and more robust than most practitioners realize. The most famous study — published by Shai Danziger and colleagues in 2011, tracking Israeli parole board judges over ten months — found that the proportion of favorable rulings dropped from roughly sixty-five percent at the start of each session to nearly zero just before a break, then rebounded sharply after food and rest. The judges weren't biased by the content of the cases at the end of a session — their depletion was producing a systematic shift toward the safest, most conservative default: denial. The same mechanism operates in every organization, on every team, in every decision-making context that involves sustained cognitive work.
What depletion actually does to decisions — the two failure modes
The signature of decision fatigue is not worse decisions in an obvious way — it's not that depleted decision-makers suddenly become careless or irrational in a visible sense. The degradation is more specific. It produces two predictable failure modes that each have their own character and consequences.
The first failure mode is status quo bias: the tendency to approve whatever is already in front of you, to avoid making any change, to pass a decision upward or defer it rather than resolving it. This is what the parole board judges were doing. When cognitive resources are depleted, the brain conserves by avoiding the processing cost of evaluating alternatives. The result is a systematic bias toward the existing state — not because the existing state is actually the best option, but because selecting it requires the least cognitive work.
This failure mode is particularly dangerous because it disguises itself as caution. A leader who says "let's revisit this next week" or "I want to think about this more" may be exercising genuine prudence. Or they may be experiencing a depleted system defaulting to the least cognitively expensive option, which happens to be delay. From the outside, the two are indistinguishable. From the inside, they also feel similar — the impulse to delay feels like good judgment either way.
The second failure mode is simplification bias: the tendency to focus on fewer variables, to give disproportionate weight to whatever consideration is most salient in the moment, and to resist the effort required to hold multiple competing factors in mind simultaneously. Depleted decision-makers don't become stupid — they become narrower. They cut through complexity not because they've found the essential consideration but because their system can't afford to hold the full complexity any longer.
The combination is insidious. A depleted leader late on a Friday afternoon, facing a complex decision with real trade-offs, will tend to either defer it or collapse it into a simpler version of itself that is easier to resolve. The deferral gets called prudence. The simplification gets called decisiveness. Neither is what it appears to be.
The organizational patterns that make fatigue worse — and that leaders can change
Most leadership calendars are filled by other people's needs. The important meeting gets scheduled when everyone is available, not when the decision-maker is at their cognitive best. The stakeholder who needs a commitment gets fifteen minutes at three in the afternoon because that was the first open slot. The major strategic review happens after three hours of operational calls because that's when the executive team could all make it.
These patterns are so ubiquitous that they feel structural — like the water leadership teams swim in rather than a set of choices. But they are choices, and they have systematic consequences. Consequential decisions made at the wrong time in the cognitive cycle don't get the quality of reasoning they deserve. Not because the decision-maker doesn't care, but because the conditions for good reasoning weren't protected.
I've spent enough time observing leadership teams across different organizations and industries to have noticed a consistent pattern: the leaders who make consistently better decisions under uncertainty tend to have more deliberately managed calendars than the leaders who don't. Not more controlled calendars in the sense of being less accessible — in the sense of being more intentional about which decisions happen when. They protect the morning hours for cognitively demanding work. They batch decisions of similar type to reduce context-switching cost. They resist the scheduling convention that says "fit it wherever there's a slot."
There's a specific structural problem that compounds all of this: back-to-back scheduling. The conventional practice of filling a calendar with consecutive thirty- and sixty-minute calls is, from a cognitive resource perspective, a systematic degradation mechanism. Every transition between topics and contexts carries a processing cost. Every call that ends without any recovery time leaves a residue of cognitive load that gets carried into the next one. By the end of a day of back-to-back calls, even a decision-maker who entered the day with full cognitive resources has depleted them incrementally through dozens of small transitions.
The calendar as a leadership discipline
Once decision fatigue is understood as a structural reality rather than a personal weakness, the implications for how to organize your time become both obvious and somewhat radical relative to how most organizational calendars actually work.
The most important implication is temporal sequencing: consequential decisions should happen in the morning, at the start of cognitive sessions, not stacked after a morning of other demands. This requires protecting time explicitly — blocking morning hours on the calendar, communicating to assistants and direct reports that mornings are not available for meetings that don't require decision-making, and accepting the social awkwardness of declining requests for meetings in your best hours.
Barack Obama's famous decision to reduce his wardrobe to gray and blue suits is the canonical example of decision elimination — removing a choice in order to preserve cognitive resources for more important choices. The principle is sound even if the specific application seems trivial: every decision, however small, depletes the resource. Reducing the number of trivial decisions a leader makes frees capacity for the ones that matter. This is why the question "do I actually need to be the one who decides this?" is one of the highest-value questions a leader can ask throughout a day.
There are three approaches to reducing decision load that I've found most useful across my own practice and my observation of other leaders. The first is elimination: examining which decisions you're currently making that don't actually need your involvement, and removing yourself from them. Not delegating — removing the decision entirely from your cognitive landscape. The second is delegation: transferring decisions to other people who are qualified to make them without your involvement, and genuinely giving them the authority to do so rather than requiring ratification. The third is routinization: converting recurring decisions into rules or standing policies that make future instances non-decisions. A hiring approval process that requires me to approve every candidate I've already implicitly approved by approving the job description and the shortlist is a routinizable decision. A policy that specifies the budget level below which team leads can approve without escalation converts dozens of monthly individual decisions into a single standing choice.
The "not now" intervention — the simplest and most effective tool
The hardest thing to implement in practice — and the one I've found most reliably valuable — is a simple practice I think of as the "not now" intervention. When I'm aware that I'm in a depleted state and a non-urgent decision is in front of me, I say "not now" explicitly. I reschedule it. I don't decide it wrong; I defer it to a moment when I'll decide it better.
What makes this hard is that the judgment about "am I depleted?" is itself impaired when you're depleted. The decision-making system that's most degraded is also the system you'd use to assess whether it's degraded. This is why structural rules are more reliable than in-the-moment assessment. No major decisions after three in the afternoon. No consequential commitments stacked the day before or after significant travel. A minimum of one hour of unstructured recovery time after any intensive all-day workshop before making any commitments.
The rules feel arbitrary until you've seen the pattern they protect against. I've caught myself making clear-headed decisions on Monday mornings that directly reversed decisions I'd made on the preceding Friday afternoons — decisions that had felt reasonable in the moment and turned out to be products of fatigue rather than judgment. Once you've seen that pattern clearly enough times, the structural protection becomes not a discipline but a basic professional obligation to the quality of your decisions and the people who depend on them.
Leadership requires good decisions. Good decisions require cognitive resources. Cognitive resources are finite and depletable. That chain of logic, followed honestly and consistently, will improve the quality of your decision-making more reliably than most of what is marketed as leadership development.
Related: Making High-Stakes Decisions Under Genuine Uncertainty, The Hidden Cost of Indecision in Organizations