I learned this with John, my most trusted manager. He'd been with us since day one, proven through every storm the business survived. Promoting him was the easiest call I ever made.

Then, slowly, he went passive. Or maybe he was passive all along and I only noticed now.

Decisions that were his sat waiting for my opinion. Escalations skipped him and landed on my desk. His own team started walking past him to ask me instead.

We talked about it. More than once. Direct, then softer, framed as development. He nodded. Agreed. Nothing changed.

I thought it was just us.

Then I started working with other founders, and saw the same thing everywhere. Almost every business, somewhere around and past 7-figures, has a John.

There are three reasons a competent technical person goes passive after a managerial promotion. Only one of them is actually about the manager.

Cause A — Capability gap: the skill genuinely isn't there for the task that's failing.

Cause B — Authority gap: they have the title, not the territory. Their team bypasses them because they don't have what they need to actually decide.

Cause C — You: a hundred small, reasonable moments. Sitting in on one meeting. Adjusting a decision slightly. Taking an escalation instead of pushing it back down. Each one justified. Together, they teach your manager that waiting is safer than deciding.

Here's the question that tells you which one you're dealing with:

If yes, the skill is there. Something else is blocking it.

The instinct that made me indispensable to this business was the same instinct quietly disabling John.

Which one are you looking at right now, A, B, or C? 💡

To Help you Figure it Out. Grab the Diagnostic Worksheet Below 👇