Most Delegation Advice Solves the Wrong Problem

We wrote recently about making delegation stick—the neuroscience behind why leaders revert to doing work themselves, and the micro-habit sequencing that bridges the gap between knowing you should delegate and actually doing it under pressure. That piece built on Elsbeth Johnson’s HBR framework, extending her diagnostic tools into sustained behavior change.

The problem most executives face isn’t that they can’t delegate. They’re treating every delegation failure as the same problem—and applying the same fix.

Five failures, not one

When delegation breaks down, the default explanation is “communication.” The task wasn’t clear enough. Expectations weren’t set properly. That diagnosis is comfortable because it’s fixable with a checklist. It’s also wrong about 60% of the time.

Our work with executive teams surfaces five distinct failure types, each requiring a different intervention.

Clarity failure is the checklist problem—work comes back wrong because the leader delegated a task rather than an outcome. “Handle the client meeting” when they meant “get the proposal approved.” This one responds well to context-setting frameworks and handoff protocols.

Capability mismatch is a fit problem. The person tried and couldn’t deliver—wrong skill set, insufficient support, or unrealistic scope. No amount of clearer instructions fixes this. The intervention is reassignment or resource allocation, and it requires honesty that most leaders avoid because it feels like a judgment on the person rather than the pairing.

Commitment gap is an enrollment problem. The work got deprioritized because the person never actually bought in. You assigned; you didn’t enroll. The distinction matters—assignment transfers tasks, enrollment transfers ownership. Self-determination theory (Deci & Ryan, 2000) tells us why: intrinsic motivation depends on three conditions—autonomy in how work gets done, a sense of competence to do it well, and relatedness to the people and purpose involved. Strip any of those out during a handoff and you’ve assigned a task, not enrolled an owner.

Authority vacuum is a structural problem. “I tried, but they wouldn’t listen to me.” The leader delegated responsibility without ensuring the person had the leverage to execute. This is a setup failure, not a performance failure—and it’s the failure type most likely to be misdiagnosed as a commitment gap. The person looks disengaged when they’re actually blocked.

Accountability void is a follow-through problem. No check-ins, no visibility, quiet drift into failure. The leader delegated and disappeared.

The diagnostic discipline is identifying which failure type you’re dealing with before you intervene. Most leaders have a pattern—they repeat the same type across different situations, different teams, different years. Recognizing your pattern is more valuable than memorizing all five types.

Direction changes the playbook

The second diagnostic layer is direction. Most delegation advice assumes you’re delegating downward—to someone who reports to you, or should defer to your authority. That assumption breaks the moment you try to delegate laterally or influence upward.

Research on influence tactics (Yukl & Tracey, 1992) shows that most approaches effective with subordinates lose their impact with peers and superiors. “I need this by Friday” works when you have role authority. Say it to a peer with competing priorities, and you’ve accomplished nothing. Say it to your board chair, and you’ve created a different problem entirely.

Downward delegation requires clear outcomes and the removal of obstacles—your job is to make success possible, not just to assign tasks. Lateral influence requires leading with the other person’s interest and building reciprocity before you need it. Upward influence means framing everything in terms of their priorities, never bringing problems without options, and making it easy to say yes.

Most executives default to downward tactics regardless of direction. The COO who excels at delegating to her direct reports may be functionally ineffective at influencing a peer in finance or managing up to a board that wants more detail than she thinks they need. Same person, different failure—because direction changes the rules entirely.

The distinction underneath

There’s a separation underneath all of this that rarely gets named in delegation literature: the difference between management problems and building problems.

Management problems are about task execution, role clarity, process design, and resource allocation. They respond to systems—checklists, accountability structures, clearer handoffs.

Building problems are about relationships, trust, and political dynamics. The silent stakeholder who misses deadlines isn’t necessarily unclear on expectations—they may not trust you, may feel threatened by the project’s success, or may have priorities you’ve never asked about. No checklist fixes that. The intervention is a conversation, and often a difficult one.

We see this play out in the “political minefield” scenario: visible executive sponsorship but quiet resistance from a powerful middle manager whose cooperation you need. Publicly supportive, privately slow-walking everything. The presenting problem looks like accountability. The actual problem is relational—something about the initiative threatens their position, and no amount of project management rigor addresses that until someone names it.

The discipline is pausing long enough to ask: Am I solving a management problem or a building problem? Argyris and Schön’s theory-in-use framework applies here directly. The leader’s espoused theory—“I’ve clearly delegated and set expectations”—may diverge sharply from what their behavior actually communicates about trust, control, and a willingness to let others lead.

Making this operational

Diagnosis without action is an academic exercise. The protocol we’ve found effective with executive teams takes 60 seconds before any delegation conversation.

First, name the failure type you’re trying to prevent. If you can’t name it specifically—clarity, capability, commitment, authority, or accountability—you haven’t diagnosed the problem yet. Second, identify the direction. Are you delegating down, influencing across, or managing up? Match your approach to the direction, not your default instinct. Third, ask whether this is a management problem or a building problem. If the relationship is the blocker, fix the relationship first. The task conversation can wait.

That 60-second pause becomes a micro-habit over time. It requires almost nothing from the prefrontal cortex once practiced—exactly the kind of low-willpower intervention that holds up when stress impairs executive function and leaders revert to their most automatic patterns (Arnsten, 2009). Gollwitzer’s research on implementation intentions shows that pairing a specific situational cue (”before I delegate anything”) with a specific behavioral response increases follow-through substantially—in several studies, completion rates doubled or tripled compared to motivation alone (Gollwitzer, 1999).

The accountability mechanism matters as much as the diagnosis. Find one peer—not a direct report, not your coach—and schedule a 15-minute check-in ten days out. One question: what did you try and what happened? Social commitment to a specific action, with a specific follow-up date, is what separates insight from behavior change.

Where the conversation goes next

This framework addresses the delegator’s diagnostic skill. Three adjacent conversations are worth having.

The first is identity. Some delegation failures aren’t skill problems—they’re fit problems. Johnson’s example of the M&A lawyer who stepped back from leadership because he preferred doing deals is instructive. He didn’t need a better framework. He needed a different role. When diagnosis reveals a pattern that no technique seems to break, the productive question shifts from “how do I delegate better” to “is this the right seat for me.” That’s a harder conversation, and an honest one.

The second is equity. Authority vacuums don’t distribute evenly. Leaders from underrepresented groups are more likely to be given responsibility without corresponding authority—delegated to without being empowered. The five-type framework diagnoses the individual instance. The organizational response is to examine who gets authority alongside responsibility and who doesn’t, and to redesign the system rather than coach the individual.

The third is the other side of the table. Everything here is from the delegator’s perspective. The experience of receiving delegated work—particularly across power differentials where saying “I don’t have the authority to do this” carries real career risk—shapes whether delegation actually lands. We’ll take that up separately.

Where this leads

Delegation advice fails when it treats delegation as a single skill to improve. It’s a diagnostic practice—identifying what’s actually broken, aligning your approach with the direction, and distinguishing the management problem from the underlying building problem. The leaders who get this right aren’t better at “letting go.” They’re better at reading the situation precisely enough to know what kind of letting go the moment requires.

The 60-second diagnostic is where to start. Run it before your next three delegation conversations this week. Name the failure type, identify the direction, and ask whether you’re solving a management problem or a building problem. Track what you notice. The patterns that emerge will tell you more about your leadership than any assessment instrument.

This work synthesizes research from organizational influence theory (Yukl & Tracey, 1992), self-determination theory (Deci & Ryan, 2000), implementation science (Gollwitzer, 1999), and stress neuroscience (Arnsten, 2009), applied through an implementation lens to executive delegation practice.

Contact us for a complete list of works cited.