Manager vs. IC Decision Load: The Overhead Nobody Measures

The common assumption is that managers burn out because they make harder decisions. Hiring, firing, budget allocation — high-stakes calls that carry weight. But when you look at DLI patterns across role types, the picture is different. Managers don’t report harder decisions. They report more decisions.

Where the Load Concentrates

DLI scores break into five dimensions. When comparing self-reported role types (manager vs. individual contributor), the distribution differs more than the total:

The most striking difference is context switching. A manager’s day is structurally fragmented: a 1:1 followed by a budget review followed by a Slack escalation followed by a hiring debrief. Each transition resets working memory. An IC who does deep work for 90 minutes and then checks Slack has made one context switch. A manager in the same 90 minutes may have made four.

The Invisible Tax: Delegation Decisions

Individual contributors rarely think about delegation as a decision category. But for managers, every task triggers a chain: Should I do this myself or assign it? Who is available? Who has the right skills? Will they need context? How much context? When do I follow up? What if they get stuck?

A single incoming request that an IC would just do generates five to seven decisions for a manager before any work begins. These delegation decisions are cognitively invisible — they don’t show up in calendars, task lists, or time tracking. But they show up in DLI scores.

The IC Counterpoint: Deep Ambiguity

ICs are not immune to high decision load. The ambiguity dimension tells a different story. An IC working on a complex technical problem with unclear requirements can carry extremely high decision load — not from volume, but from the weight of each unresolved question.

A senior engineer deciding on an architecture pattern carries one decision. But that decision may have dozens of downstream implications, and the uncertainty of “is this the right call?” generates sustained cognitive cost. The DLI captures this as ambiguity load rather than volume load.

What This Suggests

If decision load differs by type across roles, then interventions should differ too:

• Managers: Reducing context switches and creating delegation templates may lower load more than “time management” techniques. The bottleneck is not time — it is the number of cognitive mode changes per hour.
• ICs: Reducing ambiguity — clearer requirements, earlier architectural decisions, explicit scope boundaries — may matter more than reducing meeting count.
• Both: Externalizing open loops (writing down unresolved decisions) appears to reduce load regardless of role type. This finding is consistent with the 7-day retest data.

What This Does Not Mean

This is observational data from self-reported role types. We cannot claim that management causes higher context-switching load — it is possible that high context-switchers self-select into management roles. The correlation is clear; the direction of causation is not.

We also cannot claim these patterns hold across all organizations. A manager at a 10-person startup and a manager at a 10,000-person enterprise face structurally different decision environments.

This is a research field note based on observational, self-reported data. Patterns described are correlational, not causal. This content is educational and does not constitute professional advice. Individual results vary.