The First-90-Days Checklist

Every other tool in this part — the one-on-one, the status report, the feedback script — assumes you already know your team and your terrain. But there is one moment when you know almost nothing: the first day in a new manager role. Whether you were promoted from inside the team or hired from outside, you are now responsible for outcomes you don’t yet understand, produced by people you don’t yet know, inside a system you didn’t build.

This page gives you a checklist for that moment: a phased plan for roughly the first 30, 60, and 90 days. It tells you what to learn, who to meet, and — just as importantly — what not to change yet. The single most useful idea here is one principle, so let’s name it up front: learn before you change. A new manager who reorganizes the team in week one is not decisive; they are guessing.

Why the first 90 days are a distinct problem

A new manager arrives under a peculiar pressure. Everyone is watching to see what kind of boss you’ll be, and the temptation is to prove yourself — to make a visible mark fast, to show you deserve the role. That instinct is exactly backwards. In your first weeks you have the least information you will ever have and the most credibility you can spend. Spend it wrong and you spend the rest of the year recovering.

The 90-day frame exists because trust and understanding both take time, and they build in a rough sequence. The first month is for listening — you cannot lead people you haven’t met or fix a system you haven’t seen run. The second is for making sense — patterns emerge, you form a view of what’s actually wrong. The third is for acting — now your changes rest on evidence, and the team has seen you do the homework, so they’ll follow. Skip a phase and the later ones wobble.

The evidence — the transition is where managers are most likely to fail

Work on leadership transitions — most famously Michael Watkins’s The First 90 Days (2003) — generally finds that a manager’s early moves shape their success far out of proportion to the time involved, and that a large share of new leaders stumble in the first year or two. The recurring cause isn’t incompetence; it’s acting on assumptions carried from a previous role or formed too quickly. Treat the exact figures as illustrative, but the direction is well established: the transition is a distinct, high-risk phase that rewards deliberate learning over fast action.

The template

Use this as a living checklist — copy it, tick items off, add your own. The phases overlap in reality; the boundaries are guides, not walls.

FIRST-90-DAYS CHECKLIST — [your name], [role], starting [date]

DAYS 0–30 · LISTEN AND LEARN  (change almost nothing)
  People
   [ ] One-on-one with every direct report — just to know them (see /toolkit/one-on-one-agenda/)
   [ ] Meet your own manager: what does success look like to them?
   [ ] Map the stakeholders — who does the team depend on, and who depends on the team?
   [ ] Meet the top 3–5 stakeholders in person
  The work
   [ ] Learn the current goals — what is the team actually trying to achieve, and by when?
   [ ] Sit in on the team's core rituals (standups, reviews) as an observer, not a changer
   [ ] Find the pain: ask each person "what's the most frustrating part of your week?"
   [ ] Read the last 3 months of docs, metrics, retros, incidents
  Yourself
   [ ] Write down your first impressions — you'll want them later, and memory fades
   [ ] Say out loud: "I'm here to learn first. I won't change things I don't understand yet."

DAYS 30–60 · MAKE SENSE  (form a view; pick one early win)
   [ ] Name the 2–3 real problems you now see (separate symptoms from causes)
   [ ] Confirm your read with the team — "here's what I'm seeing; what am I missing?"
   [ ] Identify ONE early, low-risk win: small, visible, clearly helpful, hard to get wrong
   [ ] Agree with your manager on what you'll focus on this quarter
   [ ] Start delivering the early win — with the team, not around them

DAYS 60–90 · ACT  (change what the evidence supports)
   [ ] Ship the early win; make the improvement visible to the team
   [ ] Propose any bigger changes now — explained, with the reasoning shown
   [ ] Set the cadence you'll run from here (one-on-ones, status, retros)
   [ ] Give and ask for feedback openly — you're past "the new person" now
   [ ] Review your day-1 notes: what did you get right, what surprised you?

How to use it

Run the phases in order, but let them overlap. You’ll still be meeting stakeholders in week five and still learning in month three. The point of the phases isn’t rigid dates — it’s sequence of emphasis. Early weeks weight heavily toward listening; later weeks toward acting. If you find yourself acting hard in week two, stop and ask what you actually know.

Do the one-on-ones first, and do them for their own sake. In the first 30 days, a one-on-one with each report isn’t about status or goals — it’s about the person. Who are they? What do they do well? What’s frustrating them? What do they need from a manager? These conversations are where trust starts, and trust is the thing every later change will draw on.

Ask the same open questions everywhere. Two questions do most of the work: “What’s the most frustrating part of your week?” and “If you had my job, what’s the first thing you’d fix?” Ask every person and every stakeholder. When the same answer comes back from five different people, you’ve found something real — and you didn’t have to guess.

Pick the early win carefully. The right early win is small, visible, clearly useful, and almost impossible to get wrong. It is not a reorganization or a strategy pivot. It’s the annoying broken thing everyone complained about that you can quietly fix. The purpose isn’t the fix itself — it’s to show the team, with evidence, that you listened and you can deliver. That earned credibility is what pays for the harder changes later.

Say the quiet part out loud. Tell the team, in your first week, that you intend to learn before you change. This does two things: it buys you room to ask “naive” questions without looking weak, and it reassures people who are (rightly) nervous that the new boss will blow up what works. Then honor it — nothing erodes trust faster than promising to listen and reorganizing on day ten.

The common trap — the two ways new managers derail

There are two classic failure modes, and they are opposites.

The first is changing too much, too fast. Eager to prove themselves, the new manager reorganizes the team, kills a process, or launches a big initiative before understanding why things are the way they are. Often the “obviously broken” thing exists for a reason nobody thought to explain. The team, who wasn’t consulted, digs in. The manager has spent their credibility before earning any, and now every future change meets resistance.

The second is the opposite: hiding and changing nothing. Afraid of missteps, the manager stays vague, defers every decision, and three months in has left no fingerprint at all. The team concludes the new boss is either checked out or afraid, and starts routing around them. Listening was supposed to be a phase, not a permanent posture.

The escape from both is the phased plan: listen genuinely and visibly early, then act decisively on what you learned. Learning is the setup; the early win is the proof that you were setting up to do something.

A filled-in example

Here’s the checklist as Priya filled it in — she was hired from outside to manage a 9-person kitchen and service team at a busy cafe. Notice she resisted the obvious “fix the slow morning rush” instinct until she understood why mornings were slow.

FIRST-90-DAYS — Priya, Cafe Floor Manager, started Apr 1

DAYS 0–30 · LISTEN
  People
   [x] 1:1 with all 9 staff — learned two baristas are quietly doing the schedule unpaid
   [x] Met the owner: success = fewer walkouts at peak, keep the regulars happy
   [x] Mapped stakeholders: owner, supplier rep, the landlord, the weekend regulars
   [x] Met the supplier rep — deliveries land at 8am, right in the morning rush
  The work
   [x] Learned the goal: cut the 8–9am queue without adding headcount
   [x] Watched three morning shifts from the corner — said nothing, just timed things
   [x] "Most frustrating part of your week?" → 6 of 9 said the 8am delivery chaos
   [x] Read last quarter's sales — mornings are 40% of revenue, so the pain is expensive
  Notes to self
   [x] Day-1 hunch: "hire more morning staff." NOTE: check this against what I learn.

DAYS 30–60 · MAKE SENSE
   [x] Real problem isn't staffing — it's the 8am delivery blocking the counter for 20 min
   [x] Confirmed with team: "Is the delivery the real bottleneck?" → unanimous yes
   [x] EARLY WIN chosen: move the delivery to 6:30am. Small, cheap, obviously helpful.
   [x] Told the owner: focusing this quarter on flow at peak, not on hiring
   [x] Called the supplier — they can do 6:30am at no extra cost

DAYS 60–90 · ACT
   [x] Delivery moved to 6:30am. Morning queue visibly shorter within a week.
   [x] Team saw it: "she actually fixed the thing we complained about"
   [x] Bigger change proposed WITH the team: a simple pre-open prep checklist
   [x] Set the cadence: 15-min pre-shift huddle, monthly retro (see /toolkit/retro-format/)
   [x] Reviewed day-1 notes: the "hire more staff" hunch was wrong — glad I waited.

The whole example turns on one restraint. Priya’s day-one instinct — hire more morning staff — was expensive, slow, and wrong. Because she listened first, she found the actual cause (a delivery landing mid-rush), fixed it for free, and won the team’s trust in the process. Had she pushed the hiring plan in week one, she’d have spent money, solved nothing, and taught the team that the new manager doesn’t listen.

In practice — why the early win came in month two, not week one

Priya could have moved the delivery time in her first week — the fix itself was trivial. She waited on purpose. In week one, moving the delivery would have looked like a lucky guess, and she wouldn’t have known it was the real bottleneck versus a symptom. By confirming it with the whole team first, the same small change became something else: visible proof that she’d done the homework and heard them. Same fix, very different meaning. The delay wasn’t wasted time; it was what converted a fix into trust.

How it connects

This checklist is really the whole toolkit deployed in sequence. The first 30 days lean on the one-on-one agenda to meet each report. As you make sense of the work, the RACI matrix helps you map who owns what, and the project charter frames your early win. Once you’re acting, the weekly status report and the retro format set the cadence you’ll run from here. If you inherited a team with open roles, the hiring scorecard waits until phase three — hiring before you understand the work is its own version of changing too fast. For the bigger picture, see the toolkit overview.

Try this

If you’re starting a new manager role in the next month, copy the template above into a document and put real names in the “meet every report” and “top stakeholders” lines today. If you’re already in a role — even one you’ve held a while — run the days 0–30 questions anyway: ask each report “what’s the most frustrating part of your week?” and “if you had my job, what would you fix first?” You’ll almost certainly hear something you’d stopped noticing. Write down what comes back, and look for the answer that shows up more than twice — that’s your next early win.