A Toxic Manager Without Knowing It: The Blind Spots of Management

There is a gap that is rarely discussed: almost every article on difficult management addresses those who suffer it, and hardly any addresses those who produce it. Yet in most observed situations, the manager doesn't know.

That is not an excuse, and it isn't naivety either. It is a structural property of the position, and it has six identifiable causes.

In the article that follows, I explore the burden of management and workplace stress. If you recognise yourself in this theme, the tests on the platform help you take stock.

The six blind spots

1. Asymmetry blocks feedback

This is the central mechanism. Someone who depends on you for their appraisal, their hours, their projects and their progression will not tell you that your way of working costs them. The cost of saying so is too high and the benefit too uncertain.

The manager therefore receives, structurally, a filtered flow of feedback: what comes up is what is risk-free. And they draw a logical, false conclusion — since nobody says anything, everything is fine. A manager who has never received negative feedback from their team does not have a satisfied team: they have a team that doesn't speak.

2. Intention is visible from inside, invisible from outside

You know why you were short in that meeting: you had just come out of a difficult committee, the news was bad, you didn't have the facts. That information exists only in your head.

On the other side, there is only a behaviour. And a behaviour without its context gets interpreted — usually in the worst light, because that is how threat evaluation works.

Which is why explicit repair beats silent good intentions. One sentence — "I was short yesterday, it wasn't aimed at you, I'd come out of a tense committee" — costs ten seconds and repairs what matters. Without it, the episode stays as it was in the other person's memory, and adds to the previous ones.

3. Pressure received is passed on unchanged

A manager under an impossible target almost always reproduces, one level down, the exact form of what they endure: the same impossible deadlines, the same useless reporting, the same absence of criteria.

They don't experience it as transmission. They experience it as "how the business works". The distinguishing sign is temporal: these behaviours appear and disappear with cycles — closings, budget reviews, reorganisations.

This isn't an individual problem, it's an organisational one. It isn't corrected by personal willpower but by explicitly filtering what must be passed on and what must be absorbed.

4. The promoted expert who redoes instead of managing

Technical promotion is the most common and least supported route into management. The outstanding specialist becomes responsible for a team doing what they did better than anyone.

They have no intention of controlling; they have a habit of doing. They revise, they correct, they redo — and what they experience as help is experienced opposite as dispossession. It is the most frequent source of micromanagement.

5. The difference in scale

A remark that costs you thirty seconds can occupy an entire weekend for the person receiving it. That isn't hypersensitivity: it is the mechanical effect of the position. What a manager says engages a role, a progression, an income. What a peer says engages nothing.

Practical consequence: a sentence thrown out without thinking does not exist without thinking. A remark like "we'll see whether you're up to this one", said as a joke, can be replayed for weeks by the person who heard it.

6. The inner circle that forms by itself

Nobody decides to have favourites. But desk proximity, similarity of background, the ease with which some people ask, and availability at informal moments create, within weeks, a circle that gets more information, more autonomy and more visible work.

From inside, it feels like fluidity. From outside, it is favouritism — and both readings describe the same facts.

The special case of "kind" management that constrains

This variant deserves separate treatment, because it is hard to name and because it claims the opposite.

Three mechanisms:

The request that can't be refused because it is kind. "I know you're swamped, I wouldn't ask if I had anyone else, but you're the only one who can do it." The framing makes refusal ungracious. The result is the same as an order, without the possibility of discussing it. The absence of criteria in the name of flexibility. Refusing to set targets so as not to seem "rigid" produces exactly the effect described elsewhere: work you can never know you have succeeded at. Kindness does not compensate for undecidability — it makes it harder to challenge. Disagreement turned into a relational problem. When a professional objection is answered with "I'm disappointed", the exchange changes register: it was never the idea that was at stake, it was loyalty. That extinguishes disagreement far more effectively than a curt reply.

A team that never contradicts a very pleasant manager is not an aligned team. It is often a team for whom contradicting has become expensive.

Five checkable questions to ask yourself

They are about facts, not intentions.

When was I last contradicted, and by whom? If no date comes to mind, that is the first thing to address.

Are my appraisal criteria written down anywhere? If the team had to state them without me, would the answers agree?

What is my median response time on blocking issues? It is measurable in your inbox, and the gap with what you assume is often large.

Who did I give the last three visible projects to, and on what statable criterion?

When did I last repair something? Explicitly revisiting an episode where I was unfair or too harsh.

How to get usable feedback

Asking "is everyone okay?" in a team meeting produces nothing, for the reason set out in the first blind spot.

What does produce something:

• a genuinely anonymous survey, with enough respondents for the anonymity to hold;
• questions about facts, not feelings: "Were the criteria for evaluating your work stated in advance?", "Have you ever decided not to flag a problem? Why?";
• a third party: a peer from another department, HR, an external coach — someone the team doesn't depend on;
• and above all, visible follow-up. A feedback mechanism with no visible consequence is worse than none: it teaches people that speaking up is pointless.

From the employee's side: what this changes, and what it doesn't

What it doesn't change: the effects. A brief that changes three times costs the same whether it was deliberate or not. Sleep doesn't distinguish intent from negligence, and nobody has to tolerate more on the grounds that "it isn't on purpose". What it changes: the lever. Behaviour that comes from a blind spot can recede once it is made visible — through a confirmation email, a request for criteria, feedback framed factually. Behaviour that comes from something else does not recede for that reason, and it is better to notice this than to redouble the effort.

The test is on the facts: does the situation change when it is named, or not? A dated record like ScanMyJob lets you answer on a series rather than an impression. And the five criteria that separate demanding from damaging provide the reading frame.

One limit

This article describes mechanisms and blind spots. It does not say what any particular manager is, nor what the law would make of a given situation — that second question belongs to a lawyer. And if your health has changed, occupational health services, where they exist, can generally be contacted at your own initiative without going through your employer.