Guiding. Coaching. Delegating. Most managers use these words interchangeably, as if they’re all just different flavors of the same thing: telling people what to do.
They’re not. They’re three distinct modes of managing, and each one is appropriate in different situations. Defaulting to the wrong one, especially defaulting to always guiding or always telling, doesn’t just miss the moment. It actively gets in the way of your team’s growth.
Understanding the difference, and knowing when to use each, is one of the most practical skills a manager can develop. Let’s break them down.
Delegating: get out of the way
Delegation is the simplest of the three, and the most misunderstood. Managers often think delegation means giving someone a task and then checking in constantly to make sure it’s done right. That’s not delegation. That’s micromanagement with extra steps.
Real delegation means identifying someone who has the competence to handle something, handing it off, and trusting them to execute. There’s no teaching happening here. There’s no coaching conversation. You’ve got a lot on your plate, a last-minute request just came in, and you need it handled. You pick the right person, you give them clear context, and you let them work.
The key assumption in delegation is competence. You’re not delegating to develop someone; you’re delegating because they’re already equipped. If they’re not, you’re not delegating, you’re setting them up to fail.
“Delegation isn’t about getting something off your plate. It’s about trusting that the right person can carry it.”
Guiding: working through it together
Guiding is more collaborative. It’s the mode you use when someone needs support navigating a challenge, not because they lack competence entirely, but because the path forward isn’t clear and they’d benefit from having you in the room working through it with them.
Guiding often sounds like: “Let me show you how I’d approach this” or “Here’s what I’d be thinking about in this situation.” You’re sharing knowledge, perspective, and experience. You’re helping them see around corners they haven’t encountered yet.
The risk with guiding is that it can become a crutch, for both of you. If you’re always guiding, your team member never has to figure anything out for themselves. And you never get to find out what they’re actually capable of.
Guiding has its place. But it shouldn’t be your default mode for every situation.
Coaching: building the confidence to think for themselves
Coaching is the hardest of the three, and the most rewarding. The core principle is simple: you do not give the answer.
This goes against every instinct most experienced managers have. You’ve seen the problem before. You know the solution. It would take thirty seconds to just tell them. But the moment you do that, you’ve stolen the learning. You’ve trained them to come back to you every time instead of developing the judgment to figure it out.
“The goal of coaching isn’t to get them to think like you. It’s to get them to think for themselves.”
I’ve seen this play out over and over in my career. When an engineer on my team is ready to step up (ready to move from mid-level to senior, ready to take on more scope), I start looking for opportunities to give them real ownership. Not invented ownership, real ownership.
We were once building a donation forms application. Instead of assigning the receipting portion of the system to a senior engineer, I gave it to someone who was ready to grow into that level of responsibility. But I didn’t just hand it off and disappear. I gave them the full scope: design the system architecture, meet with the stakeholders, figure out the dependencies, make the calls that need to be made. Bring this piece to life.
Then I coached them through it.
Not by telling them what to do at each step. By asking questions. What are you thinking? Where are you stuck? What options do you see? What happens if you go that route? The goal wasn’t to get them to arrive at the answer I already had in my head. The goal was to build their confidence to arrive at their own answer, and trust it.
The question that keeps the ball moving
The moment most managers dread, and most team members dread, is the roadblock. Someone hits a wall. They don’t know what to do next. They feel insecure about asking for help. So they wait. The work stalls. And what started as an exciting growth opportunity starts to feel like a failure.
This is where coaching earns its keep. When someone comes to me stuck, I don’t solve it for them. I give them a question to carry with them:
“How do I keep the ball rolling forward?”
That’s it. It sounds simple. But it reframes the whole problem. Instead of “I’m blocked and I need someone to unblock me,” it becomes “What is one thing I can do right now to keep this moving?” Maybe it’s a conversation with a stakeholder. Maybe it’s a smaller experiment to test an assumption. Maybe it’s flagging a dependency earlier than planned.
The question shifts the mindset from waiting to acting. And over time, that shift, that habit of always looking for the next forward move, is what turns a developing engineer into a senior one.
A growth mindset isn’t just about being open to learning. It’s about having the agency to keep moving through uncertainty. Coaching is how you build that.
Knowing which mode to use
So how do you know which mode a situation calls for? Here’s a simple way to think about it:
- Use delegation when the person has the competence and the task just needs to get done. Don’t overthink it.
- Use guiding when someone needs support navigating unfamiliar territory and would benefit from your direct experience and perspective.
- Use coaching when the goal is development: when you want them to build the capability to handle this kind of situation on their own next time.
The mistake most managers make isn’t choosing the wrong mode. It’s never asking the question at all. They walk into every situation in the same mode, usually guiding or telling, regardless of what the moment actually needs.
Start noticing which mode you’re defaulting to. Then ask yourself: is this what this person actually needs right now? Or am I just doing what’s comfortable for me?
Key takeaways
- Delegating, guiding, and coaching are three distinct tools. Using them interchangeably limits your team’s growth.
- Delegate when the person is already equipped. Your job is to hand off clearly and trust the execution.
- Guide when someone needs your experience and perspective to navigate unfamiliar ground.
- Coach when the goal is development. That means asking questions, not giving answers, even when you know the answer.
- The goal of coaching is to build confidence and independent thinking, not to get them to think like you.
- Give your team the question that keeps them moving: “How do I keep the ball rolling forward?”
- Notice which mode you default to, and ask yourself if it’s actually what the moment calls for.