Dear Leaders,

I hear it more often now, which usually means a word has begun doing damage.

A highly successful executive sits across from me, lowers their voice, and confesses:

“Hamza, I think I’m a micromanager.”

There is usually a trace of embarrassment, as though admitting to some outdated managerial vice, like smoking in the office or yelling at reception.

I don’t blame them. Corporate America has done a brilliant job of brainwashing us. We elevated “Delegation” and “Empowerment” to religious status, and turned “Micromanagement” into the ultimate executive heresy.

You are told that if you touch the granular details of your team’s work, you are a toxic, insecure bottleneck who stifles innovation.

It’s a tidy story. Reality is less polite.

So whenever a client says that to me, I ask the same question:

Give me the exact example. What did you do?

And we pull the incident apart. Because there are two entirely different species of this behavior. One is a disease. The other is mandatory for survival.

Here are actual clients of mine who “micromanaged” their teams:

1. A founder twelve months into hyper-growth is sorting out her first executive hires, refining the core product, and securing her Series A simultaneously. She is in every facet of the business. She audits the wireframes, reads the outbound sales copy, and sits in on mid-level interviews.

Some call this “failing to scale.” I call it staying alive. Year One is not a democracy. It is triage. You don’t hand off core decisions to people who arrived three weeks ago.

2. The founder/CEO of a multi-decade family business watches a critical supply chain issue unfold in real time. He built the company from nothing. He knows where these situations usually unravel, and he steps in immediately, directing the fix as it happens.

In the process, he turns the entire episode into a lesson. Twenty-five years of judgment is being transferred in real time. The problem gets fixed, and the team sees exactly how an experienced operator behaves under pressure.

3.  A partner at an elite investment bank gets a call at 6 pm on the Friday of a holiday weekend. A tier-one client needs something urgent done by Tuesday morning. It’s a two-week job compressed into 72 hours.

He calls his team, cancels their weekend, and instead of “empowering” them to figure it out, he sits on the calls, reviewing pages line by line, checking numbers himself, dictating the wording of key slides.

Why? Because when the work is client-facing and the margin for error is zero, credibility is revenue.

All three of these executives felt guilty. All three of them were completely wrong to feel that way. Practicing hands-off leadership in those moments would’ve been gross executive negligence.

Look closely at any operation where standards are brutally high, and you will usually find someone obsessed with detail at the center of it.

David Fincher makes generation-defining films. He notoriously runs his cast through 90 takes of a single scene – someone setting down a glass of water – to capture the exact, microscopic expression of dread he wants. His crews call it exhausting. They also keep coming back.

A few weekends ago, I visited a friend who runs a three-Michelin-star kitchen in NYC. I stood in the corner during Saturday dinner service. If a chive was a millimeter off-center, if a sauce reduced thirty seconds too long, the plate went in the trash. He watched every hand, every garnish, every wiped edge of porcelain. Brutal, granular, unrelenting micromanagement.

That level of scrutiny is part of why he still has those three stars.

I remember reading about Ben Bradlee, who ran the Washington Post during the most consequential period in American political history. He was notorious for his habit of grabbing copy off a reporter’s desk and rewriting the lede himself. Not suggesting, rewriting the whole thing. Reporters hated it. Editors called it corrosive to ownership culture. Bradlee agreed with them, but wouldn’t stop. The reporters he “undermined” went on to win Pulitzers. Several said later the lede rewrites were the best education they ever got.

The best work you’ve ever seen up close was made by someone who couldn’t leave it alone.

The difference between the two isn’t visible in the behavior. It’s in what’s driving it:

Anxiety-Driven Micromanagement: You micromanage because you need to feel safe. You demand to be CC’d on trivial emails. You rewrite a mid-level manager’s perfectly fine internal memo because you prefer a different adjective. You refuse to let your VP sign a $5,000 vendor contract without your signature.

This has nothing to do with risk mitigation. This is self-protection. You are terrified of becoming irrelevant, and you are using your authority to soothe your own psychological anxiety. This is the behavior that destroys morale, bottlenecks the company, and is a strong indicator that a change must be made within you.

Tactical Micromanagement: You micromanage because there is no margin for error. The timeline is impossible. The structural foundation of a new division is being poured, and if it dries crooked, the building collapses. You dive into the weeds, take the wheel, execute the maneuver, and once the crisis is averted or the system is stable, you step back out.

This type of micromanagement isn’t only good and necessary, not doing it is irresponsible.

Autonomy at work is often spoken of as though it were a moral entitlement.

It is not.  Autonomy is earned through a demonstrated history of competence. Your job is to calibrate how much rope you extend and to whom. Sometimes that calibration means you take the rope back entirely. That isn’t a failure of trust. It’s good judgment.

You have to know how to operate at 30,000 feet, and exactly when to drop to three inches. Know when to zoom out and let your high-performers run. But stop being afraid to zoom in so close it makes people uncomfortable.

Sometimes the devil really is in the details, and someone has to go down there and deal with him.

The immature leader interferes constantly. The mature leader knows exactly when interference is required.

Tactical micromanagement isn’t a failure of leadership. It is the job.

Onward,

Hamza