Your first 90 days in a new job

It is your second week. A senior colleague walks you through the team’s deployment pipeline and, somewhere around the fourth tool in the chain, says apologetically, “Yeah, we know this part is messy.” Your instinct fires immediately. You have seen this solved before. You know exactly what the fix looks like. You are already composing the Slack message in your head.

Do not send it.

Not because you are wrong — you might be completely right — but because you do not yet know what you do not know. You do not know why the messy part exists. You do not know who owns it, who tried to change it before, or what political capital got spent on that attempt. You do not know whether the “mess” is in fact load-bearing in a way no documentation captures. The fastest way to be dismissed in a new job is to prescribe before you have finished diagnosing.

The first 90 days at a new job are the most consequential period of your entire tenure there. Research by Michael Watkins — who wrote The First 90 Days, a widely cited model for executive transitions — shows that the patterns established in the first quarter tend to persist for years. The impression you form, the relationships you build or fumble, the credibility you accumulate or squander: these compound. Getting this quarter right is not about being meek or strategic in a cynical sense. It is about doing the obvious thing that most ambitious people refuse to do — slowing down enough to actually learn the environment before acting on it.

The three-phase arc

The 90-day period maps cleanly into three distinct phases with different goals. Most people conflate all three into a single undifferentiated ramp-up period. That is why they charge in and change everything in week two, then wonder why nobody is listening by week six.

Phase one: listen and map (days 1 to 30)

Your only job in the first month is to understand the environment. That means understanding the people, the power structures, the unwritten rules, and the history of decisions that shaped everything you are inheriting.

Schedule 30-minute conversations with every person whose work touches yours — peers, stakeholders one level up, the team members who will work for or alongside you. Ask the same four questions in each conversation: What is going well that we should protect? What is not working that nobody talks about? What would you do first if you were in my role? What do I need to know that is not in any document?

That last question reliably surfaces the most important information. Every team has context that lives only in the heads of its longest-tenured members — the product decision that failed and was quietly shelved, the relationship between two teams that has been strained for two years, the process that everyone follows and nobody believes in. You will not find this in the wiki or the org chart. You find it in one-on-ones.

While you are listening, map the stakeholders. Draw it on paper if that helps — who has formal authority, who has informal authority (they are not the same people), who is a blocker, who is an ally, who is neutral and persuadable. Watkins calls this a stakeholder map, but you can call it whatever you want. The point is to have a model of the social landscape before you start trying to navigate it.

Do not share opinions publicly in month one. This is harder than it sounds. When you are capable and ambitious, silence feels like invisibility. Suppress the reflex. Opinions cost credibility when they are uninformed. Questions earn it. Nobody resents a new person who asks good questions. People remember the new person who opened their third week with a confident pronouncement that turned out to miss three years of context.

Clarify expectations explicitly with your manager

In your first week, have a direct conversation with your manager about what success looks like in 30, 60, and 90 days. Do not wait for them to initiate it. Most managers intend to have this conversation and do not get to it.

Ask: “What does a strong first 90 days look like from your perspective? What would make you think bringing me in was the right call?” Then write down what they say and send it back to them in an email. “Here is what I heard from our conversation — let me know if I am missing anything.” This does two things. First, you have a shared document of expectations that you can revisit. Second, your manager sees that you operate with precision and care about alignment. That impression matters.

If your manager is vague — “just get up to speed, we’ll figure it out” — push gently for specifics. “What would getting up to speed look like at 30 days? Is there a deliverable I could aim for, or a relationship I should have built?” Vague expectations are a trap. You will work hard and feel like you are delivering, and then a review comes and the criteria turn out to have been different from what you assumed.

This is not about being rigid or reducing everything to metrics. It is about naming the target so you can aim at it.

Phase two: pick the right win (days 31 to 60)

By the end of month one, you should have a clear enough picture to identify one thing worth doing. Not ten things — one.

The early win has to meet three criteria. It has to be deliverable within the quarter (nothing that requires six months of buy-in). It has to be visible to people who matter — a win that only you and one colleague see does not build broad credibility. And it has to solve a real problem, not a cosmetic one. A dashboard nobody asked for is not an early win. A process change that saves two hours per week for five people is.

The temptation in month two is to pick something ambitious — to tackle the big structural problem you identified in your listening tour. Resist this. Big structural problems require political capital you do not yet have. They require deep context about why the structure exists and who benefits from its current form. Most importantly, they take longer than 90 days, which means you will not be able to show a finished result.

Small and finished beats large and half-done every time.

Once you have identified the win, scope it tightly and align explicitly with your manager before you start. “I am planning to tackle X over the next four weeks. My thinking is that the output would be Y. Does that feel like a good use of my time?” This does two things: it ensures you are working on something they care about, and it creates an expectation that you will deliver — which sharpens your own commitment.

Phase three: ship it and narrate it (days 61 to 90)

Month three is execution and communication. You build the thing, ship the thing, and then tell people clearly and specifically what happened.

The narration part is the piece most early-career professionals leave out. They ship the work and wait for people to notice. People are busy. They do not notice. You need to close the loop explicitly: send an update to your manager, mention it in the relevant team channel, include it in whatever status communication exists. Not in a self-promotional way — just the facts. “We shipped the automated reconciliation report this week. It replaces three hours of manual work for the finance team each Monday. Here is what we built and why.”

This is not bragging. It is organizational communication. Decision-makers build their picture of your contribution from the signals they receive, and if you do not send signals, they build their picture from absence. You do not need to be loud. You need to be legible.

The diagnosis before prescription principle

The thread running through all three phases is a single idea: diagnose before you prescribe.

When a doctor meets a patient presenting with symptoms, they do not walk in with a treatment plan. They ask questions, run tests, form a provisional hypothesis, update it as new information arrives. They earn the right to prescribe by demonstrating that they understand the patient’s specific situation — not by applying the protocol that worked last time.

New job, new team, new context. Your experience from previous roles is valuable, but it is prior probability, not certainty. The thing that worked brilliantly at your last company may fail here because the culture is different, the constraints are different, or the problem was never quite what it looked like. Your job in month one is to update your priors, not to act on them.

The people who charge in and immediately start changing things are usually not stupid. They are usually capable and confident. That confidence is precisely what makes the mistake so damaging: they move fast enough to create friction before they have the credibility to absorb it.

A note on authenticity

Nothing here requires you to be someone you are not. This is not about performing humility or hiding your capabilities. It is about sequencing. Share your ideas — in month one, share them in one-on-ones and conversations, not in all-hands meetings. Ask your questions out loud. Offer your analysis when asked. Show your thinking process. Just do not confuse having ideas with having the full picture.

The best colleagues I have seen navigate new jobs did not become different people in their first quarter. They became particularly attentive. They asked more questions than usual. They were slower to conclude. And by month three, when they delivered something concrete, everyone was ready to listen — because the credibility had been earned.

The first quarter shapes how you are seen for years. Use it deliberately.