The Five Traps: Super-Doer, Buddy, Micromanager, Seagull, Firefighter

The Five Traps Every New Manager Walks Into

Here is something that should both unsettle and reassure you: the way you are about to fail as a new manager is almost entirely predictable. Decades of observation across thousands of organisations have shown that new managers don't fail in infinite, creative ways. They fail in five remarkably consistent patterns. These patterns are so reliable that an experienced executive coach can usually identify which one a new manager is sliding into within twenty minutes of conversation.

This is good news. It means you don't need to invent a unique survival strategy. You need to recognise the trap you are most prone to, spot the early warning signs, and apply a known antidote. The traps are not character flaws. They are not signs that you shouldn't be a manager. They are the natural consequence of being good at something else (individual contribution) and suddenly being asked to do something different (leading people) without the muscle memory yet built.

What makes the traps dangerous is not their existence but their invisibility from the inside. Each one feels, in the moment, like the responsible thing to do. The super-doer feels they are pulling their weight. The buddy feels they are being kind. The micromanager feels they are ensuring quality. The seagull feels they are being decisive. The firefighter feels they are being heroic. Every trap has a virtuous story it tells itself, and that story is exactly what keeps you stuck in it.

In this lesson we will walk through each of the five, name the specific behaviours that signal you are caught, diagnose the root cause, and give you the antidote. By the end, you should be able to name your personal default — the trap you fall into under pressure — and recognise the first early warning sign. That self-awareness is, by itself, ninety percent of the escape route.

Trap One: The Super-Doer

The super-doer is the most common trap, and by a significant margin. It is the manager who cannot stop doing the work that got them promoted. They were the best engineer, the best salesperson, the best analyst — and now, even though their job title has changed, their calendar still looks like an individual contributor's. They take on the hardest tickets themselves. They rewrite their team's pull requests rather than coaching them through the changes. They jump on the difficult client call instead of letting their account manager handle it. They tell themselves they are "just helping out" or "protecting the team's bandwidth."

The behaviours to watch for: You find yourself working evenings and weekends while your team leaves at five. You feel a small thrill of competence when you do the technical work, and a vague dread when you have to do the management work. You skip one-to-ones because something "urgent" came up — and the urgent thing is almost always something you should have delegated. You measure your day by what you personally shipped.

The root cause: Identity. You were promoted because you were excellent at the craft, and your sense of self-worth is wired to that excellence. Leadership work feels uncomfortable because you are mediocre at it (everyone is, at first), and humans naturally retreat to where they feel competent. There is also a deeper fear: if you stop doing the work, what exactly is your value? You haven't yet internalised that your value is now the team's output, multiplied.

What it costs the team: Your people stop growing because you take all the interesting work. The best ones leave because they are not being developed. The rest learn helplessness — why try hard when the boss will just do it? Your team's capacity is capped at one (you), instead of multiplied. And you burn out, because you are now doing two jobs badly instead of one well.

The antidote: Each week, audit your calendar. For every task you did personally, ask: could someone on my team have done this at seventy percent of my quality? If yes, that task should have been theirs. Seventy percent done by them beats one hundred percent done by you, because it builds capacity. Make a written list of the three technical tasks you are most reluctant to hand over. Those are precisely the ones you must delegate first.

Trap Two: The Buddy

The buddy is the manager who cannot tolerate the distance that comes with the role. They want their team to like them. They were promoted from within and are managing former peers, and the relational gravity is enormous. So they soften every piece of feedback into mush. They avoid the difficult conversation about Marcus's persistent lateness. They say yes to every request for time off, every push-back on a deadline, every "can we do this differently?" because conflict feels like a betrayal of friendship.

The behaviours to watch for: You rehearse difficult conversations in your head and then don't have them. You find yourself agreeing to things in meetings that you later regret. You give vague feedback like "yeah, that was good — maybe just tighten it up a bit?" when you actually thought it was below standard. You feel anxious before one-to-ones with certain team members. You catch yourself wanting to be "one of the team" at the pub more than you want to lead them on Monday morning.

The root cause: A confusion between being liked and being respected. These are not the same thing, and over time they often diverge. People can like a manager who is weak and still not respect them — and respect, not affection, is what makes a team trust your judgement when things get hard. There is also often a fear of loneliness: management is, by nature, a slightly more solitary role, and the buddy is trying to outrun that loneliness.

What it costs the team: Standards erode quietly. Your high performers lose faith because they see poor performance going unchallenged. Resentment builds — people work hard while others coast and nothing happens. Eventually you will be forced into a hard conversation you should have had six months ago, and it will be ten times harder because the behaviour is now entrenched and the person has every reason to think it was fine.

The antidote: Reframe your job from "being liked" to "being trusted to tell the truth." The most generous thing you can do for a team member is to tell them, kindly and specifically, where they are falling short — because that is the only way they grow. Practise small acts of candour weekly. Say the slightly uncomfortable thing in the meeting. Give the feedback the same day, not a fortnight later.

Trap Three: The Micromanager

The micromanager is the trap that gets the worst press, and rightly so — it is corrosive to talent and exhausting for everyone involved. But it is almost always misdiagnosed. Micromanagers are not, as a rule, controlling tyrants. They are usually anxious perfectionists who genuinely believe they are being thorough. They check in "just to see how it's going" three times a day. They ask to be copied on every email. They redo work that was perfectly adequate because it wasn't done their way. They confuse oversight with control.

The behaviours to watch for: You ask for status updates more often than your team can plausibly have made progress. You find yourself editing other people's work for stylistic reasons rather than substance. You want to be in every meeting. You feel uncomfortable when you don't know exactly what each team member is doing right now. You give detailed instructions on how to do things rather than describing the outcome you want.

The root cause: Anxiety dressed up as standards. The micromanager believes that if they look away, something will go wrong, and they will be blamed. There is often a history of being burned by a delegated task that went poorly, and the response is to never feel that vulnerability again. There is also frequently a hidden belief — rarely admitted — that nobody on the team is quite as capable as the manager, so close supervision is simply realism.

What it costs the team: Your best people leave. Always. Talented professionals do not tolerate being treated like apprentices. The ones who stay become passive, because initiative is punished — every independent decision gets second-guessed, so why bother making any? You become the bottleneck for every decision, and your team's velocity collapses to whatever speed you can personally process. Worst of all, you never find out what your team is actually capable of, because you never let them try.

The antidote: Shift from inputs to outputs. Define what "done" looks like at the start, agree the check-in cadence (and stick to it — no extra check-ins), and then get out of the way. When you feel the urge to check in early, write it down instead of acting on it. Most of the time you'll realise an hour later that you didn't actually need to know. We will return to this in depth in the delegation module.

Trap Four: The Seagull

The seagull manager is a memorable archetype because the metaphor is so accurate. The seagull flies in, makes a lot of noise, dumps on everything, and flies off again — leaving the team to clean up. They are largely absent — in other meetings, working on their own priorities, dealing with their own manager — and then they appear suddenly when something goes wrong, deliver strong opinions and criticism, and disappear before they can be held accountable for any of the consequences.

The behaviours to watch for: Your team is frequently surprised by your interventions. You give feedback on the end product without having engaged with the process. You appear in Slack threads only to disagree, then go silent. Decisions are made in your absence and then reversed when you find out. You don't have a clear sense of what your team has been working on day-to-day. People stop inviting you to things because your involvement is unpredictable.

The root cause: Usually overload combined with a failure to delegate properly. The seagull manager is genuinely too busy to be present, but instead of solving that by reducing their plate or delegating real authority, they parachute in to apply their judgement at the worst possible moment — when the work is already done. There is also sometimes a darker version: the manager who likes to be the smartest person in the room and uses sudden criticism as a way to assert their superiority.

What it costs the team: Trust collapses. Your team learns that engaging you is dangerous — better to keep their heads down and hope you don't notice. Innovation dies because nobody will take a risk that might attract your sudden displeasure. The team becomes politically defensive, building cover stories rather than working on the actual problem. And when you do swoop in, the rework cost is enormous because you are intervening after the work is largely complete.

The antidote: Engage early and often, or not at all. If a project matters, be present at the start when shaping is cheap. If it doesn't matter enough for you to be present, then trust the outcome. Set a rule for yourself: you do not give critical feedback on work whose direction you did not weigh in on at the outset. This forces you to either show up properly or stay out properly.

Trap Five: The Firefighter

The firefighter is the manager who is permanently reactive. Their day is a sequence of urgent interruptions, escalations, and crises. They are forever putting out fires. They feel heroic and important — look how needed they are! — but they never get to the strategic work, the development conversations, the systems improvements that would prevent the fires in the first place. They confuse urgency with importance, and motion with progress.

The behaviours to watch for: Your calendar is dominated by reactive meetings — "quick syncs," escalations, problem calls. You haven't done deliberate one-to-ones in weeks because something always bumps them. You feel adrenalised most of the day but can't articulate what you actually accomplished. You are proud of being responsive. You measure yourself by how many problems you solved today, not by what you built.

The root cause: Two things, usually together. First, an addiction to the dopamine of resolved crises — there is a real chemical reward to solving an urgent problem, and it is more immediate than the slow satisfaction of building team capability. Second, a system that is producing fires faster than anyone can extinguish them, because nobody is doing the upstream work of prevention. The firefighter is often the person creating the very conditions that require them.

What it costs the team: Nothing strategic ever gets done. The team's capability stagnates because development always loses to urgency. The same fires recur because nobody has time to do root-cause analysis. Your best people get exhausted because they are firefighting alongside you. And you, personally, never grow as a leader because growth requires reflection, and reflection requires uninterrupted time, which you have eliminated.

The antidote: Ruthlessly distinguish urgent from important. Block protected time each week for non-urgent work — strategy, development, systems. Treat that time as inviolable, the way a surgeon treats theatre time. For every fire you fight, ask afterwards: what system would have prevented this, and when am I going to build that? If you can't answer the second part, you will be fighting the same fire next month.

The Hybrid Traps and the Pressure Pattern

One subtlety worth flagging: most managers are not pure types. You will have a primary default and a secondary one, and they often reinforce each other in ugly ways. The super-doer who is also a buddy ends up doing the work and protecting the underperformer who should have been doing it. The micromanager who is also a firefighter creates the very fires they then fight, by bottlenecking every decision through themselves. The seagull who is also a buddy gives mushy criticism when they finally swoop in, leaving the team confused about whether they should change anything.

Pay attention to the combination, not just the primary. And pay particular attention to how the pattern shifts under different kinds of pressure. Many managers default to micromanagement when they are anxious about a specific deliverable, but slide into firefighting when their broader workload spikes. Knowing which pressure triggers which trap lets you pre-empt your own behaviour.

There is also a developmental sequence worth knowing. Most new managers cycle through the traps in a recognisable order during their first eighteen months. They start as super-doers (because that is what they know). When they realise that is not working, many overcorrect into micromanagement ("I'll let them do it, but I'll watch closely"). When that exhausts them, they tip into seagull or firefighter behaviour ("I literally don't have time for this anymore"). The buddy trap can appear at any stage, particularly when managing former peers. Recognising where you are in this sequence is itself a form of progress.

Why Self-Awareness Is the Whole Game

You may have noticed that every antidote in this lesson started with noticing — auditing your calendar, writing down the urge, observing the behaviour. That is not a coincidence. Every one of these traps is invisible from the inside while you are in it. The super-doer feels productive. The buddy feels kind. The micromanager feels diligent. The seagull feels decisive. The firefighter feels heroic. The trap defends itself by making its own behaviour feel virtuous.

The only reliable escape is external feedback combined with structured self-observation. This is why the rest of this course leans so heavily on practices — one-to-ones, feedback loops, peer learning, structured reflection — rather than just frameworks. Frameworks teach you what good looks like. Practices show you, in real time, where you are falling short of it. Both matter, but practices are what change you.

In the next lesson we move from diagnosis to one of the most fundamental leadership distinctions you will ever learn: the difference between authority (a small, finite battery) and influence (a renewable, compounding asset). Understanding that distinction will determine whether your career as a leader is exhausting or generative.