The intelligence officers in Iraq had a specific problem.
Special forces teams would raid a location, grab laptops and documents, stuff them in bags, and send them sixty miles back to the analysts. By the time the bags arrived, the sticky notes identifying what came from where had usually fallen off.
The operators thought their job was done. The analysts couldn’t do anything with what they’d been handed.
Both sides were working hard. Neither side was actually connected to the other’s job.
The general running that task force called this the difference between being a chess master and being a gardener.
A chess master believes that moving the right piece produces a predictable result — reposition someone, and the outcome follows automatically.
A gardener knows a living thing doesn’t work that way. You don’t move a plant into sunlight and get instant growth. You tend it, you give it what it actually needs, and growth happens on its own timeline, not yours.
I’ve watched a quieter version of that gap play out in my own career, minus the raids.
Early in a new role, I consistently brought insights and concerns to operational sync-up calls. The response, every time, was a nod.
Acknowledged. Noted. Nothing after that.
Nobody told me it wasn’t my job to act on what I was raising. I think leadership genuinely believed they were empowering me — hands off, figure it out, learn by doing.
What I actually needed wasn’t permission to act. I already had that.
What I needed was what makes permission usable: the big picture, the reasoning behind it, and what connected to the larger goal we were supposedly all committed to. Which risks were worth taking, and which weren’t.
Not the how — that part was mine to work out. Just the what and the why, clearly enough that my own judgment had something real to stand on.
A nod isn’t guidance. It’s the appearance of connection without the substance of it — the exact gap that let the raid intelligence rot in an unopened supply closet, just wearing a friendlier face.
Teach someone how to fish, and eventually they can feed themselves. More importantly, they can teach someone else.
That’s the only way a leadership pipeline actually gets built — not through nods, and not through hands-off empowerment mistaken for trust, but through someone willing to hand over the why clearly enough that the how becomes genuinely learnable, not just genuinely risky.