Explore Delayed Delegation With a Capable Team

A leader tells you the team is capable, then describes rewriting a report an hour before it goes out or reviewing every hire before an offer is made. The words and the behavior do not match, and most coaches jump straight to a simple instruction, delegate more. That instruction rarely works. The leader already believes in delegation. What holds them back is something more specific, a missing decision rule, a bad experience with rework, a habit built in an earlier role, or a team that has quietly learned to wait for approval. Your job as the coach is to find which one it is before you suggest anything.

Why This Conversation Goes Wrong

Coaches often treat a capable team paired with constant oversight as a confidence problem. The fix they reach for is encouragement, trust your team more, let go a little. This fails for a plain reason. The leader is not confused about the value of delegation. They already know the theory. Telling them again does not change what happens the next time a decision lands on their desk.

There is a second failure mode. Framing the pattern as a trust issue puts the leader on the defensive. Nobody wants to hear that they do not trust capable people, especially when they chose and praised those people. Once a leader feels judged, they give you the polished answer instead of the real one, and the conversation stalls on generalities like I need to work on letting go. That sentence sounds like progress and produces no change.

How to Prepare Before You Sit Down

Ask the leader in advance to bring one specific decision that returned to their desk recently. Not a general pattern, one real instance with a name and a date attached. A single case turns delegation into an operating question you can actually examine, instead of a character trait you can only discuss in the abstract.

Before the session, decide what you need to learn from that one case. You need to know who prepared the decision, what authority that person believed they had, what the leader changed after the work came to them, and what happened as a result of the change. You also want to separate two different problems that look identical from the outside. Sometimes the team lacks real decision rights. Other times they have the rights but no clear threshold for using them, so they default to asking. The conversation you run depends on which one you find, so resist any urge to diagnose before the leader gives you the specifics.

What to Say

You ask, "Tell me about a decision that came back to you last week." The leader says, "My operations director put together the vendor renewal, and I still rewrote two of the terms before we signed."

You ask, "What had you told her about that decision." The leader pauses, then answers, "I told her to bring me anything involving a vendor." You ask, "Was this a new vendor, or a renewal on an existing one." The leader stops and reconsiders. "It was a renewal, under a budget we already approved. I could have let her handle any renewal inside that budget and only bring me new vendors or terms that fall outside the current agreement."

You ask, "What does she need from you to use that boundary with confidence." The leader lays out three things on the spot, the budget ceiling, the two situations that still require escalation, and a date to review how the new boundary is working in practice.

Notice what the exchange does not do. It does not tell the leader they have a control problem. It surfaces one missing sentence, a decision rule that was never written down, and the leader repairs it in real time. The director also gets something valuable out of this, a clear invitation to act on her own judgment and a named path for raising a genuine exception, instead of guessing what will trigger a rewrite.

Mistakes to Avoid

A few habits derail this conversation even when your questions are good.

1. Accepting a vague first answer, such as I just like to check things, and moving on. Push past it to the specific decision and the specific rule that existed or did not exist.
2. Letting the leader close the conversation with a promise to delegate more, with no rule attached. A promise without a rule reverts within a week, because nothing in the leader's daily routine actually changed.
3. Treating every case as a trust problem. Sometimes the real issue is that the leader never defined a threshold, and the fix is a written boundary, not a mindset shift.
4. Forgetting the other person in the story. The director in the example also needs to hear about the new boundary directly from her leader, or she keeps bringing everything forward out of habit built over months.

How to Practice and Score It

This conversation is easy to describe and hard to run well live, because the leader's answers come slowly and the useful question depends on what they just said. Rehearsal helps more than reading about it. DealSpeak lets you run this scenario against an AI counterpart playing a leader who insists the team is strong while describing a decision they quietly overrode, so you can practice the questioning sequence before you use it with a real client.

Score your attempt on four things. Did you get the leader to name one specific decision instead of a general pattern. Did you extract the exact authority the team member believed they had, in the leader's own words. Did the session end with a concrete rule, not a restated intention. Did you address what the team member needs to hear, not only what the leader needs to change. Weak sessions usually fail on the third point, ending on insight without a rule anyone can act on.

Once you are comfortable running this pattern, you can browse other HR and Leadership practice conversations that build the same muscle in adjacent situations, from performance conversations to hiring decisions.

Where This Leads Next

The delegation note the leader writes after this session, naming the result sought, the authority granted, the exceptions that require escalation, and a review date, only works if it gets used the next time a similar decision comes up. The post on how to Set Working Expectations for a Newly Delegated Responsibility covers how to hand that note to the team member so the boundary sticks on their end too. And because a rule without a date tends to drift, the piece on how to Close a Development Conversation With an Observable Commitment shows how to end this kind of session with something you can actually check on later, rather than a vague intention to do better.

The gap between a leader's stated trust in their team and their actual behavior is rarely about trust at all. Find the one decision, name the missing rule, and give both people a boundary they can use. That is a fixable operating problem, not a character flaw, and it responds to specific questions far faster than it responds to encouragement.