The first weeks of managing a team for the first time are genuinely disorienting. You spent your career building credibility as someone who does the work, and now suddenly your job is to help other people do it. The skills that earned you the promotion — precision, speed, independent problem-solving — are exactly the ones most likely to get you into trouble in the new role. Almost every first-time manager makes the same handful of mistakes. The good news is that knowing about them in advance significantly changes the odds.

Mistake One: Doing Instead of Developing

The pull toward doing is intense when you are new to management. You know how to do the work. You are fast at it. Watching a team member struggle with something you could solve in twenty minutes is almost painful. So you swoop in, solve it, and move on. This feels helpful. It is not. Every time you step in to complete a task your team member should own, you prevent them from developing the competency that would eventually free you from having to step in. You also communicate — unintentionally — that you do not trust them to figure it out. Research from the Center for Creative Leadership found that the ability to transition from individual contributor to developer of others is the single most common sticking point for new managers. The managers who clear it fastest are the ones who learn to tolerate the discomfort of watching someone work through difficulty rather than resolving it for them. Ask questions instead of giving answers. "What have you tried?" and "What are your options?" do more long-term good than "Here, let me show you."

Mistake Two: Avoiding Difficult Conversations

New managers often have close relationships with their former peers. That history makes hard conversations feel like personal betrayals. So underperformance gets mentioned vaguely, feedback gets softened into incomprehensibility, and problems that should be addressed in week three are still festering in month six. Avoidance is not kindness. It is a transfer of discomfort — you feel better, your team member does not get the information they need to improve, and the problem grows. The earlier you give clear, specific feedback, the more correctable most situations are. Waiting does not make the conversation easier. It makes it harder, higher-stakes, and more likely to end badly for everyone.

Mistake Three: Managing Everyone the Same Way

Different people need different things from a manager. Some thrive with autonomy and check in naturally when they need support. Others need more frequent touchpoints and get anxious when they feel left alone with ambiguity. Some want detailed feedback on their work. Others find that level of scrutiny stifling. The mistake is assuming your preferred working style is everyone's preferred working style. In your first month, ask each team member directly: how do you like to receive feedback? What kind of support is most useful from a manager? What does micromanagement feel like to you? These conversations take thirty minutes and prevent months of friction.

Mistake Four: Disappearing Into Busyness

Management adds meetings. A lot of them. Many new managers fill their calendars with coordination work, then find they have no time to actually be present for their people. One-on-ones get rescheduled. Hallway (or Slack) check-ins stop happening. The team starts to feel like they have a manager in title only. One-on-ones are not status updates — that is what project boards are for. They are relationship investments. Protect them. A study from the Institute for Corporate Productivity found that managers who held regular one-on-ones with direct reports had teams with significantly higher engagement and lower turnover, even when controlling for team size and industry.

The Tangent Worth Taking

Here is something nobody tells you before your first management role: the feedback loop changes completely. As an individual contributor, your work produces visible results and someone evaluates them. As a manager, your results are your team's results, the feedback is indirect, and the cycle time is months rather than days. This is psychologically harder than it sounds. You will have weeks where you feel like you are doing everything wrong and have no data to confirm or deny it. Build your own feedback loop. Ask your team directly, regularly: what is working, what is not, what do I do that is useful, what do I do that gets in your way? This feels vulnerable. It is also the fastest way to learn the job.