The Mistakes First-Time Managers Make (And How to Avoid Them) [2026]

I became a manager for the first time at 30. I was promoted because I was a strong individual contributor, which turned out to be nearly irrelevant preparation for management. Here is what I got wrong and what eventually worked.

The Transition That Nobody Explains

Individual contributors create value directly through their own work. Managers create value indirectly through enabling, developing, and removing obstacles for their team. The shift from "doing" to "enabling others to do" is genuinely psychologically difficult for most people who've built their identity around technical competence. The temptation to solve problems yourself (faster, better, the way you'd do it) rather than developing the person who should solve them is one of the core manager failure modes, and it's almost universal in the first year.

One-on-Ones Done Right

Weekly one-on-ones with each report are probably the highest-leverage management activity available. Most new managers run them as status updates — which is a waste of the format. One-on-ones should be primarily about the person: what's working, what's frustrating, what they're trying to develop, what obstacles you can remove. Status is better communicated in writing. The things you learn in one-on-ones done this way will change how you manage the person and often reveal team dynamics that aren't visible in group settings.

Feedback Is a Skill

Specific, behavioral, proximate feedback (immediately or very soon after the behavior) is the format that produces change. "You could be more proactive" is not actionable. "In the meeting yesterday, you had an idea that you didn't share until I asked directly — I'd like you to offer those unprompted going forward" is. Most new managers either avoid hard feedback (too uncomfortable) or deliver it in ways that trigger defensiveness. The SBI framework (Situation, Behavior, Impact) is a reasonable scaffold for learning to deliver feedback specifically.

What I Got Wrong

I avoided difficult performance conversations too long, which was unfair to the person who deserved honest feedback earlier. I solved problems instead of developing the people who should solve them. I conflated "managing up" (managing your relationship with your own manager) with success when the team was actually struggling. These are common enough that I feel okay sharing them as representative rather than exceptional failures.

Real talk: Being a good manager is a different skill set than being a good individual contributor. Treat it as seriously as any other major skill you've developed.