The Micromanaging Boss: How to Spot It, Cope With It, and Get Out

It is the most frequently cited management behaviour, and the most often misidentified. Many people call micromanagement a close oversight that isn't; others live with textbook micromanagement without naming it, because their manager is courteous and they can't point to anything specific.

In the article that follows, I explore mental load and professional exhaustion. If you recognise yourself in this theme, the tests on the platform help you take stock of your tension level.

What it isn't

Close oversight isn't micromanagement. A weekly check-in, a shared dashboard, sign-off on financial commitments or client deliverables: these are normal steering mechanisms, and they're protective. A period of observation isn't either. A new manager, a new hire, a new project, a recent incident: control rises, then it comes back down. It's the coming back down that distinguishes. Demanding a good outcome isn't. Asking for impeccable work and refusing sloppy work is about the output, not the path. Micromanagement is about the path.

The three markers that distinguish it

1. Granularity

Control lands on decisions that belong to the role: the wording of a sentence in an internal note, the order of a table, who to ask about a routine question, the colour of a chart.

The test is simple: if the object of control is a decision the role is supposed to allow you to make alone, the granularity is excessive.

2. Absence of use

Reports, progress updates and tracking spreadsheets are demanded — and nothing observable follows. No decision rests on them, no feedback is given, nobody reads them again.

This is the most revealing marker, because it shows the mechanism has no steering function. Its function is to lower an anxiety, and it lowers it in the person who asks for it, not the person who produces it.

3. Temporal asymmetry

Your replies are expected within the hour. The approvals you're waiting on take days and block entire chains.

That imbalance produces micromanagement's most destructive effect: you are simultaneously under immediate pressure and prevented from moving forward.

What it costs, concretely

Time. The share of the day spent reporting rises mechanically at the expense of the share spent producing. Then production falls behind, which justifies more control. The loop is self-sustaining and closes within weeks. Decision-making. This is the most insidious effect. Having minor choices validated over and over, you stop making them. Highly autonomous people find themselves, after a few months, asking for sign-off on a three-line email. It isn't a loss of competence, it's the extinction of a behaviour: what is never allowed to be exercised stops being exercised. Switching off. The unpredictability of requests prevents you closing the day. Vigilance stays on in the evening — you keep an eye on the inbox "just in case" — and that residual vigilance, more than the workload, ranks first among burnout mechanisms. Reputation. A delayed and unfair effect: someone who has spent a year having their decisions validated looks, from outside, like someone who doesn't decide.

Where it comes from — and why that changes the strategy

Micromanagement is rarely a wish to crush. In the large majority of observed cases it comes from one of three sources.

Responsibility anxiety. The manager will answer for the error, they know it, and they can't tolerate not seeing. Control is a soothing behaviour — ineffective, like all avoidance of this type, since it soothes for an hour and reinforces the need afterwards. Technical promotion without training. The excellent specialist turned manager keeps doing the work they mastered, through other people. They aren't controlling: they're redoing. Pressure passed on. What they endure in reporting, they replicate identically one level down. Distinguishing sign: it appears and disappears with the company's cycles.

This origin matters, because it shows where to push. Control that comes from anxiety recedes when the anxiety falls. Control that comes from a wish to diminish someone does not recede for that reason — and that rarer case is handled differently: it belongs with the other behaviours described here.

Four levers that genuinely make anxious control recede

1. Supply before you're asked

Counter-intuitive, and the most effective. A short progress update, sent unprompted at a fixed time, costs fifteen minutes and removes a large share of scattered interruptions — because it treats the cause, which is uncertainty, rather than the symptom.

A format that works: three lines, same day, same time. What's done, what's in progress, what's blocked and by whom.

2. Propose the rhythm rather than absorb it

Ask for a frame instead of waiting for one to be imposed: "Would a thirty-minute check-in on Monday morning work, with the status sent the evening before?"

An anxious manager almost always accepts — they get visibility — and you gain control of the calendar.

3. Have it arbitrated in writing when oversight creates overhead

When the reporting mechanism consumes a visible share of your time, the right response isn't to complain about it but to have it arbitrated:

"The weekly reporting takes about half a day. To hold the delivery on the 12th, I need to know which takes priority: the reporting in its current format, or the date."

That message accuses no one. It turns a complaint into a prioritisation decision, and it leaves a dated trace of the overhead.

4. Separate the decisions that need sign-off

Propose an explicit list: what always goes up (financial commitment, external communication, change of scope) and what doesn't (decisions internal to the role). Even partial agreement on that list beats a permanent grey zone, and it can be referred back to later.

When these levers produce nothing

They don't always work, and it's better to notice that than to redouble the effort. Three signs that the control isn't anxiety-driven:

• it is selective — your colleagues at the same level don't get it;
• it increases when you supply more — every piece of evidence given prompts a further demand;
• it lands on inconsequential points while genuinely blocking issues go unanswered.

In those cases the dated record becomes the main tool: log the requests, the delays, the blockages and their effects on deliveries. That is what ScanMyJob produces — a chronology of observable facts, without a conclusion, usable by a third party.

And if you are the one micromanaging

The question is worth asking plainly, because almost nobody recognises themselves in the word. Three honest indicators:

• you systematically reread deliverables you almost never change;
• you ask for progress updates you do nothing specific with;
• the idea of a project moving forward without your having seen every step makes you uncomfortable, including when the result is good.

This isn't a moral failing, it's a response to a worry. It can be worked on — and the blind spots of management have a whole article.

One limit to keep in mind

This article describes behaviours and ways of acting. It does not characterise the person or the situation, and it cannot say whether what you are living through falls under a legal category — that question belongs to a lawyer. If your health has changed lastingly, occupational health services, where they exist, can generally be contacted at your own initiative without going through your employer.