Sustainable Capacity

Workloads Seen in Context

A spreadsheet that shows eight people booked at 80% capacity looks calm from a distance. Up close, workload sustainability depends on how many conflicting contexts a person holds in working memory, how often unplanned escalations derail their day, and whether critical knowledge is concentrated in a single exhausted specialist.

01

The Myth of 100% Utilization and Kingman's Formula

In traditional resource planning, idle capacity looks like waste. Yet British mathematician J. F. C. Kingman proved in his 1961 queuing approximation that as system utilization approaches 100% in the presence of variability, wait times approach infinity. In knowledge work—where task duration and urgent bug arrivals vary wildly—scheduling a team above 75–80% planned utilization guarantees gridlock.

Furthermore, psychologist Gerald Weinberg documented in Quality Software Management: Systems Thinking (1992) that splitting an individual across three concurrent projects destroys roughly 40% of their effective capacity through context-switching penalties alone.

Close-up of wooden workload tokens stacked unevenly across three columns on a dark ledger sheet
Cognitive Load Theory

Intrinsic, Extraneous, and Germane Load

Educational psychologist John Sweller distinguished between intrinsic load (the inherent difficulty of the task) and extraneous load (clunky tooling, ambiguous specs, noisy deployment steps). Teams rarely burn out from solving interesting hard problems; they burn out from high extraneous load combined with relentless interrupts.

02

Spotting Uneven Pressure Across Roles

Look beyond assigned ticket counts to uncover where pressure actually accumulates inside the team.

Signal 01: Interrupt Concentration

On-Call & Escalation Skew

Track how many production pages, urgent sales requests, or executive ad-hoc questions land on each role per sprint. Often two tenured engineers or operations leads absorb 70% of interrupts while still carrying full project expectations.

Signal 02: Invisible Glue Work

Uncredited Coordination Load

Principal engineer Tanya Reilly popularized the term "glue work" for essential activities like onboarding, cross-team alignment, and design review. If glue work is not budgeted as explicit capacity, the most helpful teammates get penalized on feature output.

Workload Symptom Diagnostic Evidence Structural Remedy
Senior specialists working late nights while juniors wait for tasks High ratio of tasks requiring single-owner domain sign-off Dedicate 20% of senior capacity to pair delivery and architectural runbooks; cap solo ownership.
Everything is started on Monday, nothing finishes by Friday Active WIP exceeds 1.5x the number of team members Enforce column-level WIP limits and adopt a "stop starting, start finishing" daily check.
Planned roadmap slips every sprint due to urgent support Unplanned work arrival rate exceeds 30% of weekly throughput Establish a rotating "designated responder" role shielded from roadmap commitments during their shift.
03

Christina Maslach's Burnout Dimensions in Practice

UC Berkeley researcher Christina Maslach identified that workplace burnout stems not merely from raw work volume, but from six mismatches: workload, control, reward, community, fairness, and values. When teams have zero say in how their capacity is measured—or when metrics ignore chronic under-resourcing—cynicism and exhaustion follow rapidly.

Next: Turn review into adjustment