Article
The Self-Reliance Curve

Hesitant team: why they wait on you (and how it changes)

Raymond Honings 13 October 2025
A team member thinking carefully about a question, with a manager waiting and giving room.
Summary

I used to feel frustrated watching my team hesitate and wait for my decision, until I realised I was the reason. The pattern loops: the manager feels frustration, makes the call, the team registers that the decision was hers, and waits again next time. Three reasons sound rational. Fear of losing control, the sense that doing it yourself is faster, and doubt that anyone will meet the standard. That doubt rarely gets tested.

Key Insights
  • A hesitant team usually doesn't have a capacity problem. It has learned to wait on the manager.
  • Delegation isn't about handing off work. It's about distributing growth.
  • One question turns delegation from handing out into creating ownership: 'what do you need to succeed?'

I used to feel frustrated when I saw my team hesitate, waiting for my decision.

Until I realized: I was the reason myself.

I was the reason myself

That's an uncomfortable conclusion. Because if the leader is the cause, frustration doesn't help. Frustration reacts to the symptom (hesitation) while perpetuating the symptom (by reacting to it you create more waiting).

The pattern works like this. The manager feels frustration. The manager makes the decision. The team registers: this decision was hers. Next time they wait again, because the system has been confirmed. The frustration grows. The cycle accelerates.

Only when you look at the pattern in yourself instead of in the team do you see the way out. Not because it's your fault. Because only your behavior is in your control.

Three reasons leaders don't delegate

I've seen it hundreds of times, including with experienced leaders. They don't delegate because:

  1. They're afraid of losing control. The assumption is: if I don't decide, something will happen that can't.
  2. They think it's faster if they do it themselves. On the scale of today, maybe. On the scale of a quarter, no.
  3. They doubt whether anyone meets their standard. A reasonable doubt that's rarely tested. Often the team does meet the standard, but the manager has done it herself before they got the chance to show it.

Three reasons that sound rational and rarely get made explicit. The moment they become explicit, the illusion of rationality falls away and room emerges to choose.

The paradox: holding on keeps the team small

But here's the paradox: holding on is precisely what keeps your team small and your calendar full.

The assumption underneath holding on is: I'm protecting quality. The reality is usually: I'm confirming dependency. Because every gap the manager closes is a gap the team doesn't learn to close.

In the short term, holding on seems safer. In the long term, it's actually riskier, because the system builds no resilience. If the manager falls away, work stops. If the manager gets too busy, things sit that no one else has learned to pick up.

Delegation is distributing growth

Delegation isn't about handing off work. It's about distributing growth.

The difference sits in who carries the challenge. With handing off, the challenge has stayed the same, only now it sits with someone else. With distributing growth, the challenge is sized to what the person needs to move forward.

That seems subtle. In practice, it makes the difference between delegation that exhausts and delegation that develops.

The human layers that make delegation work

Traditional models focus on what, who and when. But they miss the human layers that really make delegation work:

  • Personality fit. How you and they prefer to work. Someone sharper in solo execution fits poorly with delegation that asks for continuous collaboration, and vice versa.
  • Communication style. How you and they prefer to communicate. Whoever thinks in writing needs different support than whoever shapes ideas in conversation.
  • Future value. Is it worth learning now for later? Not every task justifies the learning investment. Some do.
  • Meaning. Does the task help them (and the team) grow? A task with meaning gets more attention than a task that's only output.

These four layers determine whether a delegation works or leaks back to the manager. Classical delegation models treat them as bonus. In practice, they're the foundation.

Stretch without overload

Liz Wiseman calls this Multiplier Leadership: creating stretch without overload.

The crux sits in the balance. Too little stretch is comfortable but builds no capacity. Too much stretch is overwhelming and undermines trust. The right amount of stretch sits just outside what someone already can do, with enough support to make it.

Amy Edmondson reminds us that people only take ownership when they feel safe to try, fail and learn.

Safety isn't the opposite of challenge. It's what makes challenge possible. A team that feels unsafe doesn't take on challenges. It minimizes risk. What looks like lack of ambition is usually lack of safety.

The question that changes everything

So the next time you delegate, ask yourself:

"Am I throwing work over the fence, or creating growth?"

A simple approach I use myself:

After explaining the goal or task, ask the person you're delegating to:

"What do you need to succeed?"

It adds a layer of learning, trust and ownership. Every time.

The question works for three reasons. One: it makes explicit that the manager is willing to support, not only expect. Two: it asks the other to think ahead, not only to nod. Three: it opens the door to feedback about the delegation process itself, not only about the result.

One question. Three functions. Enough to turn delegation from handing out into ownership.

A Take-Home Message

A hesitant team usually doesn't have a capacity problem. It has learned to wait on the manager. The cycle doesn't break through frustration but through seeing the pattern.

Delegation is about distributing growth, not handing off work. The four human layers (personality fit, communication style, future value, meaning) determine whether delegation works or leaks back.

One question changes it: 'What do you need to succeed?' Every time.

Frequently Asked Questions

What's the difference between handing off work and distributing growth? +
Handing off work is putting the same work with someone else. Distributing growth is choosing work that fits what someone needs now to move forward. The difference sits in the choice, not in the action. A task that's trivial for you and a meaningful learning step for the team member is good delegation. The same task to someone for whom it's also trivial is work distribution.
How do I know if my team is waiting from hesitation or dependency? +
Hesitation comes from uncertainty about what's right. Dependency comes from habituation to your decision. Test it by explicitly handing one small decision back to someone, asking what they need to make it. If they answer the question sharply and then decide, it was hesitation. If they hand the question back or keep postponing, it's dependency. The intervention differs.
Does 'what do you need to succeed?' always work? +
Not when the question is used to avoid the manager role. The question works when it's sincere. A team member feels the difference between a question that genuinely opens and a question that's only formality. Combine the question with your actual availability to support. Otherwise it becomes a conversation opener without consequence, and the team stops answering.
What if I really am faster than my team? +
On specific tasks, usually yes. On the system as a whole, rarely. A leader who does everything herself builds no resilience. A leader who delegates builds a team that over time becomes faster than herself. The question isn't whether you're faster today. The question is which distribution of work yields most over a quarter. On that scale, 'I'll do it myself' almost always loses.
How do I start delegating if my team has never really had to decide? +
With something small where the stakes are limited. Not to practice, to experience. Explicitly give permission to choose, with an agreement to discuss Friday how it went. The goal isn't only the decision, but the experience that making a decision is allowed and supported. One experience changes little. Four in a row change the system.
Raymond Honings
About the author

Raymond Honings

Raymond is the founder of Seemotion. He works with managers and leadership teams across cultures, helping them build self-reliant teams that perform under pressure. Over the past years he has worked with more than 1,000 managers worldwide. Today most of his work takes place in Asia, mainly in Korea, Taiwan, China and Japan.