New-Manager Onboarding Playbook — First 90 Days as an EM

The first 90 days as an engineering manager at a new company determine the next two years. Most new EMs either over-index on listening and ship nothing, or over-index on shipping and break trust with their team before they've earned any. The 2026 playbook is neither: it's a disciplined sequencing of listening, decision-making, and shipping that produces a manager who is trusted by the team, credible to peers, and visibly delivering to leadership by day 90. This guide is the week-by-week version, opinionated and specific.

The first 90 days are won or lost in the first two weeks

The most common failure mode for new EMs is assuming there's plenty of time. There isn't. Leadership has made a large bet on you, peer teams are watching for competence signals, and your direct reports are calibrating you against their last manager within the first five 1:1s. By day 14, the shape of your tenure is largely set — your team has decided whether you are trustworthy and substantive, and peer EMs have decided whether you are serious. You cannot recover from a weak first two weeks by being strong in weeks 3-12. The converse is nearly true.

The new EM who spends the first two weeks listening to everyone is not humble. They are running out the clock on the only time window when asking anything is free.

Use the first two weeks aggressively. Ask every question. Meet every stakeholder. Form opinions out loud, and update them publicly when new information arrives. Demonstrate that you are learning fast, not learning carefully.

Week 1-2: listening tour with structure and written output

The first two weeks are a listening tour, but not a passive one. Schedule 30-minute 1:1s with every direct report, your manager, every peer EM on the engineering leadership team, your PM counterpart, your design counterpart, and at least two skip-levels in key adjacent teams. That's 15-25 meetings. Block them into the first 10 working days.

In each meeting, ask the same core set of questions — the consistency is the point. The pattern-matching across answers is where the signal lives.

1. What's going well on this team right now?
2. What's the single biggest thing holding the team back?
3. If you could change one thing about how we operate, what would it be?
4. Who on the team is a flight risk, and why?
5. Who on the team is underutilized, and why?
6. What do you wish my predecessor had done differently?
7. What should I absolutely not change in my first 90 days?

Write the answers down, in the same document, side by side. By day 10, you'll have a matrix of perspectives that surfaces the 2-3 things everyone agrees on (act on these fast), the 2-3 things everyone disagrees about (these are the real political questions), and the 2-3 things only one person mentioned (these are the idiosyncratic concerns that may or may not matter).

Produce a written "first impressions" document at the end of week 2 — shared with your manager first, then with your team. Three sections: what I'm hearing, what I'm not yet sure about, what I'm going to do about it. This document establishes that you process input, form views, and act. It also creates a dated record you can reference at day 90.

Week 3-4: make one small, visible decision

By week 3, the team needs to see you make a decision. Not a big one. A small one, visible to them, that demonstrates you have judgment and are willing to exercise it. Classic good first decisions:

• Operating-cadence change: Moving standups from daily to MWF, or collapsing two separate syncs into one, or adding a short weekly team retro.
• Tooling or process fix: Resolving a specific pain-point everyone mentioned in the listening tour — a broken CI gate, a PR-review norm, a flaky on-call process.
• Prioritization call: Killing one low-value workstream the team has been half-heartedly maintaining, or explicitly greenlighting a neglected initiative.
• People decision: Pairing two ICs on a project to break a knowledge silo, or adjusting a reporting line that's clearly not working.

Whatever you choose, pick something that (a) came up in multiple 1:1s, (b) is genuinely in your authority to change, (c) can be reversed if wrong, and (d) ships visibly this week. Announce it, implement it, and follow up on it. This is the signal that converts "new EM" into "our EM."

Don't reorganize in the first month. Don't change performance expectations. Don't touch compensation. Don't do anything that can't be undone in a meeting. Those decisions come later — but the willingness to decide small things now is the foundation that lets you decide big things later.

Week 5-8: build your operating system

By week five, the listening tour is done and the first small decision has shipped. Now you build your operating system — the repeatable mechanisms that will let your team run without you having to be in every meeting.

The core mechanisms every EM team should have by week 8:

• Weekly 1:1s with every direct report, 30 minutes, agenda doc shared in advance, running notes maintained meeting-to-meeting.
• Weekly team meeting, 30-45 minutes, with a consistent structure: priorities, blockers, announcements, no status updates (those are async).
• Async status update, published weekly by you, covering what shipped, what's in flight, what's at risk, and what decisions are pending.
• Decision log, a running document of non-trivial decisions with date, context, and outcome. This is invaluable when reviewing in quarter 2.
• Incident review process, even if the team is small. How do you learn from misses? Who runs the review? What's the cadence?
• Roadmap review with your manager, monthly, 60 minutes, structured against business goals not task lists.
• Peer EM sync, biweekly, to stay calibrated with other teams and surface cross-team issues early.

If the team already has versions of these, evaluate them and improve the weakest one. If they don't, install them. Don't install all of them at once — add one per week so the team can absorb the change. By week eight, the team should feel noticeably more organized than when you arrived.

Week 9-12: ship something real and set the quarter

By week nine, you need to ship something material — either something the team ships under your ownership, or something you personally deliver as a manager (a hiring plan, a reorg proposal, a major process fix). The distinction between an EM who is managing and an EM who is leading is that the latter has visibly delivered something to the organization by day 90.

Choose the thing carefully. It should be (a) aligned with what your manager told you success looks like at 90 days, (b) visible to at least one level above your manager, (c) achievable with the current team without heroics, and (d) a stepping stone to the quarter-2 goals rather than a standalone deliverable.

Also, by week 12, set the quarter's goals. Don't inherit them from your predecessor. Write them, socialize them with your manager and team, and publish them. This is the document the team will use to orient for the next 3 months, and it should carry your fingerprints. If you're still operating off the previous EM's plan at day 90, you haven't taken the role; you've just physically occupied it.

End the 90 days with a written retrospective to your manager: what you learned, what you changed, what's working, what's at risk, what you need from them in the next quarter. This document mirrors the one you wrote at day 14 and closes the loop. It demonstrates that you treat the role as a learning system, not a status. Managers who see this kind of document from a new EM mark them as high-potential for the next tier up.

Common 90-day failure modes — and how to avoid each

A few specific failure patterns are worth naming explicitly, because they're common and they're often invisible while they're happening:

• The invisible EM: Listens for 90 days, decides nothing, ships nothing. Team loses respect by week 6. Fix: make the week-3 small decision, on schedule.
• The reorg-happy EM: Arrives with a thesis, starts reshuffling in week 2. Team loses trust. Fix: no structural changes in the first month.
• The friend-to-the-team EM: Over-indexes on being liked, avoids hard feedback. Performance problems compound. Fix: give one piece of substantive feedback in every 1:1 from week 2 onward.
• The peer-ignoring EM: Focuses entirely on the team, ignores peer EMs and cross-functional partners. Gets blindsided by organizational dynamics. Fix: biweekly peer EM sync from week 1.
• The under-delivering EM: Manages the team well but ships nothing visible by day 90. Leadership loses confidence. Fix: pick the week-9 deliverable early and work backward.
• The over-communicating EM: Sends long updates no one reads, holds too many meetings. Team feels micromanaged. Fix: 80-word weekly async update, tight agenda discipline.

Each of these failure modes has a recovery path, but the recovery always takes longer than the original window would have taken. Prevention is cheap; recovery is expensive.

Next steps

Before your first day as an EM, do three things. First, draft your listening-tour target list — every direct report, peer EM, cross-functional counterpart, and relevant skip-level. Second, write down the seven listening-tour questions and commit to asking them verbatim in every meeting. Third, schedule a day-14 working session with yourself to produce your first-impressions document.

In the first two weeks, run the tour aggressively and write the document. In weeks 3-4, make the one small visible decision. In weeks 5-8, install the operating system. In weeks 9-12, ship the material thing and set the quarter. Close with the retrospective.

The first 90 days are the foundation of the next two years. Treat them as a managed project, not an adjustment period, and the rest of the tenure gets dramatically easier.

Related guides

• Your First 1:1 With a New Manager — The Template That Works — Your first 1:1 sets the tone for year one. Use this 30-minute template to surface operating norms, expectations, and the calibration you need.
• First Week Playbook for Engineers: Read, Ask, Ship in 7 Days — A concrete day-by-day plan for engineers starting a new job in 2026: what to read, the questions to ask, and what to ship before Friday.
• The 30-60-90 Day Plan Template for a New Job in 2026 — By Role and Seniority — A strong 30-60-90 plan turns a new job from vague onboarding into a visible operating plan. Use this role-by-role template to learn fast, build trust, ship early wins, and avoid overpromising in your first quarter.
• First-Day Questions to Ask Your Manager: The Year-One List — The specific questions to ask in your first one-on-one that set up year-one success. No filler, no soft-pedaling — a checklist you can bring into the meeting.
• First Week Playbook for Data Scientists: Access, Baselines, Stakeholders — A concrete first-week plan for data scientists in 2026: get data access on day one, establish baselines, and map the stakeholders who will act on your work.