The Trust You Extend Isn't the Trust That Holds

The Precise Leader Series: Leadership & Organizational Precision

Why leaders who delegate badly retreat into control, and what a four-star general figured out about the difference.

Every leader I work with says they want to delegate.

Almost none of them mean what they think they mean by it.

I've spent years working privately with leaders across entire organizations, hundreds of one-on-one sessions, from CEOs down through directors and team leads, sustained week after week.

That vantage point shows me something most leaders can't see from inside their own org: the gap between the version of delegation they believe they're practicing and the version their people are actually experiencing.

And the most expensive failures I see don't come from leaders who refuse to let go.

They come from leaders who let go of the wrong half.

The Half That Gets Dropped

Real delegation has two parts.

The first is trust, handing someone the authority to make a call.

That part is easy to talk about and easy to feel good about.

The second is visibility, building the conditions that let you see how the work is actually going while it's happening, not after it's finished.

That part is quiet, unglamorous, and almost always the one that gets skipped.

Here's what skipping it looks like in practice.

I watched a leader hand a project to one of their people and step back, genuinely step back, no hovering, the kind of hands-off trust every management book tells you to extend.

No check-ins on the actual work.

No validation that what was being built matched what was needed.

What came back was an elaborate, expensive system that only the person who built it could run or maintain.

A requirement that a beginner could have satisfied with something simple had turned into a permanent dependency on one individual.

The trust had been real.

The visibility had been absent.

And absent visibility, the trust had nothing underneath it.

The Retreat Is The Real Damage

Here's the part that stayed with me, because it's the part that compounds.

The leader didn't walk away distrusting that one person.

They walked away distrusting delegation itself.

One bad experience with unvalidated trust, and the reflex hardened into something worse: hold everything, approve everything, be the bottleneck on everything.

The single failure didn't recalibrate their read on one report.

It recalibrated their posture toward the whole team, and everyone downstream inherited a tighter leash they'd done nothing to deserve.

That's the mechanism I see most often, and it's the one nobody names.

We talk endlessly about leaders who won't let go.

We rarely talk about the leaders who let go once, badly, got burned, and spent the next three years proving to themselves that letting go doesn't work.

Their over-control isn't a personality flaw.

It's a scar.

What The General Understood That Most Leaders Miss

In 2004, General Stanley McChrystal was commanding the best-resourced special operations force on earth and losing to an enemy with worse weapons, less money, and no formal training.

His fix has become famous, and it's almost always remembered wrong.

People remember it as "push authority down." That's half of it, the same half leaders love to quote.

But the move that actually made it work was the other half: what he called shared consciousness.

He built a daily briefing, open to thousands of people across the organization, where everyone could see the whole picture, not a summary, the picture.

He pushed decisions to the edge and simultaneously made the work radically visible to everyone, himself included.

The transparency is what made the delegation survive contact with reality.

He didn't just trust his operators and hope.

He built the visibility that let their judgment be trusted safely.

Strip that visibility out and you don't get a lighter, faster version of what he did, you get the opposite, dressed in the same language.

Abdication Wearing Empowerment's Clothes

That's the phrase I keep coming back to.

Delegation without visibility isn't empowerment.

It's abdication wearing empowerment's clothes, and the costume is exactly what makes it dangerous.

From the outside, and from inside the leader's own head, "I trusted them and got out of the way" is indistinguishable from "I stopped paying attention." The two look identical on day one.

They only diverge later, when the work comes back, and one version has a leader who saw it coming, and the other has a leader who's blindsided and now believes trust is the thing that betrayed them.

The leader I watched did the first half without the second.

Extended the trust, skipped the visibility.

And when it broke, they didn't fix the visibility, they withdrew the trust.

Which is precisely the trap McChrystal spent years climbing out of: the belief that control hoarded at the top is safer than judgment distributed to the edge.

In a slow environment you can almost get away with that belief.

In a fast one, the control you hoard is the control you lose.

What Visible Trust Actually Looks Like

The fix isn't to trust less.

Leaders who respond to a bad delegation by tightening their grip are solving the wrong problem, they're removing the trust when they should be adding the visibility.

Visible trust means the authority still goes to the person closest to the work, but the work itself stays legible while it's in motion: lightweight checkpoints that surface direction without seizing the wheel, a shared view of what "done" and "on track" mean before the work starts, and enough transparency that a wrong turn shows up as a course correction instead of a post-mortem.

Done right, it doesn't feel like surveillance and it doesn't feel like abdication.

It feels like the thing McChrystal built: people making real decisions at the edge, in the open, where a mistake is cheap to catch and a good call is visible to everyone who needs to learn from it.

So here's the question I'd leave you with, and it's the one I ask the leaders I work with.

The last time you delegated something that mattered, were you extending trust, or were you building the visibility that lets trust hold?

Because if it was only the first one, you didn't delegate.

You just found a new way to end up as the bottleneck.