You've set clear expectations and learned to deliver feedback that lands. Delegation is where those skills converge into the single strongest signal of trust you can send: handing someone real ownership says "I believe you can carry this" far louder than any words you could offer. But delegation is also where managers fail in two opposite directions, and both quietly tell the person the opposite of what you intended.

Three behaviors look similar from a distance but feel completely different to the person receiving them. Micromanagement is staying too close: you control the how, review every draft, and re-decide calls the person already made, which signals "I don't trust your judgment." Abdication is the opposite failure: you hand off the work and vanish, with no context, no clarity on decision rights, and no backup when things wobble, which signals "you're on your own."

Healthy autonomy sits between them. You're clear on the outcome and the boundaries, you've named which decisions are theirs, and you stay accountable and reachable without hovering. The trap is that both failures feel responsible in the moment: micromanagement feels like diligence, abdication feels like empowerment. The test is simple. Are you controlling the how, or clarifying the what and then getting out of the way while staying available?

The toughest delegation case is your strongest performer who has gone quiet on stretch work, often after a moment that stung. The instinct to "help" by scoping out the hardest piece is the most damaging move you can make. Scoping out the hard part is abdication dressed as kindness: it confirms their fear that they're not trusted with the real thing.

Instead, lead with the offer plainly, say why you chose them with specific evidence rather than flattery, acknowledge their hesitation without making it the headline, and hand over the full scope with concrete backup named out loud.

• Ryan: I want you to own the full client review next month, including presenting both segments live to the exec group. I'm asking you because your segmentation analysis last quarter was the sharpest the team produced.
• Jessica: I appreciate that. Honestly, after how the last exec session went for me, I figured you'd want someone else on the live piece.
• Ryan: I thought about that, and I still want you on the whole thing. Here's the backup: one prep run-through together, I'm in the room as your second, not your lead, and we debrief after. You make the calls.
• Jessica: Okay. If I own it, I own it. Let's do the run-through early.

Notice what Ryan did not do: offer to "just take the keynote part." Keeping the hard part in her hands, with support around it, is what turns the offer into real trust.

Here's the part managers skip: the trust you extend only holds if your own reliability holds. The moment you delegate something visible and then go dark on the support you promised, miss the review you scheduled, or let an unblock you committed to slide, you've handed someone a stretch project and pulled the floor out from under it.

So audit yourself honestly. List your reliability misses from the last quarter: the late Slack replies, the "I'll get back to you" moments that never closed, the follow-ups that evaporated. Group them, name the one dominant pattern, and install a single concrete system change this week rather than resolving to "be more on top of things." Specificity beats virtue every time.

The throughline of this unit is one idea: delegation only signals trust when you give real ownership and prove reliable enough to back it. Three things sit ahead. First, a quick self-check sorting manager behaviors into micromanagement, autonomy, and abdication. Then a live conversation where you offer a high-visibility project to a hesitant top performer and resist the pull to scope out the hard part. Finally, an honest audit of your own reliability so the trust you extend actually holds. Start by watching, in your next delegation, whether you're controlling the how or clarifying the what.