Delegation in the Age of AI: Developing People While Orchestrating Machines
This is the eighth article in a series on the human capabilities that AI cannot replicate.
The average manager uses only 66% of the intelligence and capability their people bring to work.
That number comes from Liz Wiseman, whose research across more than 150 leaders found a striking divide between Multipliers — leaders who amplify the people around them — and Diminishers, who suppress them. The divide is about delegation: how much authority leaders hand over, to whom and whether what they hand over lands as opportunity or as overwhelm.
Most leaders believe they delegate well. Ask their teams, and you get a different answer.
Gallup’s research shows that 70% of the variance in team engagement — the single most influential factor in whether people bring their best to work or quietly check out — stems directly from the quality of the manager. When leaders hold too tight, they become a bottleneck. Their people stop making decisions, stop taking initiative, stop exercising the judgment that the organization is paying them to bring. When leaders let go too fast, without context, coaching or clarity about the desired outcome, they set people up to fail at tasks they were never prepared for — and then blame them for the result.
Both are delegation failures. And in many organizations, the same leader is committing both at once.
The Leader Who Was Two Problems in One
I worked with a leader — I'll call him Frank — whose team had stopped moving without him.
The symptom that surfaced first looked like a lack of initiative. Frank's people, by every external measure, were capable. Experienced, credentialed, well-compensated. And still, nothing happened without Frank in the loop. Decisions waited. Projects stalled. Leaders at every level were constantly checking in, asking for direction on things they should have been able to resolve themselves.
When I looked deeper, two very different patterns emerged.
On the work Frank understood — the territory he had built his career on, the domains where he felt competent and confident — he held on. He reviewed everything. Approved every decision. When he did assign tasks, he hovered. He checked back daily. Asked for updates before they were due. He wasn’t delegating; he was asking his people to execute while he directed every step.
On the work Frank didn’t know or didn’t want to do — the projects outside his expertise, the tasks he found tedious or low-status — his style reversed completely. He assigned them with a phrase his team had learned to dread: “Figure it out.” No context. No defined outcome. No scaffolding for how to approach it. And then, predictably, he was disappointed with the results.
On one side, a micromanager. On the other, a leader who over-delegated to people who hadn’t been developed to handle the task. The organizational result of both, combined, was a culture of compliance — a team that had learned, through years of mixed signals, that there was no safe place to operate independently. They checked in because the cost of not checking in was too high. Taking initiative had never been reliably rewarded.
Frank’s deepest frustration? He complained constantly about the fact that his people couldn’t work without him.
He was, without knowing it, the reason.
The Delegation Staircase
The model we use with leaders like Frank is what I call the Delegation Staircase — a 10-step progression that maps the relationship between authority and trust on any given task.
At Step 1, the leader instructs precisely: Do as I say. There is no investigation, no analysis, no decision-making. It is execution by directive. Step 1 is appropriate for onboarding, for high-stakes tasks requiring exact precision or for situations where someone is genuinely new to a domain. The mistake is treating it as a permanent address.
At the top of the staircase — Steps 9 and 10 — the dynamic is reversed: Decide. Take action. It’s your responsibility now. The leader is not in the loop unless the person chooses to bring them in. That level of autonomy is earned, not given. It is the product of a relationship, built stair step by stair step, in which the person has demonstrated judgment and the leader has developed the trust to honor it.
The middle of the staircase — Steps 4 through 7 — is where most development happens. Here, investigation and analysis are shared. Decisions are co-constructed. Autonomy expands gradually, one step at a time, as capability and trust accumulate. You investigate. We analyze. We decide becomes You analyze. You decide. Share your decision and wait for my green light. And eventually: Decide and proceed unless you hear otherwise.
The staircase is a map of where a specific person is, on a specific task, at a specific moment. The same person may be at Step 8 on work they have owned for three years and at Step 3 on something they have just taken on. The step on the staircase an employee is on changes with the relationship and the task.
Frank’s error was that he skipped the staircase entirely — lurching between Step 1 on the work he controlled and Step 10 on the work he didn’t, with no development in between.
Three Practices That Build the Staircase
1. Reading the step before assigning the task
Before you hand over a task, ask your direct report where they think they are in terms of both skill and confidence on the staircase for this task, right now. Not where they want to be. Not where they were on the last project.
Hersey and Blanchard identified this principle in their Situational Leadership research more than 50 years ago: Leadership effectiveness is not about finding one style and applying it consistently. It is about reading the person in front of you and matching your approach to where they actually are. Their framework maps four leadership styles — directing, coaching, supporting, and delegating — to four stages of follower readiness. The Delegation Staircase extends this logic into 10 gradations, because development rarely moves in quarters. It moves in steps.
The most important shift I see in leaders who improve their delegation is not the decision they make about what to hand over. It is the conversation they have first.
2. Climbing one step at a time
Once you know where someone is, your job is to help them take one step up — not two, not five, not 10.
Frank’s failure was a failure of understanding that radical change is temporary (and most often leads to failure), but incremental change is permanent. He expected people to be ready for the top of the staircase without ever investing in the climb. The result was precisely what Wiseman’s research identifies as the signature of Diminishers: people assigned responsibility without capability, set up to fail by a leader who confused assignment with development.
Climbing one step at a time means giving people tasks that stretch them slightly beyond where they are, with enough clarity about the outcome and enough access to guidance that success is achievable and visible. It means starting with you investigate, I decide and moving, deliberately, toward you decide, let me know. It means having an honest conversation about the staircase itself, as a tool for growth.
In our Culture Catalyst program, one of the most productive exercises leaders do is showing this model to their direct reports and asking where they think they are on the staircase for each of their key responsibilities. The gap between where a leader assumes someone is and where that person believes they are (the Delegation Gap) is always illuminating and always worth discussing.
3. Assigning AI to the bottom of the staircase
The arrival of AI has made choices about delegation more consequential.
AI is a capable, tireless resident of the lower steps. It investigates well (based on correct prompts). It analyzes reliably. It executes precisely when given clear instruction. Steps 1 through 4 on the Delegation Staircase describe work that AI handles effectively — and handles faster, at scale and at lower cost than any human team.
The risk is delegating to AI at the bottom of the staircase while continuing to micromanage humans at the same level. You’re gaining the efficiency of automation, but depriving your people of the development that comes from doing lower-stakes work before they’re handed higher-stakes responsibility.
The strategic move is the opposite: Push AI down to Steps 1 through 4, and push your people up to Steps 7 through 10. Use the capacity AI creates to expand development opportunities. The leader’s job shifts from directing work at the bottom to developing people at the top. That is a different kind of delegation. And it requires a different kind of leader.
Why Delegation Is a Human Capability AI Cannot Replicate
AI can investigate, analyze and produce at the lower steps of the staircase without complaint, without ego, and without needing to be developed.
But you cannot hand AI a task at Step 3 this year and expect to hand it a task at Step 8 next year because you invested in the relationship. You cannot watch AI navigate a setback, learn from it and carry that learning forward with more judgment than it had before.
Delegation to humans is not a transfer of work. It is a transfer of capability — incrementally, gradually, deliberately, across hundreds of small interactions. People grow when given the right stretch at the right time, by a leader who is paying enough attention to know which step they’re ready for.
In my next article, I'll explore innovation — how leaders reframe problems rather than just solve them, and why the human capacity for creative insight matters more than ever in an age that generates answers faster than we can form good questions.
This article is part of a series on the human capabilities that AI cannot replicate. Previous installments have covered connection, trust, accountability, curiosity, discernment and integration.
If delegation is showing up as a bottleneck or a development gap in your organization, I’d like to help you think it through. Book a 30-minute Insight Call with me and let’s talk about what’s actually happening and what to do about it.
