First-Time Manager Mistakes (And How To Avoid The Big One)

Reading time: 6 minutes

You recently got promoted. Congratulations.

You’re now responsible for other people’s performance, not just your own. You’ve never done this before. Nobody really trained you. And everyone’s watching to see if you can handle it.

No pressure. No pressure at all. Here’s what you need to know about first-time manager mistakes – and the one mistake that matters most.

Keep in mind, most advice focuses on tactical first-time manager mistakes like micromanaging, avoiding hard conversations, trying to be everyone’s friend, not delegating enough.

That’s all fine. But there’s one mistake that matters more than all of those combined – and almost nobody talks about it.

The big mistake: Building a siloed environment from day one.

Let me explain.

—

The Mistake You Don’t Know You’re Making

You got promoted because you were exceptional at your job. You produced results. You solved problems. You executed well.

Now you’re a manager. And, unconsciously, you start building the same environment you built as an exceptional worker. After all, it worked then, it should work now.

So you create an environment where things work the way YOU work.

  • Your standards become the standards
  • Your methods become the methods
  • Your judgment becomes the reference point
  • Your involvement becomes required for quality

It feels natural because you’re just maintaining the same type of exceptional behavior that got you promoted.

But here’s what’s actually happening:

You’re building a Performance Silo™ – a team that can only operate at the level YOU operate, using the approaches YOU use, requiring YOUR involvement to succeed.

When I look into my crystal ball, I see that six months into your job, you’re going to start getting frustrated. Your team isn’t performing at the level you need and they’re not taking initiative. They keep asking for your input and can’t seem to figure things out on their own.

You think the problem is them.

The problem is the most common of all the first-time manager mistakes: it’s the environment you built.

You’ve built a Performance Silo™.

And if you don’t address this early, it’s going to get exponentially harder to fix.

—

The Common First-Time Manager Mistakes (That Everyone Talks About)

Let’s get these out of the way first:

Mistake 1: Doing Instead of Managing

You’re used to doing the work yourself. It’s faster. It’s easier. You know you’ll do it the way you need it.

So you keep doing it, even though you’re now supposed to be managing people who do it.

Why this happens: Doing feels productive to you. It’s part of your identity. Managing still feels slightly uncomfortable.

The easiest fix: Block time for manager work (1-on-1s, planning, development). Stop doing the tasks that individual contributors should be doing.

Mistake 2: Avoiding Hard Conversations

This is one of the biggest first-time manager mistakes.

Inevitably someone is going to underperform. Or miss deadlines. Or behave poorly in some way or another.

You don’t want to be thought of as the type of boss who’s always critical. Maybe you want to make sure everybody likes you. So you let it slide. Maybe you drop some hints and convince yourself that they understood what you meant as you silently hope it all gets better.

Why this happens: Difficult conversations feel like confrontation. Maybe you want to be liked. Maybe you have a fear of conflict. There’s a reason you’re avoiding them or justifying why the conversation can always be had tomorrow.

The tough truth: Difficult conversations don’t have to be confrontational. In fact, they shouldn’t be, because giving direct feedback is actually a gift to others. It’s a way of jointly solving a problem. Avoiding the conversation is more like cruelty because 1) the person doesn’t know they’re failing and 2) the team sees that you tolerate poor performance.

Remember, a team culture is defined by the worst behavior a leader is willing to tolerate.

Mistake 3: Trying to Be Everyone’s Friend

Maybe you were peers with these people last week, and now you’re their manager. Or you just stepped in from somewhere else, and you feel like you have to prove that you can be part of the team. You don’t want things to feel weird.

So you try to maintain friendly relationships. You stay casual, as if you are all equals.

Why this happens: The transition from peer to manager – or individual contributor to manager – is uncomfortable. It’s a common mistake amongst first-time managers to try to be “one of the gang.”

The advice: You can be friendly to your team members without being friends. Be warm, be human, but it’s important to maintain boundaries. You’re still their boss and have to build the respect by understanding when and where boundaries need to exist.

Mistake 4: Micromanaging Because You’re Nervous

Everything might feel like it’s high-stakes. I know, I’ve been there.

All of the sudden you’re responsible for results that you don’t directly produce. So you check everybody’s work because it reflects on you. You have to approve everything because you are the one who knows best. You’re always involved.

Why this happens: This often comes from a lack of confidence in your ability to manage, not a lack of confidence in your team.

The path to success: Give clarity to your teams on the expected outcomes for each project and the standards you have. Then trust them to get it done – even though that may feel uncomfortable at first. In the end, you want to check the results, not their methods.

(As a side note, this isn’t just one of the more common first-time manager mistakes, it’s actually a mistake that happens with seasoned mid-level managers as well. This is all a reflection of the Performance Silo™.)

Mistake 5: Not Delegating Enough

You keep the important work but you delegate the tasks nobody wants to do. You justify this by telling yourself you’re being generous by not overwhelming them. How kind of you.

Why this happens: You’re still thinking like an individual contributor. Just like when you were the exceptional worker, you equate important work as the work that you need to do.

The reality: Your job as a leader is to develop your team, not to protect them. The most important work you need to delegate, is the work that allows them to grow and flourish.

—

All of those are real first-time manager mistakes. They all matter.

But none of them are THE mistake.

—

The Big Mistake: Building a Silo From Day One

Here are the things that most first-time managers do without even realizing it:

You Establish Yourself as the Standard

This is one of the most common first-time manager mistakes — and the hardest to see.

What this looks like:

  • You work longer hours than everyone else
  • You respond to messages faster
  • You have higher quality output
  • You solve problems more quickly
  • You’re always available, always engaged, always on

Why you do it:

You want to lead by example. So you try to model the behaviors you want to see as a means of proving you deserve the promotion.

What’s actually happening:

You’re letting people know that “What I do is the standard. It’s what I expect from you, so if you want to succeed, you need to try to match my pace and success.”

The problem:

You’re an outlier. You’re the one that got promoted – not them. That’s because of your productivity, your work style and your capabilities. Most people can’t operate like you — and they don’t need to.

But they’ll try – because you’ve told them they need to. And you know what is going to happen? They’ll either burn out or feel completely inadequate for not being able to match your pace.

The pattern you’re setting: The environment only works if everyone operates like you. See? It’s the Performance Silo™.

You Build Everything Around Your Involvement

Sometimes first-time manager mistakes feel like they’re just about being responsible. Building everything around your involvement is one of them. So pay attention.

What this looks like:

  • Major decisions come to you for approval
  • Important client relationships run through you
  • Quality control requires you to review
  • Strategic thinking is your responsibility
  • Problem-solving escalates to you

Why you do it:

You’re good at these things. Besides, you want to ensure quality. After all, this is just about being responsible, right?

What’s actually happening:

You’re architecting a system where you’re the center. When everything routes through you, any progress requires your involvement.

The problem:

You’ve just built organizational dependency into the foundation of your team culture. Six months from now, you’ll be drowning in work that “only you can do” — not because it actually requires you to do it, but because the environment you built requires you to be at at the center of it. Welcome to your very own Performance Silo™.

The pattern you’re setting: Nothing important happens without you.

You “Improve” Everything Your Team Produces

Like most first-time manager mistakes, this one comes from good intentions but creates bad outcomes.

What this looks like:

They complete their work and bring it to you to review. You always seem to see ways to make it better – so you make it better.

The work becomes higher in quality and, besides, they get to learn from seeing your edits. Everyone wins, right?

What’s actually happening:

You’re letting your team know that they’ll never be good enough for you. Everything they do is going to require your involvement in order to reach the quality you demand.

The problem:

They stop aiming for excellence. Why should they even try to be exceptional when you’re going to change it all anyway? So they slide into mediocrity and let you take the burden of being exceptional.

Et voila, your “high standards” just created a ceiling on their abilities to grow professionally. Well done.

The pattern you’re setting: Your judgment is the only judgement that matters. Theirs simply isn’t good enough.

You Solve Every Problem They Bring You

Of all the first-time manager mistakes, this might be the easiest to fix once you see it.

What this looks like:

Someone comes to you with a challenge. You listen. You see the solution. Then you tell them what to do.

Efficient. Helpful. Good management, right?

What’s actually happening:

You’re training them to not fully think through problems. After all, if they bring them to you without a solution in mind, you’ll solve it for them.

The problem:

In six months, they bring you every problem with little to no thought on solutions. You say you want problem-solvers, maybe you’ve even called it one of your core values, but you’ve created the environment that punishes it.

The pattern you’re setting: Problems are yours to solve and only yours. Their main job is to identify problems and give them to you to solve.

—

You know what, maybe you should learn a bit more about pattern recognition in leadership.

—

Why This Mistake Matters More Than the Others

All the common mistakes are about behaviors you can change:

  • Stop doing and start managing
  • Have hard conversations
  • Set appropriate boundaries
  • Stop micromanaging
  • Delegate more

Those common first-time manager mistakes are primarily tactical.

The big mistake is architectural.

Whether you recognize it or not, you’re building your team’s environment. The environment is comprised of the system of how work gets done, how decisions get made, how success gets defined, and how people interact with each other – and with you.

And if you build a siloed environment from day one, if you build the Performance Silo™, everything else breaks:

  • Delegation doesn’t work (because the environment requires your involvement)
  • Initiative doesn’t happen (because the environment rewards dependence)
  • Professional development doesn’t occur (because the environment has no space for their capabilities to grow)
  • Quality stays dependent on you (because the environment makes you the standard for excellence)

You can fix individual behaviors but you just can’t framework your way out of an environment problem.

(This is also why leadership coaching for newly promoted VPs focuses on environmental architecture.)

—

How to Avoid Building a Silo From Day One

Avoiding first-time manager mistakes starts with understanding the difference between tactics and architecture.

Architect for Multiple Ways of Operating

Don’t establish yourself as the standard.

Yes, you need to model good behaviors. But you also need to explicitly make space for different types of approaches:

“What ideas do you have for solving this?” “What do you think the best way is for us to approach this?” “If you see a good path that makes sense and will get to our expected outcome, take it.”

What this does: Creates space for their methods of doing things, not just yours.

Design for Independence, Not Dependence

Don’t build systems around your involvement.

When setting up processes, ask: “Am I doing this because I can do it, or because I should do it?”

Decision-making:

  • What decisions can they make without checking with you?
  • What requires your input vs. your approval?
  • How do you want to be involved vs. how do you need to be involved?

What this does: Creates conditions where progress can happen with or without you.

Develop Judgment, Not Dependence on Your Judgment

Don’t solve every problem they bring you. In fact, the less problems you solve the better.

Your job is to help them learn how to solve problems on their own.

Next time someone brings you a challenge, don’t give them an answer. Instead, start with questions.

“What do you think we should do?” “What would you do if I weren’t available?” “Have you thought about any other ideas?”

Then either approve their recommended approach or talk with them about if their idea will achieve the expected outcome.

What this does: Develops their problem-solving capability instead of their dependence on yours.

Create Space for Their Excellence

Don’t improve everything they produce.

Agree on clear standards, then let them meet those standards their own way.

When reviewing their work, here’s what you should consider:

  • Does this meet the standard we agreed on? (If yes, ship it – even if you’d have done it differently)
  • Does this not meet the standard? (If no, ask them to revise it – do not revise it for them)

What this does: Develops their judgment about quality instead of having a dependence on yours.

Build a Greenhouse, Not a Silo

From day one, think about architecture:

  • How will decisions get made when I’m not here?
  • What am I doing that creates dependence vs. capability?
  • Am I building an environment with room for one way of operating, or multiple ways?
  • What does success look like when it doesn’t look like me?

What this does: Creates conditions where everyone’s talents can grow, not just your talent for maintaining control.

For more on building greenhouse environments, see Leadership Coaching: The Complete Guide.

—

The First 90 Days: What to Actually Focus On

Your first 90 days determine whether you fall into the standard first-time manager mistakes or build something sustainable. In fact, studies on management transitions confirm that the first 90 days set lasting patterns.

Weeks 1-4: Understand Before You Architect

Don’t change everything immediately. Learn how things actually work.

  • What patterns already exist?
  • What’s working that you don’t want to break?
  • What’s broken that everyone’s working around?
  • What do people need from you vs. what do they think they need from you?

Weeks 5-8: Architect the Environment

Now you can design.

Not “here’s how I do things” – but “here’s the environment where we’ll all operate.”

  • How will decisions get made?
  • What does good work look like? (Outcomes are more important than your methods)
  • How do we work together? (Expectations, communication, feedback)
  • What’s yours to own vs. theirs to own?

Weeks 9-12: Test and Refine

Apply your architecture in real situations.

  • Give someone a decision that doesn’t actually need you
  • Let work go out that you’d have improved on (but that met the agreed upon standard)
  • Resist solving a problem they brought you
  • Watch what happens

Then refine based on reality, not theory.

—

The Questions to Ask Yourself Every Month

Am I building my teams self-sufficient abilities or their dependence on me?

  • Are they developing or just executing?
  • Can things move without me?
  • Am I becoming more essential or more optional?

What does my calendar reveal?

  • How much time am I doing vs. enabling?
  • What meetings don’t actually need me?
  • Where am I the bottleneck?

What patterns am I setting?

  • What behaviors am I unconsciously rewarding?
  • What does success look like in practice? (Is it just matching me?)
  • What happens when someone does things differently than I would?

Is this sustainable?

  • Can I maintain this pace for years?
  • What happens when this team grows to 15 people? 30 people?
  • Am I building something that requires me, or something that scales?

Answer these honestly – and regularly. It will keep you from accidentally building the Performance Silo™.

—

The Green Flags You’re Doing It Right

You’re becoming less involved, not more.

The team is making more decisions without you. Solving more problems without you. Producing quality work without your input.

This isn’t because they’re taking over. It’s because the environment you architected has room for them to operate.

Your team disagrees with you regularly.

Not disrespectfully – but openly. They have opinions and feel comfortable pushing back. They realize that they can see things you don’t see.

This means you’ve built an environment where their thinking matters, not just their execution of your thinking.

Different people succeed in different ways.

Not everyone operates like you, and that’s fine. Multiple approaches can coexist. Multiple standards of quality can coexist.

If you’ve got that, then you’ve architected a greenhouse, not a silo.

You’re developing as a manager, not just as an expert.

You’re learning to lead through others. You can purposely architect environments and see patterns. You understand how to create the conditions where your teams talents can flourish.

You’re not just doing your old job with more people reporting to you. You’re no longer the exceptional worker, you’ve become the successful leader.

Most first-time manager mistakes are fixable. But the Performance Silo™ mistake? That’s exponentially harder to fix later.

It’s important to understand that solving first-time manager mistakes means distinguishing tactical problems from architectural ones.

—

The Bottom Line

The common first-time manager mistakes are real. You need to avoid them.

But the big mistake – the one that makes everything else harder – is building a siloed environment from day one.

An environment where:

  • Everything depends on you
  • Only one way of operating works
  • The teams overall ability stays limited to yours
  • Growth requires your involvement

If you can avoid this mistake, everything else gets easier.

So build a greenhouse from the start. Create the conditions where everyone can excel and architect for independence, not dependence.

That’s how you become a manager worth following.

—

Ready to Architect a Greenhouse From Day One?

Option 1: Schedule a Consultation
One call. We’ll set up the right environment from the start.

Schedule Here →

Option 2: Join the Free Leadership Diagnostic Workshop
Uncover the patterns that are holding you back.

Secure Your Spot →

Option 3: Start With My Newsletter
Join 14,000+ leaders getting one “oh shit, that’s me” moment every Monday.

Try It Free →

—

Related Articles

—

Jeff Matlow spots patterns for a living. Specifically, the ones keeping your team dependent on you—and the siloed environment those patterns create. Then he shows you how to rearchitect the whole thing into a greenhouse environment where people can actually excel. 3x entrepreneur (all companies acquired). 25+ years working with leaders at L’Oreal, Disney, Nestlé, Porsche, Citi and hundreds of high-growth companies. Think Ted Lasso meets Brené Brown meets a Navy SEAL.