What is the biggest mistake new engineering managers make?

Keeping the IC hero role — coding the hardest work, skipping people time, and measuring success by personal output instead of team outcomes.

How do I stop micromanaging as an EM?

Delegate outcomes with clear definition of done, set check-in points, and resist rewriting their approach unless quality or risk demands it.

Is saying yes to leadership always bad?

Constant yes without capacity math burns the team. Push back with options: what slips, what you need, or what you’ll cut to say yes.

10 Common Engineering Manager Mistakes (And How to Avoid Them)

Most engineering manager mistakes aren’t character flaws — they’re IC habits wearing a new title. Here are the 10 I see (and have made), with the fix you can use this week.

Most of these mistakes shrink when you practice solid delegation tips for engineering managers.

1. Micromanaging every detail

Fix: Delegate the outcome and the “done” criteria. Schedule a midpoint check. Only jump into the how when risk is high — then coach, don’t hijack.

2. Failing to communicate priorities

Fix: Write the top 3 weekly priorities somewhere the team can see. If everything is P0, nothing is. Say what you’re explicitly not doing.

3. Ignoring team feedback

Fix: Ask specific reverse-feedback questions in 1:1s. Thank them. Change one visible thing. Silence after feedback teaches them to stop offering it.

4. Overloading the team because you won’t say no

Fix: Protect capacity out loud. “We can take X if Y slips — which do you want?” Bring numbers, not vibes.

5. Neglecting 1:1s when things get busy

Fix: Busy seasons are when you need 1:1s most. Shorten to 25 minutes before you cancel. Status never belongs here anyway.

6. Not delegating the work that grows people

Fix: Give stretch ownership with air cover — design reviews, stakeholder updates, incident leads. Delegation without sponsorship is just dumping.

7. Being inaccessible (always “in meetings”)

Fix: Hold office hours or a daily “interruptible” block. If every question requires a calendar invite, you’re the bottleneck.

8. Focusing only on technical skills in hiring and promos

Fix: Score collaboration, communication, and ownership alongside code. The strongest IC is often a weak manager — and a weak teammate can sink a squad.

9. Avoiding hard performance conversations

Fix: Document early, be direct, set a timeline. Hoping it improves is how you end up with a surprise PIP and a team that lost respect for you.

10. Failing to recognize good work

Fix: Specific praise within a week of the win — in public when it helps, in private when it’s personal. Recognition is free leverage. Use it.

If you’re new, pair this with the 9 things every new EM should know — prevention beats cleanup.