Five Ways New Managers Sabotage Their Own Teams

12 min read

Most writing about self-sabotage frames it as a private problem. You are the one who suffers, you are the one who loses out, you are the one who has to break the pattern. Management self-sabotage is different, and the difference matters. When you sabotage yourself as an individual contributor, you pay the cost. When you sabotage yourself as a manager, your team pays the cost with you, usually more than you do, and usually without knowing that is what is happening.

This is a catalog of the five patterns we see most often in early-career managers, written from the inside. Each one starts as a reasonable impulse, hardens into a habit, and eventually becomes the thing that caps the team’s ceiling and your own.

Each of these self-sabotages is reversible with a single deliberate choice. Harvard Business Review’s Managing Yourself archive is the best outside library for the patterns new managers most commonly fall into.

1. Over-Delivering Instead of Delegating

This is the first pattern and the most common. You take on more than your role requires, ship it yourself rather than route it to the team, and tell yourself it is because the work needs to be done well and fast. What you are actually doing is three things at once: protecting yourself from the anxiety of someone else doing the work differently than you would, avoiding the harder managerial work of coaching someone through a first attempt, and quietly building a case for your own indispensability.

The tell is resentment. If you find yourself thinking “I’m the only one who cares about quality around here,” you are in this pattern. Your team is not underperforming because they do not care. They are underperforming because you have not given them the repetitions they need, and you have not given them the repetitions because you keep pulling the work back the moment it gets hard.

The fix is uncomfortable. Let something ship at 80 percent of your standard. Do not rescue it. Do a proper retro afterward with the person who owned it. Their version two will be closer to 90 percent, and you will have gained something you cannot fake: a team member who knows you will let them actually own work.

2. Being “Nice” Instead of Being Clear

This is the pattern that does the most damage per unit time, and it is the hardest to see in yourself because it feels virtuous. You soften feedback. You hedge expectations. You praise effort instead of output. You say “let’s explore this direction” when you mean “do not do it that way.” You end hard conversations with a warm moment that leaves the other person unsure whether the hard thing was real.

You are doing this because clarity feels aggressive and you do not want to seem mean. The cost is that your team is flying with fogged instruments. They cannot course-correct because they do not know which way to correct. They develop a working theory of you as a manager who will not tell them the truth, which makes them stop asking for your input, which makes your feedback sessions increasingly hollow. By month nine, everyone is polite and no one is improving.

The fix is a sentence structure. “The thing I want to be direct about is [X]. The reason I think it matters is [Y]. What would need to be true for you to change [Z]?” Say it exactly that way at first. The scaffolding protects you from the impulse to soften, and the third question turns the feedback into a conversation instead of a verdict. Your team will not like the feedback more, but they will trust you more, which is the actual currency.

3. Checking In Too Often

This one masquerades as care. You Slack your direct report to ask how the project is going. You drop into their work-in-progress doc three times a day. You schedule “quick syncs” between their 1-on-1s. You tell yourself you are being available and attentive.

What your team member is experiencing is surveillance. Not because you intend it that way, but because a person who is trusted does not get checked on six times a day. Your anxiety has become their environment. They start performing progress rather than making progress, because performing progress is what your check-ins require. They stop taking on ambiguous problems because ambiguity is harder to narrate in a Slack update.

The fix is to notice the impulse to check in and do nothing with it. Write down the question you were going to Slack, save it for the 1-on-1, and see if it still matters by then. Two-thirds of the time it does not. The remaining third is the signal worth keeping.

4. Playing the Shield Too Well

A common piece of management advice, one we believed for years, is that a manager’s job is to shield the team from organizational chaos. Push back on unreasonable requests from above. Absorb the political friction. Let the team focus on the work.

This is half right. Taken too far, it becomes a form of self-sabotage that hurts the team more than it helps them. When you absorb all the context, the team loses their ability to make good calls, because good calls require understanding the constraints. When you absorb all the friction, the team never develops the political and interpersonal judgment that senior ICs need. When you take every hit, you become the single point of failure for the team’s connection to the rest of the company, and when you burn out or leave, they are suddenly exposed with no skills for the exposure.

The fix is selective transparency. Not radical transparency, which has its own problems. Ask yourself, for each piece of context you are carrying alone, whether your team would make better decisions if they knew it. If the answer is yes, share it, even if sharing it means they will be annoyed, anxious, or distracted. Annoyed-but-informed beats calm-and-wrong every time.

5. Avoiding the Conversation You Know You Need to Have

This is the master pattern that contains most of the others. There is a specific conversation you need to have, with a specific person, about a specific thing, and you have been avoiding it for weeks. You know you are avoiding it. You have even scheduled it once or twice and then moved it. Every day you do not have the conversation, the team operates on a slightly worse information set, and the cost compounds.

You are avoiding it because the conversation will produce an outcome you do not want to be responsible for. Telling someone their performance is not at the level required. Telling a team member you do not think they are ready for the promotion. Telling your peer that their team’s work is blocking yours. Telling your boss you disagree with the direction. Each of these conversations has a predictable trajectory: a hard moment, a few days of awkwardness, and then a meaningfully better working relationship on the other side. The cost of avoiding them is always more than the cost of having them, but the costs are paid on different timelines, which is why this pattern persists.

The fix is a calendar rule. Every Friday afternoon, list the conversations you have been avoiding this week. Put one of them on the calendar for the following week. Do not let the list exceed three items without clearing it. This is crude, but it works, because the bottleneck is never the conversation itself; it is the decision to have it. Forcing the decision onto a calendar removes the daily re-evaluation that lets avoidance win.

The Thread Running Through All Five

Each of these patterns is, at root, an attempt to manage your own anxiety at the expense of your team’s development. That is worth sitting with. Most management self-sabotage is not laziness or incompetence. It is the quiet, plausible-looking refusal to tolerate the discomfort that comes with actually doing the job, and it overlaps heavily with the imposter syndrome most first-time managers are also quietly carrying.

The work is not to eliminate the discomfort. The work is to build enough self-awareness that when the anxiety starts steering, you can name what is happening and choose the harder move anyway. The harder move is almost always the right one, because in management, what is hard for you is usually what your team needs from you. The cost of avoiding it shows up eventually, sometimes as a team member leaving who you did not see was about to leave.

If you recognized yourself in three or more of these patterns, you are not a bad manager. You are a manager in the standard middle stretch of learning the job. The good ones stop sabotaging themselves around year three. The ones who never figure it out stay stuck at the edge of effectiveness forever. The difference is not talent. It is whether you are willing to name the pattern out loud to yourself and pay the short-term discomfort of changing it.

Going through something as a new manager? Send us a letter. The best ones become the next letter.

Keep reading

• The First Time You Feel Like a Fraud as a Manager
• How to Run Your First 1-on-1 as a New Manager
• Five Ways New Managers Sabotage Their Own Teams
• Recommended Resources