The delegation move most people skip

You need to delegate more. Every manager hears it. The standard playbook hands you Michael Hyatt’s 5 levels of delegation and tells you to pick a level for each task.

The 5 levels are genuinely useful — most managers I work with find them clarifying once they see them laid out. But the framework doesn’t tell you two things that determine whether it actually lands: what’s going on for you in your role in your org (a front-line manager at Company A and a VP at Company B might share overlapping struggles — it’s less about your title than about what your version of the work actually looks like), and what purpose you’re delegating for (freeing your attention vs. growing someone else).

Pick those two first; the right level falls out of them. And if you don’t know the levels, read on.

One of the common places where people struggle to delegate is that shift from individual contributor to front-line manager, but in reality, I see the delegation struggle play out in all sorts of levels in the organization. You might recognize this if you’re a Director learning that certain leadership tasks should and could be delegated through developing your team. The VP who holds onto all the weight of responsibility of the area (which is not inherently a bad thing) when in reality some of that translates into quick fixes and noise that could be distributed throughout their vertical. Or, a senior executive who is caught playing in their lane instead of delegating across the organization.

Across all of these, the same question keeps surfacing. What are you delegating for?

• At the front-line level and those newer to managing, it becomes about how you shift your thinking from needing to produce to helping others grow.
• Directors face a new challenge, managing managers, and with that comes the skill of delegating people management.
• In 2026 people are overworked. The number of VPs that I’ve worked with who’ve mentioned guilt of delegating is real.

When delegating, consider: is this to offload or to develop? And can it be both? Sometimes it’s about freeing your own attention. Other times it’s something you could hand off precisely for someone’s development. Not because you need your time freed up or because you don’t want to do it, but because it could upskill someone on your team. And to take it a step further, could delegation be a way to enable your team members to live in a “strengths” zone, empowering people to work in their strengths (which, by the way, tends to increase engagement)?

That tension, keep it or hand it off, often shows up as guilt. And guilt tends to come in two shapes when delegation comes into play. The first is the guilt of offloading: “I’m putting this on someone else, I should still own this, what does it say about me if I hand this off.” The second is the guilt of not developing: “I’m holding onto this thing that could stretch someone on my team, they could do this if I let them, but I’m keeping it because it’s mine to do.”

Both are real, and both are worth paying attention to. The first usually points at something about how you’re holding your role: are you measuring your value by what’s still on your plate, or by what’s getting done across the team? The second points at something about who’s around you and what they’re ready for, and how often you’re really checking. Or maybe it’s a signal that you and your team need to engage in some real prioritization conversations.

I find guilt is rarely just guilt — it’s usually a tell, and often one you can set down (Dina Denham Smith, HBR).

The other thing to consider is not just the why of delegating but the what. Clients who have worked with me will likely encounter the Eisenhower Matrix at some point. An oldie but a goodie: a 2-by-2 grid of urgent against important:

	Urgent	Not Urgent
Important	Do — handle it now. Crises, real deadlines, the things that genuinely can’t wait.	Schedule — plan it, prevent it, build for it. Strategy, relationships, development.
Not Important	Delegate — push it down or out. Interruptions, some meetings, requests for information.	Delete — let it go. Busywork, distractions, low-stakes asks dressed up as obligations.

Originally developed as a task management tool (yes, by the former US President), I find myself inviting people to use it as a mental framework more than a task management tool in and of itself. For example, can you shift your mind to really zone in on what is urgent and important as opposed to spending all of your time on what is urgent but could realistically wait?

For leaders in particular, this can be a helpful starting place to consider what things to delegate. The urgent but slightly less important things. I also find myself working with leaders to explore what informs their definition of urgency vs importance. Is it a true business critical level of impact when it comes to sense of urgency? Or is it because it’s a shiny object. And is it truly important because it’s high risk or high stakeholder impact? Or important because you care about it.

All of these thoughts across my client work keep bringing me back to another classic: the five levels of delegation by Michael Hyatt in Free to Focus.

Level	Name	What it sounds like
1	Do as I say	”This is the task, this is how to do it — do it the way I tell you.”
2	Research and report	”Do some digging around this, let me know what you find, and I’ll tell you how to do it.”
3	Research and recommend	”Do some digging, come up with a plan, and I’ll give the final OK.”
4	Decide and inform	”Do what you need to do to make this happen and keep me posted on what happens.”
5	Act independently	”Take this over, you got this.”

These levels were originally presented as levels of complexity and scaling up. The idea: each progressive tier is a little more autonomy in the decision-making process.

This, of course, looks a bit different depending on where you sit in the organization. A front-line manager handing a junior IC a “dig into this and let me know what you find” is quite different from a VP asking a Director to scope a strategy and report back. The altitude + purpose question from the start of this piece is what tells you which Level 2 you’re actually setting up.

There are other frameworks in this neighborhood: RACI for mapping responsibility across people on the same piece of work, or Stephen Covey’s “stewardship vs. gofer” framing in The 7 Habits of Highly Effective People for the philosophical posture behind it. For the individual manager’s question — how do I actually hand this off? — the five levels are still the sharpest tool I’ve found.

One note before going further: this is human-to-human delegation. The recent advent of AI changes things a bit — telling AI to research and report back feels very different from telling AI to execute as you say. That’s worth a separate piece, and one is coming.

I created this reflection worksheet to get you thinking about how you might start to think about your delegation a bit more. It starts with having you think about the delegation issues you might be running into based on what’s going on (and I use levels to frame it but honestly our titles all mean different things these days so pick the one that makes sense for you) and where you think you need to stretch your delegating muscle a bit more, for offloading, development, or both. Based on that, how to break down your thinking a bit more on the different levels of delegation. Work through it on your computer, take a screenshot, or print it out and pin it up.

Delegation is tricky and imprecise. Do what you need to do, but the invitation here is to be more intentional and shift your thinking around not just what you’re doing but how and why you’re doing it.