10 first-time manager mistakes and how to avoid them in 2026

Nearly 60% of new managers underperform in their first two years, according to research from CEB (now Gartner). Recent Gallup data reinforces the urgency: manager engagement has dropped from 30% to 27% globally, and 70% of a team’s engagement is directly attributable to the manager. That’s because the skills that made managers great individual contributors don’t automatically translate into effective people management.

The transition from “doer” to “leader” is rarely smooth. You’re suddenly responsible for other people’s output, morale, and growth. And the leadership mistakes you make in those early months can ripple through your team for years. This guide breaks down 10 of the most common first time manager mistakes, from failing to set goals to avoiding difficult conversations, and gives you practical strategies to course-correct before they become patterns. Whether you’re weeks or months into your new role, these insights will help you lead with more confidence and less guesswork.

Key takeaways

• Set specific, measurable goals early: without defined objectives, your team will default to busywork over meaningful progress
• Delegate with intent, not reluctance: micromanaging erodes trust and limits your team’s ability to grow
• Build psychological safety from day one: trust isn’t earned by being liked, it’s built through consistency, transparency, and follow-through
• Create a repeatable system for managing work: using a platform like monday AI Workspace prevents things from slipping through the cracks as your team scales
• Shift your communication style: as a manager, your words carry more weight, so be intentional about context, frequency, and tone

Get started with monday.com

Not setting clear goals for your team

One of the fastest ways to lose your team’s momentum is to skip the goal-setting step entirely. As a first time manager, you might assume everyone already knows what they should be working on. After all, they were doing the work before you stepped into the role. But without explicit, shared goals, individual effort drifts. People optimize for their own priorities, and those priorities don’t always align with the team’s actual objectives.

The fix isn’t complicated, but it does require discipline. Start by establishing OKRs (Objectives and Key Results) or another lightweight goal framework that connects individual contributions to team-level outcomes. The point isn’t bureaucracy. It’s making sure every person on the team can answer: “What am I working toward this quarter, and how does it connect to the bigger picture?”

Here’s what strong goal-setting looks like in practice:

• Make goals visible and shared: post them where your team can reference them daily, not buried in a document nobody opens
• Tie individual work to team objectives: when someone finishes a project, they should understand how it moved the needle
• Review goals regularly: a quarterly check-in isn’t enough when priorities shift monthly or even weekly
• Involve your team in goal-setting: people commit to outcomes they helped define, not ones handed down from above

If you want to improve team performance, start here. Goals give your team a shared language for success and make it possible to measure progress instead of just guessing.

Failing to delegate and micromanaging

What is the biggest mistake first-time managers make? Ask any leadership coach and you’ll hear some version of the same answer: they can’t let go. The instinct to stay hands-on makes sense. You were promoted because you excelled at execution, and now you’re watching someone else do the work differently than you would. It feels risky. So you hover, review every detail, and jump in to “help” when you should be stepping back.

The problem is that micromanaging sends a signal, even when you don’t mean it to. It tells your team: “I don’t trust you to do this well.” Over time, that erodes initiative. People stop taking ownership because they know you’ll swoop in anyway. The result is a team that waits for instructions instead of solving problems independently. And you, as the manager, become a bottleneck.

Delegation isn’t about dumping work on people. It’s a skill that requires you to match the right work to the right person, provide enough context, and then get out of the way. Here’s how to start delegating with confidence:

• Start with outcomes, not instructions: tell your team what success looks like, then let them figure out the “how”
• Match assignments to strengths: an effective manager knows who thrives in which areas and assigns accordingly
• Set check-in points, not checkpoints: agree on milestones for updates instead of reviewing every step in real time
• Accept that “different” doesn’t mean “wrong”: your team members will approach work in their own way, and that’s a feature, not a flaw

If you find yourself redoing someone’s work after they’ve submitted it, that’s a sign your delegation process needs attention. Either the brief wasn’t specific enough, or you haven’t given yourself permission to let someone else own the outcome.

Skipping recognition and feedback

When you’re buried in your own adjustment to management, it’s easy to forget that your team needs something you might not have needed much as an individual contributor: recognition. And not the generic “great job, team” kind. Specific, timely acknowledgment of work well done is one of the most powerful (and free) management skills available to you. Skip it, and you’ll watch engagement drop faster than you’d expect. Gallup research shows only 22% of employees say they receive the right amount of recognition, and well-recognized employees are 45% less likely to leave within two years.

Feedback is the other side of the same coin. Many first-time managers avoid giving constructive feedback because it feels uncomfortable. You might worry about damaging relationships or demotivating people. But the absence of feedback is itself a message. When people don’t hear anything about their performance, they assume either you don’t notice or you don’t care. Neither assumption helps your team grow.

How do you build a rhythm of recognition and feedback that actually sticks? Start with your 1:1 meetings. These should be weekly, protected, and structured enough to include both praise and development. Here are a few principles to guide you:

• Be specific, not generic: “Your analysis on the Q3 pipeline report was thorough and helped the team reprioritize” beats “nice work” every time
• Give feedback close to the event: waiting until a quarterly review to address something that happened in week two is too late
• Balance recognition with growth areas: people want to know what they’re doing well and where they can improve
• Make recognition public when appropriate: calling out wins in team meetings or shared channels amplifies the impact

Investing in motivating your team through consistent recognition and honest feedback creates a culture where people want to do their best work, not because they’re afraid of consequences, but because they feel seen and valued.

Not building trust with your team

Trust is the foundation everything else sits on. Without it, feedback feels like criticism, delegation feels like dumping, and goals feel like mandates. Yet many first-time managers assume trust will develop naturally over time. It won’t. Trust is built through deliberate, consistent actions, especially in the first few months when your team is watching closely to figure out what kind of leader you’ll be.

What does this look like at a practical level? It starts with psychological safety, the belief that people can speak up, disagree, or admit mistakes without being penalized. Google’s Project Aristotle found that psychological safety was the single most important factor in high-performing teams. As a new manager, you set the tone for whether your team feels safe enough to be honest with you.

Here are three trust-building actions you can take immediately:

• Follow through on commitments: if you say you’ll do something, do it. Broken promises, even small ones, compound quickly
• Admit what you don’t know: pretending to have all the answers undermines credibility. Saying “I’m not sure, let me find out” builds it
• Protect your team’s time and focus: shield them from unnecessary meetings, last-minute requests, and organizational noise when you can

Strong team dynamics don’t happen by accident. They’re the result of a manager who prioritizes trust as a daily practice, not a one-time team-building event.

Avoiding difficult conversations

Are you putting off a conversation you know you need to have? You’re not alone. Avoiding difficult conversations is one of the most common and most damaging habits new managers develop. Whether it’s addressing underperformance, resolving a conflict between team members, or delivering unwelcome news, the instinct to avoid discomfort is natural. But avoidance doesn’t make the problem go away. It makes it bigger.

The cost of ducking hard conversations is real. Underperformance that goes unaddressed becomes the team’s new baseline. Unresolved tension between colleagues spreads. And when you finally do address the issue (because you’ll have to), the delay makes it harder to resolve. Your team also notices when you avoid conflict, and it signals that you’ll tolerate behavior that shouldn’t be tolerated.

So how do you handle conflict as a new manager? One proven approach is the SBI framework: Situation, Behavior, Impact. It structures difficult feedback in a way that’s factual rather than emotional:

• Situation: describe the specific context (“In yesterday’s client meeting…”)
• Behavior: state the observable action (“You interrupted the client twice during their presentation”)
• Impact: explain the effect (“The client seemed frustrated, and it made us look unprepared”)

This framework keeps the conversation grounded in facts rather than assumptions. It also makes it easier for the other person to hear the feedback without becoming defensive. Practice it in low-stakes situations first, and it’ll feel more natural when the stakes are higher.

Get started with monday.com

Communicating like an individual contributor

When you were an IC, your communication was mostly lateral. You talked to peers, shared updates in standups, and pinged people in Slack when you needed something. As a manager, that same communication style can work against you. Your words carry more weight now. Offhand comments land differently. Silence gets interpreted. And the way you share (or don’t share) information shapes how your team feels about their work.

The shift from IC to manager communication is about moving from “what I need” to “what my team needs to know.” That means proactively sharing context, explaining the “why” behind decisions, and adjusting your style based on who you’re talking to. A senior team member might want autonomy and minimal check-ins. A newer team member might need more frequent guidance and reassurance.

Here are a few communication shifts that make an immediate difference:

• Lead with context: before assigning work, explain why it matters and how it connects to the team’s objectives
• Repeat important messages: people absorb information at different speeds, so say it once in the meeting, follow up in writing, and check for understanding
• Listen more than you talk: the most effective leadership traits include the ability to hear what’s not being said

Communication is the one skill that amplifies every other skill you develop as a manager. Invest in it early and consistently.

Breaking down silos across your team

Silos form when teams or individuals operate in isolation, hoarding information (intentionally or not) and duplicating effort. In a remote or hybrid environment, silos build even faster because the informal hallway conversations that used to bridge gaps simply don’t happen. As a first-time manager, you might not even realize silos are forming until a project goes sideways because two people were working on the same thing without knowing it.

What makes silos so dangerous? They create blind spots. When information doesn’t flow freely, decisions get made with incomplete data. Work gets duplicated. And your team spends more time figuring out who knows what than actually making progress.

Breaking down silos requires intentional workflow management and communication habits:

• Create shared visibility: make sure everyone on the team can see what others are working on, not just their own assignments
• Cross-pollinate in meetings: regularly invite team members to share updates outside their direct area, especially in remote settings
• Document decisions and context: when decisions happen in DMs or one-off calls, they’re invisible to everyone else. Move them into shared spaces
• Use async updates strategically: weekly written updates or shared dashboards help remote and hybrid teams stay aligned without adding more meetings

Silos aren’t just an organizational problem. They’re a management problem. And solving them starts with how you structure information flow across your team.

Navigating the shift from peer to manager

One day you’re grabbing coffee with your teammates. The next day you’re their boss. This transition is one of the most emotionally complex challenges a first-time manager faces, and there’s no playbook that makes it completely smooth. Relationships that were built on equal footing now have a power dynamic layered on top of them. People who used to vent to you about management are now wondering whether they can still do that.

The biggest mistake here is trying to pretend nothing has changed. Something has changed. Acknowledging it openly is the first step. You don’t have to become a different person, but you do need to adjust how you show up. That means being thoughtful about boundaries without being cold, and being approachable without being a pushover.

A few practical guidelines for managing former peers:

• Have individual conversations early: meet with each team member one-on-one to acknowledge the shift and ask how they’d like to work together going forward
• Be consistent with everyone: playing favorites (or appearing to) will destroy credibility faster than almost anything else
• Don’t overcorrect: some new managers become overly formal or distant to prove they’re “professional.” Your team needs warmth and directness, not corporate armor

The peer-to-manager transition gets easier with time, but only if you handle the early days with honesty and intention.

Running your team without a system

Have you ever lost track of a project because it lived in someone’s head instead of a shared space? That’s what happens when a team runs without a system. As an individual contributor, you could get away with personal to-do lists and mental notes. As a manager, that approach collapses under the weight of multiple people, projects, and deadlines happening simultaneously.

Running your team without a centralized system means you’re constantly playing catch-up. You don’t know what’s on track, what’s at risk, or where the bottlenecks are until someone flags a problem. And by that point, you’re in reactive mode instead of proactive mode.

A platform like monday AI Workspace gives first-time managers the visibility they need without adding complexity. You can track who’s working on what, set up automations for repetitive handoffs, and use dashboards to spot issues before they escalate. The key is to choose a system that your team will actually use.

Here’s what to look for in a work management system:

• Centralized project tracking: one place where every project, deadline, and owner is visible to the whole team
• Automations for routine work: status updates, notifications, and handoffs should happen without manual effort
• Customizable views: different team members need different perspectives on the same data, from timelines to Kanban boards to workload views
• Easy adoption: if the platform requires weeks of training, your team won’t use it

The right system doesn’t just organize work. It gives you the confidence to manage proactively instead of reactively.

Managing top-down instead of enabling your team

First-time managers sometimes default to a top-down management style because it feels like the most straightforward way to maintain control. You decide what needs to happen, assign it, and follow up. Simple, right? Except this approach has a ceiling. It works when the work is routine and the stakes are low, but it breaks down when you need creativity, initiative, or resilience from your team.

What’s the alternative? Enabling management, where your role shifts from “decision-maker” to “decision-enabler.” Instead of telling your team exactly what to do, you provide the context, resources, and support they need to make strong decisions on their own. This doesn’t mean abdicating responsibility. It means investing in your team’s capability so you don’t become the single point of failure.

Here are a few ways to move from directive to enabling leadership:

• Ask questions before giving answers: “What would you recommend?” is more powerful than “Here’s what I want you to do”
• Share the reasoning behind decisions: when your team understands your thought process, they can make better decisions independently
• Invest in developing future managers: the best managers build people who can eventually step into leadership roles themselves
• Create space for experimentation: let people try new approaches, even if they occasionally fail. Learning from failure is how teams get stronger

Enabling your team isn’t a sign of weakness. It’s the hallmark of a manager who’s thinking beyond the current quarter and building something sustainable.

How monday AI Workspace helps first-time managers stay organized

Stepping into management means juggling more moving parts than you’ve ever handled before. And doing it with spreadsheets, sticky notes, or a dozen disconnected apps makes the job harder than it needs to be. monday AI Workspace gives first-time managers a single place to plan, track, and manage their team’s work, without the steep learning curve that comes with enterprise software.

Here’s what makes it particularly useful for new managers:

• Dashboards for instant visibility: see project status, team workload, and upcoming deadlines in one view. No more chasing people for updates or digging through email threads
• Automations that reduce busywork: set up rules like “when a status changes to Done, notify the project lead” so routine updates happen without manual effort
• Workload widget for balanced assignments: visualize how work is distributed across your team and rebalance before anyone gets overwhelmed
• monday sidekick for faster decisions: use AI-powered assistance to generate summaries, draft updates, and surface insights from your data so you spend less time on admin and more time leading

The goal isn’t to add another platform to your stack. It’s to replace the scattered, manual approach that most first-time managers default to with something that actually scales. When you can see your team’s work at a glance, you make better decisions, catch problems earlier, and spend your energy on the parts of management that matter most: coaching, strategy, and building a high-performing team.

Setting yourself up for success as a new manager

Every first time manager makes mistakes. That’s part of the growth. The difference between managers who stall and managers who thrive is whether they learn from those mistakes and build systems to prevent them from recurring. The 10 mistakes in this guide aren’t a checklist of failures to avoid forever. They’re a map of the territory you’ll navigate in your first year and beyond.

What matters most is your willingness to keep adjusting. Ask for feedback from your team. Invest in your own development. Build structures that support your team’s autonomy instead of your own control. And when things don’t go perfectly, treat it as data, not as a verdict on your leadership potential.

Get started with monday.com