When the Best Technician Becomes the Bottleneck

Micromanagement is exhausting.

If you’ve worked under it, you know exactly what it feels like before you can even name it.

Your work gets reviewed before it’s finished. Your decisions get revisited after they’ve been made. Your updates become more frequent than your actual output. Small corrections arrive on things that were working fine. Ownership quietly drains out of the work, and you’re not always sure when it happened.
Here’s the part that doesn’t get said often enough: most of the time, it didn’t start with distrust.

It started with a promotion.

The best technician on the team. The one who always stabilized the system, closed the ticket nobody else could close, and kept things from going sideways at 2 a.m. At some point, that person became responsible for a team.
And why wouldn’t they be? Their track record was the proof.

What rarely happens next is a clear conversation about what success looks like now.

New responsibilities appear – meetings, planning, reporting, headcount. But those are tasks, not a definition of success. The actual shift – from individual output to team outcomes – often goes unnamed. Nobody sits down and says “your job is no longer to fix it yourself; your job is to make sure the team can fix it without you.”

So the habits that built the career stay intact. Fix it, ship it, close it – just applied one level up.

Review more closely. Correct earlier. Stay involved, just to be safe.
Not out of malice. Not out of distrust. Out of ambiguity – and the very real discomfort of being accountable for outcomes you’re no longer directly producing.

That’s where micromanagement usually begins. Not as a character flaw, but as a leadership transition that was never fully made.

Recognizing that doesn’t make it easier to work under. But it does change what the problem actually is – and what’s worth addressing.

Flipping the perspective on Management after Promotion

For those being managed closely, the frustration is real and valid. Ownership matters. Autonomy isn’t just about comfort – it’s how people develop judgment, build confidence, and grow into roles that require independent decision-making. When every decision gets second-guessed, the signal received is that judgment isn’t trusted. Over time, people stop exercising it.

For those who recognized themselves as the manager in that post – that recognition matters. It’s worth sitting with.

If you’re on the receiving end

The instinct is to push back on individual decisions. That specific ticket, that particular change, that correction that didn’t need to be made. Sometimes that’s necessary. But the more productive conversation is usually a level up from the specific instance.

What would make delivery more predictable? What would reduce rework? What would lower after-hours escalations or eliminate single points of failure? Conversations framed around stability and risk tend to land differently than conversations framed around autonomy – even when autonomy is exactly what’s at stake.

It also helps to understand what the organization is actually prioritizing right now. Growth, cost control, stability, risk reduction – the answer shapes how much control feels necessary to leadership, and what kinds of outcomes might shift that calculus.

That’s not a suggestion to absorb poor management quietly. It’s a suggestion to pick the conversation that’s most likely to move something.
If you’re the manager

The harder question is this: what is success in your role actually being measured by?

If the answer is flawless execution and incident avoidance, stepping back will always feel risky – because under that definition, it is. Every delegated decision is a potential failure point you didn’t control.

If the answer includes team resilience, capability development, and reducing single points of failure, then control becomes the liability. A team that only performs well when you’re closely involved is a fragile system. And IT professionals understand fragile systems.

The transition from individual contributor to leader isn’t about doing less. It’s about changing what you’re responsible for building. The instinct to stay close, correct early, and remain involved doesn’t disappear on its own. It has to be replaced by something – a clearer definition of what the role is actually for, and metrics that reward building capability rather than demonstrating it personally.

If execution remains the only metric, control will remain the instinct.

---

Version 1.1 – Revised February 2026