Management Antipatterns: What a Bad Manager Actually Does

In software engineering we have a well-developed vocabulary for bad design: antipatterns. We know that a God Object is a bad idea, that cargo-cult programming leads to unmaintainable systems, and that premature optimisation is the root of much evil. But when it comes to management, we are often much less precise. «He's just a bad manager» is said, and everyone nods, but what exactly makes him bad?

This article attempts to be more precise. Based on observations from Selectel's engineering organisation and a broader survey of management literature and practitioner experience, here is a catalogue of management antipatterns — recurring behaviours that reliably degrade team performance, trust, and well-being.

1. Micromanagement

The most famous antipattern and, unfortunately, one of the most common. The micromanager checks in constantly, wants to approve every decision, rewrites subordinates' work, and is constitutionally unable to delegate anything of consequence.

The damage is multifaceted. First, it destroys autonomy — one of the three core pillars of intrinsic motivation identified by Daniel Pink (the others being mastery and purpose). When people cannot make decisions, they stop wanting to make decisions. Initiative atrophies. Second, it creates a bottleneck: every decision requires the manager's input, so the team's throughput is limited by one person's bandwidth. Third, it signals distrust, and distrust is corrosive — people who feel distrusted start behaving as if they deserve to be distrusted.

The micromanager often believes they are being helpful or thorough. The road is paved with good intentions. The remedy is deliberate practice of delegation: choose a task, hand it over completely, resist every urge to interfere, and review only the outcome.

2. Heroism Culture and the «Firefighter Manager»

This manager is always busy solving crises. They are the first to arrive and the last to leave. They are indispensable. When something breaks, everyone calls them, and they swoop in and fix it. They are the hero of the story they are telling themselves.

The problem is that heroism culture is almost always a symptom of systemic failure that the manager is perpetuating rather than fixing. Every fire that gets heroically extinguished is a fire that didn't need to start, or a fire that the team could have handled independently if systems and knowledge transfer were in place. The heroic manager keeps the team dependent, keeps processes fragile, and keeps themselves irreplaceable — which feels great until they burn out, or leave, or get sick, at which point everything collapses.

Healthy management looks boring from the outside. Processes run smoothly, the team handles incidents calmly, and the manager is rarely the most visible person in the room during a crisis.

3. Shield Mode: Hiding Reality from the Team

A well-intentioned but misguided pattern: the manager «protects» the team from bad news, difficult stakeholder demands, or organisational turbulence. «I'll handle it, don't worry about it» sounds caring but creates information asymmetry that backfires badly.

Teams that don't know the context they are operating in make decisions that are locally rational but globally destructive. They don't understand why certain priorities were set. They feel blindsided when reality eventually intrudes. They lose the ability to contribute to strategy because they have no strategic information. And when the manager eventually leaves, the institutional knowledge leaves with them.

Transparency has costs — it creates anxiety and noise — but those costs are almost always lower than the costs of information opacity.

4. The Meeting Maximalist

Meetings are how this manager works. Status meetings, sync meetings, retrospective meetings, planning meetings, meetings to discuss the outcomes of previous meetings. The calendar is full, which feels like productivity but is actually the opposite of it.

Synchronous communication is expensive. It pulls multiple people out of flow state simultaneously and produces a decision (or a vague consensus, or nothing) that could often have been produced by one person writing a document and asking for asynchronous feedback.

The rule of thumb: a meeting is justified when the value of real-time interaction (handling ambiguity, building rapport, unblocking dependencies) exceeds the total opportunity cost of everyone's attention. Most status updates do not meet this bar.

5. Feedback Avoidance

This manager doesn't give negative feedback. They smile, they say «good job», and then they either silently write the poor performer off or are blindsided when the problem grows too large to ignore and they have a difficult conversation that has been delayed by 18 months of missed earlier interventions.

Feedback avoidance comes from conflict aversion, which is natural and human. Telling someone their work is not good enough is uncomfortable. But uncomfortable conversations delivered early are almost always far less painful than the alternative: a person who never grew because nobody told them what to improve, or a team that lost respect for the manager because they saw the problem and said nothing.

Radical candour (Kim Scott's framework) is not about being brutal — it's about caring enough about the person's development to be honest with them.

6. Credit Absorption and Blame Distribution

Success is a team effort for which the manager takes credit. Failure is a team failure for which the manager finds individual scapegoats. This pattern is easy to sustain in the short term because it protects the manager's reputation upward. It is catastrophically destructive to psychological safety and team cohesion.

People will take risks, experiment, and occasionally fail if they trust that failure will be treated as a learning opportunity in a safe environment. They will not take risks if they believe failure will be publicly attributed to them while success will be attributed to the manager. Safe-to-fail environments are built by leaders who absorb blame and distribute credit — the exact inverse of this antipattern.

7. Vagueness as a Strategy

Goals are set in vague terms. Priorities are «everything is important». Deadlines are «as soon as possible». This creates a permanent state of low-grade anxiety in the team, where nobody is sure what «done» looks like or whether they are succeeding.

Vagueness is sometimes inadvertent — the manager genuinely hasn't thought through what they want. But it can also be strategic: vague goals are impossible to miss entirely, which protects the manager from accountability. If the goal was «improve the system» rather than «reduce p99 latency by 40%», it's hard to say it wasn't achieved.

The antidote is specificity. OKRs (Objectives and Key Results), for all their implementation difficulties, exist precisely to force this specificity: what are we trying to achieve, and how will we know we achieved it?

8. Perpetual Reorganisation

Every six months, the team structure changes. New squads are formed, old ones dissolved, reporting lines redrawn. Each reorganisation is announced as necessary and strategic. Each one creates months of confusion, disrupts working relationships, and interrupts ongoing work — after which the next one begins.

Frequent reorganisation is often a manager's way of demonstrating activity without the harder work of addressing the actual problems (unclear goals, poor processes, interpersonal conflict) that are causing underperformance. Structural changes are visible and legible. The underlying problems are not.

What Good Management Looks Like

The antidote to all of these antipatterns is not complicated, though it is demanding. Good management is characterised by:

• Clear goals and honest feedback about progress toward them
• Delegation with genuine authority
• Transparency about context and constraints
• Protecting the team's time and focus (fewer meetings, not more)
• Absorbing organisational complexity so the team can do deep work
• Building systems that don't depend on heroism
• Distributing credit and owning failure

None of this is exotic or proprietary. The challenge is doing it consistently, especially under pressure — which is exactly when the temptation to fall back on antipatterns is strongest.