What to Do When There's Too Much Work
Gretchen Gavett Β· article Β· 2026-09-22 Reader π₯οΈ
Burnout & RecoveryCognitive LoadOrganizational LegibilityPsychological SafetyRole Stress Taxonomy (Overload / Ambiguity / Conflict)Team Autonomy
When a team is overloaded, the leader's instinct to personally absorb the excess work is the wrong fix because it merely burns the leader out without solving anything; the real levers are diagnostic (confirm the stressor is actually workload, not role ambiguity or role conflict) and structural (redistribute decision-making capacity itself β externalizing tacit judgment criteria and pushing real authority, not just tasks, downward) rather than adding capacity or subtracting volume.
practical Β· expository β This is Gavett's 'The Insider' newsletter roundup, not a single self-contained essay: it digests and juxtaposes two HBR pieces (Melody Wilding on leader-absorbed overload; Sawhney & McCord's meta-analytic research on workplace stressors), then adds shorter AI-related pointers and a separate item on dominating/micromanaging. The unity below is the thesis Gavett constructs by placing the two lead pieces back to back, even though she never states it as a single claim herself.
Structure
| Part | Role |
|---|---|
| Opening framing: HBR subscribers consistently report work volume as a persistent pain point, with causes (AI, layoffs, budget crises) treated as interchangeable and largely given. | context |
| Wilding's five strategies for leaders whose teams are overloaded, with 'downloading your thinking' and 'pushing authority down, not just tasks' highlighted | evidence / main prescriptive argument |
| Sawhney & McCord's 60-years/515-study research distinguishing role overload, role ambiguity, and role conflict as separate stressors | evidence / diagnostic qualifier |
| Four brief AI-related pointers (capex/macroeconomy framing, process redesign over automation, AI and psychological safety, 'process collapse' in creative work) | tangential context, loosely thematically linked to organizational overload |
| Matviak & Gardiner's research on dominating conversations and micromanaging as collaboration-damaging behaviors senior leaders underestimate in themselves | parallel argument thread on leader behavior, not directly about workload |
| Closing must-reads list and a reminder to celebrate wins | flavor / newsletter convention |
Key terms
- Downloading your thinking
Wilding's term (via Gavett) for a leader explicitly articulating the criteria they weigh, the factors they prioritize, and what they let slide and why β converting tacit personal judgment into a shareable, applicable rule set so the team can act without routing decisions through the leader. - Role overload / role ambiguity / role conflict
Three distinct categories of workplace stressor from Sawhney & McCord's research: role overload is too much work; role ambiguity is unclear expectations about the role itself; role conflict is incompatible demands within or across roles. The point of naming them separately is that 'stress' commonly gets collapsed into 'workload' when it may actually be one of the other two. - Process collapse
A year-long study's term (cited but not elaborated by Gavett) for generative AI degrading creative workflows β easier concept generation coexisting with unrealistic client expectations and (implied) a loss of process rigor.
Propositions
- explicitLeaders whose teams are overloaded commonly respond by trying to personally absorb the extra work themselves, and this response leads to their own burnout rather than solving the team's problem.conf: high
- explicitLeaders typically keep the criteria behind their own decisions and tradeoffs β what they'd weigh, what they'd prioritize, what they'd let slide and why β tacit and un-externalized, which forces routine decisions to route through the leader.conf: high
- explicitMaking decision criteria explicit ("downloading your thinking") lets a team proactively tackle work without the leader as bottleneck.conf: high
- explicitRelieving team overload requires pushing authority β not just tasks β down to people who themselves manage others or work cross-functionally, including teaching them to frame a hand-off strategically.conf: highextendsHow Fast-Growing Companies Can Make Better Decisions Β· p4 β Applies the general structured-empowerment principle (curated decision authority plus outcome accountability resolves the centralize/decentralize tradeoff) to the specific case of an individual leader relieving team overload, a scale/context the original article doesn't cover.supportsFrontline Workers Know How to Solve Your Organization's Biggest Problems Β· p12 β Both converge on the same mechanism from opposite directions: ceding real decision authority (not just soliciting input or handing off tasks) is what actually produces buy-in and relieves the bottleneck β frontline-listening context here, leader-delegation context there.supports3 Questions to Pressure-Test Your Priorities Β· p4 β Complementary logic: the Replacement Test says a decision is worth a leader's time only if they're uniquely positioned to make it; 'push authority down' is the corollary β if they're not uniquely positioned, the decision right itself should move, not just the task.
- implicitThe actual fix for team overload is redistributing decision-making capacity and authority, not reducing the total volume of work or expanding the leader's own capacity β rearranging load rather than removing it.conf: highsupportsThe Invisible Work Draining Your Best Employees Β· p11 β Both treat current staffing/task volume as roughly fixed and locate the real lever in how load and decision-making are organized and redistributed, not in reducing the underlying amount of work.
- explicitWorkload is a major workplace stressor but not the only, or necessarily the most damaging, one β role ambiguity and role conflict are separate, empirically established stressor categories.conf: high
- explicitA stress problem must first be correctly diagnosed as role overload, role ambiguity, or role conflict, because intervening on the wrong stressor fails to fix the actual problem.conf: high
- explicitThere is a counterintuitive relationship between employee engagement and high workloads, per the underlying research β the newsletter references this finding without stating it.conf: high
- explicitSenior leaders systematically underestimate how often they dominate conversations and micromanage, and these two behaviors reinforce each other to damage collaboration, open dialogue, and trust.conf: high
- explicitCollecting honest, structured feedback (a 360 instrument or anonymous survey) on one's own collaboration behaviors is a necessary precondition for correcting them, since self-perception underestimates the problem.conf: high
- explicitRedesigning a workflow around AI should identify what should change, where humans should retain authority, and how the process should respond when the model is uncertain or wrong β rather than merely automating the old process as-is.conf: high
- explicitUnderstanding how AI is affecting psychological safety may be the single most important thing a leader can do to understand their organization's culture in the AI era.conf: highsupportsManagers Are Not Overhead: They Are Infrastructure Β· p4 β Both identify psychological safety around AI experimentation/adoption as a high-leverage lever for organizational AI outcomes β this document as an assertion, the other with measured lift figures.
- implicitThe article assumes the reader holds formal managerial authority over people whose tasks and decision rights can be redistributed β it leaves unaddressed how someone who leads through expertise and influence without headcount authority would apply 'push authority down.'conf: medium
Arguments
Leaders should stop personally absorbing team overflow work and instead redistribute decision-making capacity to the team.
Explicit premises:
- Absorbing extra work personally leads to leader burnout, not resolution of the team's overload.
- Leaders keep decision criteria tacit, which forces decisions to route through them.
- Externalizing decision criteria and pushing authority (not just tasks) down lets the team act without the leader as bottleneck.
Implicit premises:
- The team's inability to act autonomously β not the raw volume of tasks β is the actual constraint on throughput; this is a decision-rights bottleneck, not a hands bottleneck.
- A leader's tacit judgment can be reliably decomposed into explicit, transferable criteria without losing the nuance that made it good judgment in the first place.
- The team already has the skill and inclination to exercise more responsibility and merely lacks the explicit criteria and permission to do so β this excludes the case where the team also lacks the underlying expertise or capability, not just the authorization.
Inferences:
- A leader's recurring 'I don't have time' complaint is frequently better diagnosed as 'I haven't delegated the judgment, only the task.'
- Leaders should audit their own decision log for how often they are making calls a report could make if given the criteria and explicit license to do so.
Before intervening on a team's 'workload' problem, a leader should first determine whether the actual stressor is role overload, role ambiguity, or role conflict. strength: high
Explicit premises:
- 515 studies spanning 60 years find workload is a major but not the only or most damaging workplace stressor.
- Role ambiguity and role conflict are distinct, separately identifiable stressor categories.
Implicit premises:
- Interventions are stressor-specific: an intervention that reduces raw task volume does not reduce role ambiguity or role conflict, and vice versa β otherwise the diagnostic distinction would be practically pointless.
- Misdiagnosing the stressor wastes intervention effort and may leave the actual problem untouched even after the leader has acted.
Inferences:
- The Wilding-style fixes in the same newsletter (downloading your thinking, pushing authority down) are themselves workload/authority interventions β if a team's real stressor is role ambiguity or role conflict rather than overload, those fixes may not address, and could even worsen, the actual problem (see gap below).
- A leader who reflexively reaches for delegation-based fixes without first diagnosing the stressor type is repeating the same 'absorb-and-guess' pattern the newsletter criticizes in strategy 1, just one level removed.
Narratives
- The suggested 'easy' behavioral substitution for reducing conversation-dominating and micromanaging: making the mute button the default setting on calls.
β Illustrates that behavior change can start with a small, low-effort structural default rather than requiring willpower or a personality overhaul β supports the proposition that honest data plus small substitutions can correct underestimated leader behaviors.
Questions addressed
- β
What should a leader do when their team is overloaded but they personally cannot take on the extra work?
Externalize decision criteria ('downloading your thinking') and push authority, not just tasks, down to the team β per Wilding's five strategies, two of which are detailed. - β Is a team's stress actually caused by workload, or something else?
The newsletter states that workload is not the only or most damaging stressor and that role ambiguity/conflict are alternatives, but does not explain how to tell them apart in practice β that diagnostic method is deferred to the linked underlying research piece. - β
What specific behaviors most damage team collaboration, and how would a leader know if they're guilty of them?
Dominating conversations and micromanaging, identified via honest 360/survey data because self-perception underestimates the frequency, addressed via small behavioral substitutions. - β Do the workload-based fixes (downloading your thinking, pushing authority down) still work if the team's real problem is role ambiguity or role conflict rather than overload?
Not addressed at all β Gavett places the two source pieces back to back without noting the tension.
Gaps
- illogicalThe newsletter juxtaposes 'push authority down, not just tasks' against 'stress often isn't about workload but role ambiguity or role conflict' without noticing the interaction: expanding a report's decision scope (more authority, more ambiguous boundaries about what's now theirs to decide) could itself increase role ambiguity or role conflict β the very stressors the second piece names as sometimes more damaging than workload. The two lead pieces are presented as complementary but may actually be in tension for some teams.
Read next: The full Wilding article and the full Sawhney/McCord research paper, read against each other, to see whether either addresses how expanding decision authority interacts with role clarity. - incomplete'Downloading your thinking' presumes a leader's tacit tradeoff logic can be reliably articulated and transferred as an explicit rule set that a team member can then apply consistently. This is the same assumption the corpus's own extraction of Osmani/structured-empowerment material (extract-structured-empowerment-decisions#g5) already flags as contested in the knowledge-management literature β the newsletter doesn't engage with whether some judgment resists codification, or what happens when it does.
Read next: Knowledge-management literature on the limits of tacit-to-explicit knowledge conversion (e.g., Nonaka's SECI model critiques), or a close reread of structured-empowerment-decisions alongside this piece. - incompleteGavett teases 'a counterintuitive finding about employee engagement and high workloads towards the end' of the Sawhney/McCord piece but never states it. A reader of only this newsletter cannot evaluate, apply, or even remember the actual finding β the sentence functions as an ad for the linked article rather than a self-contained claim.
Read next: The full Sawhney/McCord HBR piece, specifically for the engagement/workload finding. - incompleteNeither the newsletter nor the strategies it highlights address a leader who leads through expertise and design judgment rather than formal headcount authority β the entire framing ('if you manage people who manage people,' 'empower your employees') assumes direct reports and formal decision-right transfer are available levers. A technical-track or informal leader has no equivalent formal authority to 'push down.'
Read next: Corpus material on informal leadership and leading without a title β how influence-based leaders redistribute decision-making capacity without formal authority to delegate. - uninformedNo diagnostic method, checklist, or set of distinguishing questions is given (in this document) for telling role overload apart from role ambiguity or role conflict in practice β the newsletter asserts the categories exist and that correct diagnosis matters, but supplies no way to actually perform that diagnosis.
Read next: The full Sawhney/McCord research piece for their stated diagnostic recommendations.
Related documents
- 3 Questions to Pressure-Test Your Priorities
- How Fast-Growing Companies Can Make Better Decisions
- Frontline Workers Know How to Solve Your Organization's Biggest Problems
- Mob programming: From avant-garde experimentation to established practice
- Software Development As Collective Learning With Hazel Weakly
- Daniel Pinkβs Post
- Scaling the Practice of Architecture, Conversationally
- 9) Nils Brede Moe om AI-paradokset, autonomi, læringskultur og fremtidens team
- Presentation: The Human Scalability Problem: Why Your Teams Don't Scale Like Your Code
- Presentation: Platform Engineering in the Age of AI