Engineer to manager

Your first 90 days as an engineering manager

5 min read Last updated
An engineering manager at his laptop thinks ahead, with an hourglass on the desk
In short

In your first 90 days as an engineering manager, listen before you change anything.

What does an engineering manager do?

The first 90 days decide whether your team trusts you. Change too much too early and people dig in. Change nothing and the problems you inherited become yours.

An engineering manager leads a team of engineers to deliver work safely, on time and to standard, and develops the people who do it. The technical work still matters, but your main output is now your team’s output. The same holds if you lead consultants, analysts or any other technical team.

  • People: hire, onboard, coach and develop your team; hold one-to-ones; give feedback; handle performance and conflict
  • Delivery: plan work and resources, set priorities, remove blockers, and keep projects on time and on budget
  • Quality and safety: set standards, review critical work, and keep people physically and psychologically safe
  • Stakeholders: report up, work across teams, and manage customers and contractors
  • Improvement: fix how the team works as well as what it produces

New managers often underestimate the first item. It takes more time than you expect, and it decides whether the rest works.

Days 1 to 30: listen and learn

Your goal: trust and a clear picture of the team. Change very little.

  • Meet every person on your team one to one. Ask: what works well, what gets in your way, and what do you need from me?
  • Meet your own manager. Ask how they will measure your success at 90 days and at 12 months.
  • Learn the current projects, deadlines, risks and commitments your team has made.
  • Meet the people your team depends on: other team leads, key customers, site managers, procurement.
  • Find out who makes decisions today, and how.
  • Note the problems you hear more than once. Don’t fix them yet.
  • Decide how much technical work you will keep, and tell your manager.

Leave alone: big changes to process, structure or tools. You don’t know enough yet, and changing them now costs trust.

Days 31 to 60: set the rhythm

Your goal: a team that knows what good looks like, and a routine that keeps you close to your people.

  • Set a regular rhythm of one-to-ones (weekly or fortnightly) and team meetings. Protect them.
  • Make expectations clear: what good work looks like, who decides what, and how to raise problems.
  • Share what you heard in your first month, and the two or three things you plan to work on.
  • Start delegating real work: whole pieces, with a clear outcome and agreed check-ins.
  • Give your first specific feedback, positive and corrective, within a day of what you saw.
  • Ask your team for feedback on how you’re doing.

Leave alone: solving every problem people bring you. Ask “what do you think we should do?” first.

Days 61 to 90: deliver and build trust

Your goal: one visible win, and a team that starts to run without you in every decision.

  • Deliver one quick win the team cares about, such as a removed blocker or a fixed process.
  • Have the conversation you’ve been putting off. Do it in private, early and kindly.
  • Handle your first real disagreement in the open: separate facts from preferences, and agree how the team will decide.
  • Check how much of the work still runs through you. Hand over one more piece.
  • Review your first 90 days with your manager against the measures you agreed.
  • Pick one leadership skill to work on next, and find support for it: a program, a mentor or a coach.

Leave alone: proving you’re still the best engineer in the room.

Where to get support after day 90

A checklist gives you the order. Changing how you lead under pressure takes practice and someone who can show you what you can’t see in yourself.

From Accidental to Authentic is our program for people in their first one to three years of leading. It runs on the Authenticity Cycle: we reveal how you lead in a live simulation, explain why with an assessment, then develop new habits on your own work. More than 100 leaders in one electrical engineering business rated our Coaching for Performance program NPS 75, with no detractors.

Leading on your own, without a company program? The Practice is our peer group for leaders. We plan the first intake for late January 2027 in APAC, the UK and Europe. Register your interest now.

For the bigger picture, read From engineer to manager: the complete guide.

First 90 days questions

What should a new engineering manager do first?

Meet every person on your team one to one, and meet your own manager to agree how they will measure your success. Listen and learn before you change anything.

What is a 30-60-90 day plan for an engineering manager?

It splits your first three months into stages. Days 1 to 30: listen and learn. Days 31 to 60: set a rhythm of one-to-ones and clear expectations. Days 61 to 90: delegate real work, give feedback and deliver one visible win.

How much technical work should a new engineering manager keep?

Enough to stay credible and close to the work, especially in a small team. Hand over anything your team should be learning, and anything that stops you making time for your people.

What are the main responsibilities of an engineering manager?

Leading and developing people, delivering work on time and to standard, keeping quality and safety high, managing stakeholders, and improving how the team works.

Ready to lead as yourself?

Tell us where your leaders are stuck. We'll tell you honestly whether we can help.