Free Calculator
What Decision Overload Is Costing You and Your Team
Most managers make 50 to 80 decisions per day and underestimate the count by half. The cost runs in four places: degraded decision quality late in the day, the time the decisions consume, the team waiting on your input, and the cognitive load that compounds toward burnout.
Used for loaded hourly cost of your time
For team bottleneck cost valuation
Most underestimate by 50%. Add 20% to your gut number.
Honest estimate: how many could a competent direct report make?
Cost of decision overload so far
$45,000
Significant. Your bandwidth is the bottleneck.
The cost runs in four places: late-day decision quality drops, time the decisions consume, the team waiting on your input, and the cognitive load compounding toward burnout.
Running per month
$7,500
current burn rate
Your time spent on decisions
22 hrs/wk
of pure decision load
Delegable hours
7 hrs/wk
you could push down
Your burnout risk
12%
over 6 months at this pace
Where the cost is coming from
What Pushing Half Down Would Save
If you cut your decision count by 50 percent (mostly by delegating decisions your team could already make), the cost curve flattens immediately.
Current monthly cost
$7,500
at your current decision count
After cutting decisions in half
$2,500
savings compound monthly
What This Number Means for You
Most decision fatigue is structural, not personal.
If you are at 60-80 decisions per day, the fix is not more discipline or more coffee. The fix is moving decisions off your plate by pushing them down, batching them, or pre-deciding them via clear team policies. The pillar guide on leadership skills for new managers covers this under skill 6 (decision-making under uncertainty), particularly the Type 1 versus Type 2 categorization that lets you stop treating every call as a high-stakes deliberation.
The "delegable but kept" line is the highest-leverage place to cut.
Every decision a competent direct report could make but you are still making is a double cost: your bandwidth plus their development. The article on you're not bad at delegation, you're addicted to being the hero covers the underlying pattern. The sibling "I'll just do it myself" cost calculator quantifies the related trap (doing IC work) which usually rides alongside this one.
Late-day decisions are demonstrably worse, even when they feel fine.
The mechanism is debated. The effect is robust: by hour 8 of a decision-heavy day, your accuracy drops 10 to 20 percent on judgment calls, your willingness to deliberate drops further, and your default-to-status-quo bias rises. The practical fix: stack the highest-stakes decisions in the first three hours of the day, batch the routine ones, and never make a personnel decision after 4pm if you can avoid it.
Why Most New Managers Underestimate Their Decision Load by Half
When you ask a new manager how many decisions they made yesterday, the typical answer lands in the 20-30 range. They are counting the big calls: the hire-or-not, the deadline negotiation, the conversation they had to plan. They are missing the other 40 to 60 decisions that happened in the background: which Slack message to respond to first, which two of four options to recommend in the meeting, whether to push back on a peer's ask, whether to interrupt the engineer or wait until 1-on-1, whether to send the email now or after lunch. None of those feel like decisions in the moment. All of them consume cognitive bandwidth.
The HBR executive tracking research that ran in 2018 found the actual median was 70 decisions per day, with new managers at the high end because they have not yet built the systems and team trust that let routine decisions happen without them. Your honest estimate is probably 60-80. The number in the calculator above is the honest one.
The Four Costs of Decision Overload
Cost 1: Time consumed. At 2 minutes per decision on average (high-stakes ones take longer, routine ones less), 70 decisions per day is roughly 2.3 hours of your day spent purely deciding. That is real time, valued at your loaded hourly rate. Over a week that is 11 to 12 hours of decision load. Over a month at typical knowledge worker pace, the cost is in the four-figure range before any quality or downstream effects.
Cost 2: Quality degradation late in the day. The research on this has had a complicated history (the original "ego depletion" framework has been challenged), but the practical effect is robust: late-day decisions are measurably worse on judgment calls, more biased toward status-quo, and more prone to escape options. A 15 percent quality reduction across the bottom third of your daily decisions translates to roughly $200-400 per day of downstream rework, missed signals, and suboptimal calls for a typical new manager.
Cost 3: Team waiting on your input. When you are decision-fatigued, the team backs up. The deck that needs your sign-off sits in your queue for half a day longer than it should. The cross-team escalation waits for you to find bandwidth. The Slack response that would unblock the team takes hours instead of minutes. Two hours per direct report per week of waiting is conservative for a decision-fatigued manager, and the cost is real, valued at loaded team labor.
Cost 4: Burnout risk that compounds. Microsoft's Work Trend Index has tracked the correlation between sustained cognitive load and manager exit risk. The pattern is consistent: managers operating above 90 decisions per day for sustained periods show measurably higher attrition risk over six to twelve months. The burnout premium in the calculator is the expected replacement cost weighted by that probability.
The Three Highest-Leverage Moves
Three concrete moves, in order of impact:
- Push delegable decisions down. Every decision your direct report makes (rather than checking with you) cuts your count, builds their judgment, and unblocks the team. Pick one category of decision this week (e.g., "anything under $200 is your call without checking"), tell the team, and resist the urge to second-guess. The math compounds across categories.
- Categorize Type 1 vs Type 2 decisions before deliberating. Jeff Bezos's framing: Type 1 = consequential and irreversible (slow down, gather inputs); Type 2 = consequential but reversible (decide fast, review later). Most new-manager decisions are Type 2 misdiagnosed as Type 1. The categorization itself does most of the work. The pillar guide skill 6 covers this in depth.
- Stack the high-stakes decisions in the morning. If you control your calendar, put the personnel decisions, the strategic calls, and the high-stakes deliberation in the first three hours of your day. Move the routine acknowledgments and approvals to the afternoon. The cost of getting this ordering wrong is real and almost completely invisible without auditing your calendar.
One category delegated this week. Type 1/Type 2 tagging starting Monday. High-stakes calls before noon. Three moves, six weeks, dramatically different cost curve.
Frequently Asked Questions
What counts as a "decision" for this calculator?
Is decision fatigue actually a real thing? Some research questions it.
How is the quality degradation estimated?
Why include "delegable but kept" as a separate cost?
What about team bottleneck cost?
How does the burnout risk premium activate?
I am skeptical that my decision count is really 60-80 per day. That sounds high.
What is the single highest-leverage move?
The Cost Curve Bends Down the Day You Stop Making All the Calls.
Pick one category of decision. Push it down. Tag Type 1 vs Type 2 on the rest. Stack the high-stakes ones in the morning. Three moves, six weeks.
Sibling: "I'll Do It Myself" Cost → Related: Manager Leverage →