How to survive your first 90 days in a new role

You got the job, you have the start date. Now you probably also have a low-grade hum of anxiety that you are not entirely sure what to do next.

This post is a field guide for the window between “congratulations” and the moment (weeks or months from now) when the role actually starts to feel like yours: What to focus on, what to deliberately ignore, and how to ask for help without feeling like you are exposing yourself.

If you have been reading this publication, you already know about the gap. This is what you do while you are in it.

The first two weeks: absorb, do not perform

The biggest mistake people make in a new role is trying to prove themselves immediately.

You walk in on day one with the energy of someone who needs to justify the hiring decision, and you start producing opinions, ideas, suggestions, before you have understood the environment you are producing them in. Resist that need to prove yourself on your first day.

Your first two weeks are not about output, they are about input. You are learning how this place actually works, which is almost never how it looked from the outside.

Pay attention to how decisions get made. Who do people check with before moving forward? Whose opinion carries more weight than their title suggests? Where does alignment actually happen? In meetings or conversations after meetings?

Learn the language. Every company has its own shorthand, its own acronyms, its own way of describing what matters. “Velocity” means something different at a startup than it does at an enterprise company. “Alignment” might mean genuine consensus or it might mean “the most senior person in the room has decided.” Listen for what words mean in context, not just what they say on paper.

Map the relationships, not just the roles. Your org chart tells you who reports to whom. It does not tell you who trusts whom, who has history, who is in tension, or who informally runs the team despite not having the title. That map takes weeks to build, and it matters more than the official one.

The temptation will be to skip this phase because it feels passive, but it’s actually the most strategic thing you can do. Every decision you make in month two and three will be better because you spent the first two weeks watching before acting.

What to focus on in the first 90 days

You cannot learn everything at once. You should not try. Instead focus on these things.

One relationship with a manager that is honest, not performative. This is the single most important thing you can build in your first 90 days - the relationship with the person who decides whether you are succeeding.

Have the conversation early. Ask them: what does success look like in this role at the 90-day mark? What would concern you if you saw it? What did the previous person in this role get right, and where did they struggle? You are not being needy by asking these questions. You are being precise. Most new hires fail not because they are incompetent but because they optimised for the wrong things. This conversation prevents that.

One early win that is visible but not forced. You do not need to revolutionise anything in your first three months. You need to demonstrate that you can see a problem, act on it, and deliver something useful. Pick something small enough to complete well and visible enough that the right people notice: a process that is clearly broken, a document that everyone complains about but nobody has fixed, a question that keeps coming up in meetings that you can actually answer.

The win does not need to be dramatic, it just needs to be real and have some impact.

One opinion that you form slowly and share deliberately. By the end of your first 90 days, you should have a point of view about something. Not a point of view about everything. One thing. Maybe it is about how the team communicates, a gap in the product, or a process that is creating more friction than value.

Form it carefully. Validate it with people you trust. And when you share it, frame it as a question or an observation, not a declaration. “I have noticed X, and I am curious about what you think” lands better than “I think we should change X” when you are still new.

What to ignore

The things you ignore as you navigate your new role are just as important as the things you act on.

Ignore the urge to have an opinion on everything. You don’t need to contribute to every conversation. You also don’t need to prove you are smart in every meeting. In fact, the people who talk the most in their first month are not always the ones who build the most credibility. Credibility in a new role comes from the quality of what you say, not the quantity.

Ignore comparisons to whoever had the role before you. You will hear their name. You will hear what they did well, what they did not, how they handled certain situations. File it but don’t compete with it. That person had a different context, different relationships, and a different version of the role. You are not replacing them. You are doing the job in your own way, in the present.

Ignore the pressure to be fully competent right now. You will not be. That is normal. If you read our post on the gap, you know that competence and confidence arrive on different timelines. The discomfort you feel is not evidence that you are failing. It is evidence that you are new. Those are different things.

Ignore informal performance reviews from your own brain. Your internal narrator may be critical in the first 90 days. It will tell you that a quiet meeting meant people are unimpressed. It will tell you that a missed detail means you are falling behind. It will score every interaction and find you lacking. Do not trust it. Trust the actual feedback you get from your manager and your team.

How to ask for help without feeling like a fraud

This is the part that trips most people up. You know you need help. You know that asking for it is rational. But the act of asking feels like admitting you should not be here. So let us reframe it.

Asking for help is a signal of competence. The people who ask good questions in their first 90 days are almost always the ones who ramp up fastest. They are not wasting time guessing. They are not making avoidable mistakes because they were too proud to check. They are doing the thing that every experienced professional knows is smart, even though it feels vulnerable.

Frame your questions with context. There is a difference between “I do not understand this” and “I have looked at X and Y, and my understanding is Z, but I want to check whether I am reading this correctly.” The first sounds like you are lost. The second sounds like you are thorough. Both are asking for help. One feels better for everyone involved.

Ask about norms, not just tasks. The questions that save you the most pain in a new role are not about what to do. They are about how things are done here. “How do you usually handle disagreements in this team?” “What is the unspoken rule about replying to emails after hours?” “Is there anything about this place that took you a while to figure out?” These questions make people feel like experts, which means they enjoy answering them, and the answers will save you months of awkward missteps.

Name the gap. If you are in a meeting and you do not understand something, you have two options. You can nod and hope nobody asks you a follow-up question, or you can say “I am still getting up to speed on this, can someone give me the short version of the context?” The second option feels risky. It is actually safer. Because the alternative is pretending you understand something you do not and then making a decision based on that misunderstanding. That is where problems with avoidable consequences start.

The 90-day mindset

Your first 90 days are for orientation not audition.

You are not there to prove you deserve the role. You already got the role. You are there to learn how to do it well, in this specific context, with these specific people, under these specific conditions. That takes time, and taking time is not the same as falling behind.

Now here’s something that’s been bothering us…

Why does the learning have to start on day one? Surgeons simulate before they operate. Pilots train before they fly. But when it comes to careers, you get a start date and hope that you will find your feet before anyone notices you have not found them yet.

This is why we built Daysim.

Daysim lets you step into a realistic version of your new role before you begin day one. You get to practise the decisions, the conversations, and situations that would normally catch you off guard. You walk in with reps behind you instead of starting from scratch.

Everything in this guide is real advice. But it is also a workaround for a problem that should not exist. You should not have to figure out the hard parts of a role live, in front of the people counting on you.

Prepare before the first day. Sign up on Daysim.

Before You're Ready is a series of field notes from the middle of figuring things out in career, job transitions, life and the things inbetween.