The first 90 days as a new engineering manager

The first ninety days as an engineering manager are strange. The skills that got you the job — writing great code, shipping fast, being the person with the answers — are no longer the job. Your output is now your team’s output, your influence is mostly indirect, and the most valuable thing you can do in week one is often to resist doing anything at all.

Here’s a way to think about the first three months that keeps you from the classic new-manager mistakes.

Days 1–30: listen and learn

Your only real job in the first month is to build context. You cannot lead a team you don’t understand, and you understand a team by listening to it, not by reorganising it.

• Meet everyone, properly. A real 1:1 with each person in the first week or two. Ask how they like to work, what’s going well, what frustrates them, what they’d change. Mostly listen. If you want a starting set, our 50 one-on-one questions are built for exactly this.
• Learn the system, not just the people. How does work actually flow? Where does it get stuck? What’s everyone quietly working around?
• Change as little as possible. The urge to prove yourself by shipping a reorg is strong. Resist it. You don’t yet know which of the things that look broken are load-bearing.

Days 30–60: find the real problems

By the second month you’ve heard the same issues enough times to tell the signal from the noise. Now you start forming a point of view.

• Look for patterns across your 1:1s. When three people independently mention the same blocker, that’s not three complaints — it’s one real problem.
• Establish your cadences. A reliable 1:1 rhythm, a way you run team meetings, how you give feedback. Predictability is a gift to a team that just got a new manager.
• Find your first win. One visible, genuinely useful thing you can fix — a painful process, a missing piece of clarity — that signals you were listening.

Days 60–90: start to act

With real context and some trust banked, you can begin to lead more deliberately.

• Address the patterns you found. Now is when a thoughtful change lands, because it’s clearly a response to what the team told you, not a flag-plant.
• Set direction. People want to know where things are going. You don’t need a grand vision — a clear sense of what matters over the next quarter is enough.
• Check your read. Ask people how the first months have felt. You’ll learn where your perception and theirs diverge — which is where the surprises live.

The traps to avoid

• Staying an IC. The most common failure mode. You retreat to the code because it’s comfortable and measurable, and your team goes unmanaged. Let go of being the best engineer in the room.
• Big changes too early. Reorganising before you understand the org burns trust you’ll wish you had later.
• Neglecting up and across. Managing your own manager and your peers isn’t optional — a lot of your team’s success depends on context and cover you can only get sideways and upward.
• Letting context scatter. You’re taking in an enormous amount in these months. The details you don’t capture, you lose.

A simple 30/60/90 checklist

If you want something concrete to anchor the three months, this is a defensible default:

• By day 30: a real 1:1 held with every report; a working understanding of how work flows and where it jams; relationships started with your manager and key peers; and — deliberately — almost nothing changed.
• By day 60: your 1:1 and team-meeting cadences established; the recurring problems identified from patterns across your conversations; one visible, useful early win delivered.
• By day 90: a thoughtful response to the biggest pattern you found; a clear sense of direction for the next quarter shared with the team; and a check on your own read, by asking people how the first months have felt.

Treat it as scaffolding, not a scorecard. Some teams need you to move faster — a team in genuine crisis can’t wait thirty days for you to listen. But absent a fire, listening first almost always beats acting first.

Don’t forget to manage upward

New managers pour all their attention downward, onto the team, and neglect the relationship that quietly determines much of their success: the one with their own manager. Use your early 1:1s up the chain to get the context only they have. A few questions worth asking:

• What does success look like for me and this team over the next few months?
• What problems are you hoping I’ll solve that might not be obvious yet?
• How do you like to be kept informed — and how often?
• Is there anything about this team’s history I should understand?

Getting this relationship right early pays off all year: it’s how you win the air cover, context and trust your team needs you to provide. A manager who’s aligned upward can shield their team from the churn above them; one who isn’t becomes a transmission line for it.

The same goes sideways. Your peers — the other managers, the leads in adjacent teams, the people in product and design you’ll depend on — are worth a deliberate introduction in the first month too. Much of what makes a team effective is the goodwill and context that lives in those lateral relationships, and they’re far easier to build before you need something than in the middle of asking for it.

Building context that doesn’t leak away

The hardest part of the first 90 days is simply holding it all. You’re absorbing dozens of conversations, impressions and half-noticed details about new people, and the human memory is a sieve. The manager who can recall, in month three, what someone told them in week one has a real advantage.

That’s why a habit of capturing as you go matters so much early on. CoManager’s observations let you jot a win, a blocker or a mood in two taps as you notice it, and CoManager quietly turns those notes into team health scores, early-warning signals and prepped 1:1s — so the context you build in your first ninety days compounds instead of evaporating. The work of the first three months is learning your team. The least you can do is make sure you remember what you learned.