The first 90 days at a new job are less about proving you can do the work and more about earning trust before you have a track record to stand on. The people around you are forming a quick read of how you operate, and that read tends to stick. The good news is that almost none of it depends on being brilliant in week one. It depends on learning how the team actually works before you try to change it, and handling the people part without tripping over yourself.
The short version: spend the first couple of weeks listening and mapping how things run, get your manager to tell you plainly what success looks like, land one small visible win, and treat early friction as information rather than a verdict. The rest of this guide walks through each of those.
Weeks one and two: learn before you change anything
The fastest way to lose goodwill early is to arrive with fixes before you understand why things are the way they are. Every process you find clumsy was built by someone who is probably still in the building. Spend the first two weeks asking how and why far more than suggesting what.
A few concrete moves: ask each person you work with what they are responsible for and what they wish ran more smoothly; map who actually owns the things you will touch, which is rarely what the org chart says; and when you spot something that looks broken, write it down instead of raising it. You are building a list to use in week eight, not week one.
Then follow through on the small stuff. The tiny commitments are what build an early reputation: replying when you said you would, showing up prepared to the first meetings, finishing the boring onboarding task. Nobody is watching for genius yet. They are watching whether you do what you say.
Get your manager's definition of success in writing
Most new hires guess at what their manager wants and find out at the first review whether they guessed right. Skip the guessing. In an early one-on-one, ask directly: what does a strong first 90 days look like for this role, and how will we both know I got there? Write the answer down and send it back as your understanding, so you are working from the same page.
If the answer is vague, that is useful too. Ask for one concrete example of what good looks like. A manager who cannot name one is telling you the priorities are still forming, which means you have room to help shape them, and that you should check in more often rather than less.
Aim for one small, visible win
Somewhere in the first six to eight weeks, finish one thing that a few people notice. Not a dramatic overhaul. A recurring annoyance you quietly fixed, a report you made easier to read, a task you took off someone's plate. The point is not the size. It is proof that you can go from new to useful, and it gives your manager something concrete to point to on your behalf.
Pick something inside your clear ownership so you are not stepping on anyone. An early win that requires rewriting someone else's work is not a win. It is the friction the next section is about.
When a teammate pushes back, decode it
Two weeks in, you suggest a faster way to run the weekly report, and a senior teammate says something like it was tried before, then goes quiet. The instinct is to read that as a verdict on you. It is almost always something else: a project that failed loudly before, a process they built, or a relationship with whoever owns that report.
The objection is a summary of a story you were not there for. Your job in the first 90 days is not to relitigate it, it is to figure out what it is protecting. So ask a low-heat question: "Was it the tool, the timing, or how people reacted last time?" That invites information instead of a verdict and gives the other person room to explain without feeling cornered.
Then adapt, and let them see you do it. If the last tool was a mess and support quietly dropped it, do not rebuild the same tool. Change something small and say that you did. Visible adaptation is what earns you permission to try bigger things later. The mistake to avoid is taking the friction personally, because it is almost always about change, timing, or territory, not about you.
When to escalate, and when not to
Some friction is just friction, and some is a signal. The difference usually comes down to whether work is actually getting blocked. A teammate who is slow to reply while the report still ships on time is a wrinkle. These are the signals worth taking seriously:
- You are cut out of meetings you need in order to do the job.
- The same question keeps going nowhere, week after week.
- Someone else's name keeps landing on work you did.
The standard advice is to document everything and report it.That matters for repeated disrespect, blocked work, or anything resembling retaliation.But it is the wrong first move for ambiguous early friction, because reporting formalizes a problem that might have been a misunderstanding, and you cannot quietly take it back once a manager or HR is a party to it.Run the ask-then-adapt approach first.
If you do need to raise it, bring a short, neutral pattern instead of a complaint: here is what keeps happening, here is what I have tried, here is what I need.
Ask for feedback before the review does it for you
Do not wait for the formal review to learn how you are landing. Around the one-month mark, ask your manager a specific question rather than a general one. "How am I doing" invites a polite nothing. "What is one thing I could be doing better in this role" tends to get a real answer. Asking early means anything you hear is still fixable before it hardens into a review line.
If your manager keeps circling a vague concern they cannot pin to an example, that is often a secondhand version of a conversation you have not had yet. Ask what a better version would look like in concrete terms. If the expectation stays fuzzy after one honest re-ask, write down your working assumption and ask them to correct it.
One thing to do this week
None of this is about being the standout in the room by Friday of week one. It is about becoming someone the team trusts to move carefully, which is who ends up with the interesting work a few months in.
If you are already in the job, write down the one recurring friction you keep working around, and ask one low-heat question about it at your next one-on-one.If you are still scouting roles, remember that the read on how a team really works starts before day one.Joblet is one place to scan openings, though no board shows you the informal rules, only the people do.
And once you are interviewing, a tight opening answer and a clear reason you are the hire are what get you to day one in the first place.