The inventory reconciliation was coming apart, and I could see it from my desk without looking at a single number.
I could see it from the email rhythm.
The pace was tightening. Two hours between messages, then ninety minutes, then one hour. The tone was sharpening — compressed, getting smaller. A supervisor named Patricia had sent something at 4:47 that was professionally phrased, all the right words, carrying the voltage of somebody about to lose it. The warehouse manager answered at 5:12, and the answer was tentative. Not the email of a person with a solution ready.
You don’t need to read the content when you’ve read twenty years of email like this. You read the gaps. The rhythm. The desperation dressed up in professional language.
I knew exactly what it was
Wrong inventory count. Shipping numbers and warehouse numbers off by about forty units.
Somebody had worked around a process — taken inventory without running it through the system, made a quick fix that felt necessary at the time. Now the system and reality were living in different places. One version of the truth in the computer, another on the shelves, no bridge between them.
The fix was straightforward. Not quick, but straightforward. Pull the physical counts, cross-reference the bills, isolate where the error entered the stream, then walk backward through whoever had worked around the system to understand why.
And then — this is the important part — fix the underlying thing, not the symptom. Because if you only fix the symptom, the next person works around the system in exactly the same way, for exactly the same reason, and you’re back here in five months.
I could have done all of it in an afternoon.
I didn’t.
Why not
Because I’d done it the last four times.
And every time I did it, three things happened that I hadn’t been counting.
Patricia learned that the ceiling of her competence was wherever I stepped in. Not because I told her that. Because I demonstrated it, repeatedly, at exactly the moment things got hard enough to be worth learning from.
The warehouse manager learned that hard problems get escalated. Not solved — escalated. That’s a skill too, and it’s the one I was training.
And I learned nothing, except that I was still needed. Which felt good, and was the actual reason I kept doing it, though I’d have told you at the time it was about the inventory.
The wobble
Here’s the thing nobody tells you about letting go: it doesn’t look like letting go. It looks like watching something you care about get slowly worse for about a week.
The reconciliation took eleven days instead of one afternoon. It was done less elegantly than I would have done it. They missed the underlying cause on the first pass and had to go back. Patricia sent two more emails I could hear the strain in.
Nothing broke. It wobbled.
That’s the distinction I’d ask you to hold onto, because it’s the one that separates delegation from abandonment.
Wobbling is a thing recovering its own balance. Breaking is a thing coming apart.
They are not the same and they don’t feel the same, but if you’ve spent years catching everything before it moves, you’ve lost the ability to tell them apart. Every wobble reads as a break. So you catch it. And it never gets the chance to steady itself.
How to know which one you’re watching
I use three questions. They’re not sophisticated but they work under pressure, which is the only test that matters.
1. Is anyone going to get hurt?
Not inconvenienced. Not embarrassed. Hurt.
If yes, step in immediately and without apology. Safety is not a development opportunity. That’s the entire exception and it’s not negotiable.
2. Is the cost recoverable?
Eleven days instead of one afternoon is recoverable. A customer relationship of fifteen years is not. Money is usually recoverable. Reputation with a regulator usually isn’t.
Be honest about the size, though. Most of us wildly overestimate this one, because “it’ll cost us” is a much more respectable reason to intervene than “watching this is uncomfortable for me.”
3. Do they know I’m here?
This is the one people skip, and it’s what makes the difference between letting someone struggle and hanging them out to dry.
Before it goes sideways, they need to have heard you say: this is yours, I think you’ve got it, and I’m right here if you want me.
Say it once, plainly, and then genuinely mean the second half. If they come to you, you don’t sigh. You don’t say “I was wondering when you’d ask.” You help, and you make it cost them nothing.
Otherwise you haven’t delegated. You’ve set a trap.
What it bought
Patricia runs those reconciliations now. All of them. She caught one last quarter that I would have missed entirely, because she was looking at a pattern I’d stopped checking years ago.
That’s eleven days of discomfort against a permanent increase in what the crew can handle without me.
And it’s the only version of leadership that actually scales, because the other version — the one where you’re the guy who fixes it — has a hard ceiling at exactly one person’s capacity.
You already know where that ceiling is. You’re standing on it.