Skip to content
Micromanagement

Micromanagement: The Email That Needed Approval

A manager insists on approving a simple three-line email before it can be sent, turning a thirty-second task into a multi-day ordeal.

Explanation

It was a three-line email. A routine reply to a client confirming a meeting time. It should have taken thirty seconds. But your manager wants to review it first. So you send them a draft. They take two days to respond. When they do, they change one word and add a comma. You send the revised version for final approval. They are in meetings all day. The client follows up asking if you received their message. You cannot reply because you are still waiting for permission to say 'Yes, Tuesday works.' This is micromanagement at its most absurd -- and its most revealing. The manager who needs to approve a routine email is not protecting quality. They are managing their own anxiety by maintaining the illusion of control over every output. Research on self-determination theory shows that autonomy is a core human need, and when it is systematically removed, people do not become more careful -- they become more passive. You stop thinking for yourself because every independent thought requires a permission slip. Over time, the micromanager creates the very incompetence they fear, because initiative has been trained out of the team. The healthier approach, if you are being micromanaged, is to name the pattern without attacking the person. Try: 'I want to make sure I am using your time well. Could we agree on which decisions need your input and which I can handle independently?' This gives the manager a sense of control while creating space for your autonomy. If that does not work, it is worth recognizing that no amount of perfect performance will satisfy someone whose need for control is bottomless.

Key Takeaway

If you need approval to send a three-line email, the problem is not the email -- it is that trust has been replaced by control.

A Better Approach

A stick figure listing all the routine tasks that currently require approval, recognizing the bottleneck pattern

Map the bottleneck. If everything needs a stamp, nothing moves.

The stick figure proposing to their manager: 'Routine replies I handle. Strategic decisions I run by you. Can we try this?'

Frame it as efficiency, not rebellion. Give control where it counts.

The stick figure sending a routine client email independently while flagging a contract question to the manager for input

Autonomy on the small things. Collaboration on the big ones.

The client getting timely replies, the manager focusing on real decisions, and the stick figure working with purpose instead of waiting

Trust is not all or nothing. It can be built one decision at a time.