You got the job. Now what? The first 90 days as a new engineering manager set the tone for everything after — and the most common mistake is trying to prove yourself too fast.
New managers often arrive with a list of changes. They reorganise the team in week two, rewrite the roadmap, or fix a process nobody asked them to fix. The team reads that as: this person did not bother to understand us first.
Days 1–30: Listen
Your first month is a listening tour. Meet every person on your team one-to-one, and ask the same few questions: what is working, what is frustrating, what would you change, what do you need from me? Meet your peers, your manager, and the people your team depends on. Map the team: who does what, who is stretched, who is quiet, where the knowledge lives.
Write it down. A simple team map — people, strengths, risks, open questions — is worth more than a dozen opinions. Run your first team meeting as an introduction, not a strategy session. Tell the team what you are doing in the first 30 days (listening), and when you will come back with a plan. Then keep that promise.
Days 31–60: Align
Now pick one to three levers — the changes that would help most — and run one small experiment. Not a reorganisation. One experiment: a better on-call rotation, a clearer definition of done, a weekly planning meeting that actually ends on time. Set working agreements with the team: how decisions get made, how feedback works, what "done" means.
This is also when difficult conversations start. Feedback given early, specifically, and kindly is far easier than feedback saved for a review. If someone is struggling, say so in week five, with a clear plan and support — not in month six, when it has become a performance case.
Days 61–90: Lead
By now you should be able to review the experiment honestly: did it help, what would you change, what is next? Set direction for the next quarter, write growth plans with each person, and clarify decision boundaries — what you decide, what the team decides, what goes up to your manager. Manage up, too: tell your manager what you learned, what you changed, and what you need from them.
Check in with yourself at day 30, 60 and 90. Are you listening enough? Are you delegating, or doing the work yourself because it is faster? Are the quiet people getting heard? A fifteen-minute weekly review — what went well, what did not, what to try next — keeps you honest.
The mistakes to avoid
Do not change everything at once. Do not keep the old manager's habits just to be liked. Do not avoid the hard conversation. Do not try to be the technical expert on everything — your job is now the team, not the code. And do not skip one-to-ones when things get busy; that is exactly when they matter most.
The first 90 days are not a test you pass or fail. They are the foundation for the next year. Listen first, align on a few things, then lead — in that order.
Want the templates? The First 90 Days as a New Engineering Manager Playbook ($15) has a listening-tour script, team map, 30-60-90 plan, 1:1 and team-health templates, and day 30/60/90 checklists: https://rainbowroadprep.gumroad.com/l/guqmxi — and the free interview sample is here: https://rainbowroadprep.gumroad.com/l/qiptza
Top comments (0)