Management Matters | Notes from an HE Coach podcast

Episode 34 - Delegation 101

0:00
19:02
Rewind 15 seconds
Fast Forward 15 seconds

What does good delegation actually involve, and why does it sometimes go wrong?

Delegation is one of those fundamental management skills that most of us have learned through experience.

We've been delegated to, we've watched how other managers do it, and we've gradually developed our own approach.

But how often have we stopped to think about the mechanisms of good delegation?

What information do people need from us? How much oversight is appropriate? And how do we make sure we're supporting someone without micromanaging them?

In this episode of Management Matters, I'm getting into the practicalities of delegation, including how to adapt your approach for different people and different types of work.

This is particularly relevant if you're managing other managers and want to help them understand why delegation sometimes goes wrong.

Two different types of delegation

I think it's useful to distinguish between two broad types of delegation.

The first is implicit, remit-based delegation.

This is where someone has responsibility for a whole area of work as part of their role.

For example, a Head of Marketing might be responsible for ensuring that the university's marketing activity is delivered effectively.

This type of delegation relies heavily on trust, experience and a shared understanding of expectations.

You're confident that the person knows what they're doing, understands the boundaries of their authority and will escalate issues appropriately.

The second is explicit, task-based or project-specific delegation.

This is where you're handing over a particular piece of work and need to be much clearer about what you're asking someone to do.

It's particularly useful when someone is new to a role, learning a new skill or taking on something that stretches their existing capabilities.

The difficulty comes when we try to delegate everything in the same way.

Closer management doesn't automatically mean micromanagement

One reason managers sometimes struggle with delegation is that they don't want to be seen as micromanaging.

So they give someone a task, step back and hope everything works out.

But sometimes people genuinely need more guidance.

If you're delegating something new or unfamiliar, it's perfectly reasonable to provide more structure and oversight.

The important thing is to explain why.

You might tell someone that you're going to manage this particular task more closely because it's a development opportunity, or because they're still learning the standards and processes involved.

That makes it clear that the additional support is intentional and temporary, rather than a reflection of your lack of confidence in them.

Responsibility, authority and accountability

When we delegate, there are several things we need to think about.

We're giving someone responsibility for completing a task.

We're also giving them a level of authority to make decisions about how that task is carried out.

But that authority needs boundaries.

What can they decide for themselves?

What needs to follow institutional processes, policies or standards?

When should they check something with you?

And because you remain accountable for the overall outcome, what information do you need them to report back?

That might include progress updates, emerging risks, questions, delays or lessons learned.

Good delegation means being clear about these expectations from the beginning, rather than discovering halfway through that you and the other person had very different ideas about what was supposed to happen.

What to include when you delegate a task

I think there are some really useful questions to work through when you're handing over a piece of work.

What exactly needs to be done?

What does a good outcome look like?

What standards need to be met?

What's the deadline, and why does it matter?

What decisions can the person make independently?

What examples, templates or existing procedures would help them?

When do you want them to check in with you, and what should they escalate?

Sometimes you won't know all the answers yourself.

In that situation, you might ask someone to spend a couple of hours researching the options before coming back to discuss their findings.

Or you might ask them to produce a one-page outline before investing time in a full presentation.

The point is to create opportunities to check understanding and direction before too much work has been done.

What delegation can learn from AI prompting

There's an interesting connection here with something I've been teaching in my AI training.

When you're using tools like ChatGPT, Copilot or Claude, the quality of your instructions makes a huge difference to the quality of the result.

And I think the same applies when we're delegating to people.

In the episode, I share a five-part framework that works for both:

  1. Explain who you are and the wider context.

  2. Describe the task.

  3. Set out the constraints and what the outcome needs to look like.

  4. Provide examples of relevant work.

  5. Invite questions to clarify anything that's unclear.

If we're prepared to give an AI tool that level of information, why wouldn't we do the same for someone in our team?

Different people need different approaches

One of the bigger lessons here is that good management doesn't mean treating everyone identically.

You might take a hands-off approach with an experienced colleague who knows the work well and has earned your trust.

Someone who's new, developing their skills or working on something unfamiliar might need more guidance, training or regular check-ins.

Both approaches can be appropriate.

The key is to be consistent in your principles while adapting your management to the person and the situation.

That's what I mean by adaptive management.

And it's something we'll return to in future episodes.

What happens after the work is delivered?

This episode focuses on setting up delegation well.

In a future episode, I'll come back to what happens when someone brings the completed work back to you.

How do you review it? What happens if it isn't quite right? And how do you use that moment to support someone's development?

In the meantime, if you've got questions about delegation or other management practices you'd like me to explore in this series, I'd love to hear from you.

You can email me at [email protected].

More episodes from "Management Matters | Notes from an HE Coach"