Your First 90 Days in a New Job: Understand Before You Contribute

It is two weeks in. You have sat through an induction you have already forgotten, been added to nine channels you do not understand, and been told twice where the kitchen is because you asked twice. Someone mentioned a project by an acronym and everyone nodded, and you nodded too. You have produced almost nothing. And somewhere around the second Tuesday, the thought arrives: they have made a mistake, and at some point soon they are going to notice.

Here is the thing worth hearing before anything else. Feeling incompetent at week three is not a warning sign. It is the job. You have been dropped into a system that took everyone else years to learn, stripped of every shortcut and reference point you built up at your last place, and asked to function in it while also learning names. Of course you feel useless. You currently are, in the narrow sense that you cannot yet do much unaided. That is a temporary state with a known cure, and the cure is time, not panic.

What follows is not about making an immediate impact. It is largely about the opposite.

Why does wanting to make an impact quickly backfire?

The instinct is understandable. Someone chose you over other candidates. You want to justify that, fast, before the goodwill runs out. So you look for something obviously broken and offer to fix it.

The problem is that in week two you can only see the surface of things. You notice the approval process has four steps and suggest cutting it to two. What you cannot see is that it had two steps until a serious mistake three years ago, that a specific person got badly burned by it, and that the two extra steps were their idea and are the reason they can sleep. You have just walked into a room and, without knowing it, told someone their careful work is stupid.

Almost nothing in a functioning workplace is arbitrary. Plenty of it is outdated, and some of it genuinely is stupid, but nearly all of it has a history. The awkward process, the spreadsheet nobody will replace, the meeting that seems pointless — each usually exists because something went wrong once. You cannot tell which are fossils and which are load-bearing until you know that history.

And credibility is asymmetric. It accrues slowly and drops fast. One “the new person thinks they know better” conversation, held when you are not in the room, can shape how your input is received for months. You will still be arguing against it in month five without knowing that is what you are doing.

The more effective version of the same instinct: be visibly engaged in learning. Ask good questions. Write things down. Take the boring task nobody wants and do it properly. This reads as competence far more reliably than an early proposal does.

Your first job is not to contribute. It is to understand. Contribution follows, and it lands far harder when it comes from someone who clearly did the work of understanding first.

What is the informal organisation, and why does it matter more than the org chart?

This is the single highest-value thing you can learn early, and almost nobody will teach it to you directly.

The org chart tells you reporting lines. It tells you almost nothing about how decisions actually happen. Running underneath it is a second structure — informal, unwritten, and far more predictive of whether your work gets anywhere.

The roles to look for:

• The person who is actually consulted. Their title may be unremarkable, but decisions do not get made without a quiet word to them first. You spot them by noticing whose name comes up as a question: “has anyone asked Priya?” — and everyone stops until someone has.
• The quiet blocker. They rarely say no outright. Things they dislike simply do not progress: the review sits, the meeting slips, the reply never comes. Nothing has been refused. Nothing has moved either. Learning who this is, and what they care about, saves you enormous frustration.
• The one who knows where everything is. Often long-tenured, often not senior. They know which of the four versions of the document is real, which system is deprecated but still running, who to email about the thing that breaks. Worth their weight in gold and usually under-thanked.
• Whose approval matters regardless of title. Sometimes a person whose sign-off is not required but whose objection is fatal. Their opinion carries because of history, expertise, or plain force of personality.
• Who talks to whom. Which two people came from the same previous employer, which team resents which other team and over what. Not gossip to join in with — context that explains otherwise baffling reactions.

You learn this by watching, not asking. Nobody answers “who really has power here?” honestly. But you can watch a meeting and note whose contribution changes the direction and whose is politely absorbed, who gets copied into things, who people check with before committing. Give it a few weeks and a pattern emerges that looks nothing like the diagram in your onboarding pack.

What should you ask early, and when does “I’m new” stop working?

For a short window, you have a licence that never comes back. You are allowed to not know things. Nobody expects you to know what the acronym means. This is the most valuable asset you have and it depreciates fast.

Questions worth asking while it lasts:

• What does a good week look like in this role?
• Who should I be talking to that I have not met yet?
• What is the thing everyone here knows that took you longest to learn?
• What goes wrong most often?
• Which of these meetings do I actually need to be in?
• Is there anything I am doing that seems normal to me but odd here?
• What does this acronym mean? (Every time. All of them.)

The window is roughly the first four to six weeks, and it does not close with an announcement. It closes when the same question, asked a second or third time, starts to read as inattention rather than newness. Around the two-month mark, “sorry, I’m still new” begins to sound like an excuse rather than a fact — particularly for anything you have already been told.

Why not asking costs more than asking

The strongest pull in the first weeks is to protect your face. You do not want to look like the hire who does not understand basic things. So you nod at the acronym, guess at the process, and quietly hope it resolves.

It compounds instead. The thing you did not ask in week one becomes the thing you cannot ask in week eight, because by then you are expected to know it. So you work around it, build a small private area of not-knowing, and it sits there — until it produces a mistake, at a point where the mistake is genuinely yours.

Asking a basic question in week two costs you nothing. Almost literally nothing: people expect it, most enjoy explaining, and it signals you are paying attention. The same question in month four costs you real credibility. Ask everything now, while it is free. Write down the answers, because you will be told most of it exactly once.

What is your manager actually judged on?

Your success is partly assessed through your manager, and their assessment of you is shaped by what they are under pressure about. Not cynical — just how the mechanism works, and knowing it makes you far more useful.

So find out. What are they measured on? What do they get asked about by their own boss? Which of their commitments is slipping? You can ask this fairly directly, and few people do, which is why it lands well: “What are the things you’re being held to this quarter? I’d like to make sure what I’m doing actually helps with those.”

The effect is that your work points at real pressure rather than at whatever was in the job description. A task that removes something from your manager’s plate is worth several tasks that are merely competent.

How do you work out what “good” means here?

Every workplace has standards that nobody writes down and everybody enforces. The mismatch is a common source of early friction — you are not doing badly, you are doing well according to your last employer’s rules. Things that vary and are never documented:

• Speed versus polish. Some places want a rough draft in an hour. Others regard sending anything unfinished as sloppy. Both consider the other approach clearly wrong.
• Response times. Is a message an hour old already rude? Is same-day fine? Is anything outside working hours actively frowned upon?
• Meetings. Is disagreeing in the room normal, or is it done privately beforehand? Do people arrive having read the document, or is it read aloud?
• Detail. Some teams want the summary. Others find a summary evasive and want the full reasoning.
• Autonomy. Is checking in seen as diligent or as needing hand-holding? Is going ahead seen as ownership or as going rogue?

The fastest way to calibrate is to read other people’s finished work. Ask for examples of things that went well — a report, a proposal, a piece of code. Not as a template to copy, but to read the level: how long, how formal, how much detail. Then check your read: “I’ve drafted this the way I would have at my last place — is this the right level of detail here?” A fast correction that stops you spending a month calibrated wrongly.

What should your first real contribution be?

Eventually you do have to do something. The instinct is that it should be impressive. It should not.

The best first contribution is small, visible, and genuinely useful to someone other than you. Not a reorganisation. Not a strategy. Something that quietly removes an irritation.

Good candidates:

• The document everyone complains is out of date. Update it.
• The recurring manual task someone dreads. Take it, or make it faster.
• The thing new starters always get confused by. Write it down properly — you are the only person who currently remembers what it is like not to know.
• The backlog item that has been sitting there because it is dull and nobody has the hours.

These work because they demonstrate three things at once: you noticed a real problem, you can finish something, and you will do unglamorous work. That combination is what makes people trust your judgement later — and when you do propose something larger, you propose it as someone who has already delivered.

One caution: check before you take it. What looks unowned is sometimes a stalled project of someone else’s. “Is anyone on this? I have capacity and I’d like to pick it up” takes ten seconds.

Who should you actually meet, and how do you ask without it being awkward?

Forget networking. What you are doing is more mundane: building enough of a relationship with the people whose work touches yours that asking them something is easy rather than an imposition.

Who to prioritise:

1. Your immediate team, properly and individually, not just in group settings.
2. Whoever hands you work, and whoever receives yours. The two ends of your actual workflow, wherever they sit on the chart.
3. The longest-serving person you can find. Almost always the most valuable conversation available to you.
4. The person who did your job before you, if they are still around and it is not awkward.
5. The other recent starter. Someone six months ahead of you remembers exactly what was confusing and can name it.

On the long-tenured person specifically: they carry the history. They know why the odd process exists, which past attempt at change failed and why, who fell out with whom. Ten years somewhere is ten years of context available no other way — and they are frequently delighted to be asked, because people mostly stopped asking.

How to ask without awkwardness: keep it short, specific and bounded. “I’m new and trying to understand how X actually works — could I get twenty minutes this week?” Twenty minutes is easy to say yes to. Then use it: turn up with questions, do not make them fill the silence, finish on time. Good ones — what does your team need from mine? What do we get wrong most often? What should I know that nobody will tell me?

Why does note-taking matter so much in the early weeks?

Because the volume is beyond what you can hold. Names, systems, acronyms, processes, logins, who owns what, why that thing is done that way — delivered in a fortnight, mostly once, mostly in passing. You will not remember it, not because you are bad at remembering but because you have no structure to attach it to yet. Facts stick when they hang off an existing framework, and you do not have one. What to write down:

• Every acronym and what it means. This list gets long and you will use it constantly.
• Names, with role and something to anchor them — who they work with, what they own.
• How to do things you were shown once. Step by step, including the obvious steps.
• Questions you did not want to interrupt for. Batch them and ask in one go.
• Observations about how things work here that surprised you. These are gold and they fade fastest — within a month it will all seem normal and you will not be able to reconstruct what struck you as odd.

Keep it somewhere you will actually search. The format matters far less than the habit.

How is starting remotely different?

Substantially, and most advice about starting a job quietly assumes an office. If you are remote or hybrid, understand what you are missing: an office delivers informal learning for free, continuously, without anyone intending it.

You overhear a call and learn how someone handles a difficult client. You see who walks over to whose desk, catch the corridor exchange where the decision actually gets made, register the mood of a room. None of it is planned. It just arrives.

Over video, nothing arrives. You see exactly what is scheduled and nothing else. Meetings start on the topic and end; there is no before and after. You cannot see who is irritated, who is close to whom, or what happened in the conversation preceding the one you are in.

So you have to manufacture it deliberately:

• Book more one-to-ones than feels necessary, earlier. In an office much of this happens by accident. Remotely, it happens only if scheduled. Fifteen or twenty minutes with everyone you work with, in the first month.
• Join calls a few minutes early and stay a minute late. The margins are where the informal talk lives. It is the closest available substitute for the corridor.
• Ask to observe. Sitting in silently on a meeting that is not strictly yours is the remote version of overhearing. Ask; people rarely mind.
• Read the archives. Old channels and threads are a written record of how decisions got made and who pushed back. This is genuinely a remote advantage — an office worker cannot rewind last year’s conversations.
• Use voice or video more than you would prefer. Text is efficient and terrible for building rapport. A five-minute call teaches you more about someone than twenty messages.
• Say out loud that you are struggling. Remotely, nobody can see you looking stuck. Confusion is invisible unless you narrate it. “I’ve been going in circles on this for an hour” is not weakness — it is the only signal available.
• Go in when you can, if hybrid. Front-load your office days into the first weeks, even beyond what is expected. The ambient learning per day in that period is worth more than it will be later.

Expect a remote start to take longer to feel normal. That is a property of the setup, not of you.

How do you get useful feedback before your first review?

Waiting for a scheduled review is a mistake. If something is going wrong you want to know in week three, when it is a small adjustment, not in month four when it has become a pattern someone has already formed a view about. The problem is that “how am I doing?” produces “yeah, good, all fine” almost without exception — too broad to answer honestly, and it puts the other person on the spot. Ask narrowly instead:

• “On that report — was the level of detail right, or would you have wanted it shorter?”
• “In yesterday’s meeting, should I have raised that or waited?”
• “Is there anything I’m doing that you’d want me to do differently before it becomes a habit?”
• “What would you want me to be doing more of by next month?”

These are answerable. They also make clear you want the real answer, which makes the next honest conversation easier.

When you get a criticism, take it plainly. Do not explain, do not justify, do not perform being crushed. “That’s useful, thank you — I’ll change that.” Handling correction well in the first weeks is itself a strong signal, and it makes people much more willing to tell you things.

What if the job is not what you were told it was?

Sometimes it genuinely is not. The role turns out to be another job entirely; the team is halved a month after you join; the manager who hired you leaves; the “strategic” post is mostly clearing an unmanaged backlog. This happens, and pretending otherwise helps nobody.

The difficulty is that in week three, normal disorientation and a real mismatch feel identical from the inside. Both produce dread on Sunday evening. Some rough distinctions:

Probably normal adjustment: you feel slow and stupid but you are measurably less lost than last week. The discomfort is about your own competence. You can see, in outline, what the job would look like once you can do it. Individual days are getting better even if the average is bad.

Possibly a real mismatch: the actual daily work is materially different from what was described, not just harder. Nothing improves across several weeks — you are not learning, because there is nothing structured to learn. You see behaviour that concerns you rather than merely confuses you. The people already there seem unhappy in a settled, resigned way. Or the specific thing you took the job for does not exist and nobody can say when it will.

Before concluding anything, give it time and gather information. Six weeks is too early for a confident judgement about most jobs; a quarter is more reasonable. Talk to people. Ask whether the current state is temporary — sometimes you have joined during an unusually bad stretch that everyone else knows will pass.

If it still looks wrong, the realistic options are these. Raise it directly with your manager, factually and without accusation: “When we discussed the role, we talked about X, and so far the work has been mostly Y. Can we talk about how that develops?” Sometimes this fixes it, because the gap was drift rather than deceit. If it cannot be fixed, you can decide to stay for a defined period to gain something specific and leave on your own timing. Or you can conclude it was the wrong move and leave a job that is not working — earlier is usually less costly than later, and a short stay explains far better than a resentful long one.

The one thing not to do is decide in week two. Almost everything feels wrong in week two.

How should you think about probation?

Calmly, and with the actual document rather than a general article. Probation arrangements differ enormously between countries and employers — how long they run, whether they can be extended, what notice applies, whether they carry any legal weight at all. Some are a genuine formal gate; some are an administrative leftover nobody looks at. General advice cannot tell you which yours is.

So read your contract and the staff handbook, and if either is ambiguous ask HR or your manager plainly — a normal question that does not signal you are worried. Find out the length, whether a review is scheduled, what happens if it is not formally confirmed, and the notice terms during the period.

Practically, the thing that helps most is not treating probation as a silent test. Ask your manager early what they are looking for and check in against it at least once before the end. Most probation problems come from an expectation that was never stated and was discovered too late to act on.

What does 90 days actually look like?

Loosely, and with the caveat that this is a shape rather than a schedule. Roles differ, and there is nothing wrong with being behind this.

First fortnight — absorb. Learn names. Write everything down. Get your access working. Attend more than you contribute. Ask the basic questions while they are free. Do not propose anything. Do small assigned tasks properly and on time — reliability is the only reputation available to you this early.

First month — map. Start seeing the informal structure. Have your one-to-ones. Find out what your manager is judged on. Work out what “good” looks like here by looking at real examples. Take on a first small useful piece of work. Ask for your first narrow feedback.

First quarter — begin contributing properly. Take ownership of something real. Start forming views, and now you can voice them — you have the context to know whether they hold. If you have spotted something worth changing, this is roughly when raising it stops being presumptuous, and it lands much better if you can say what you have already seen and who you have already asked.

What does the 90-day framing get wrong?

It implies a deadline. There is no deadline. Day 91 brings no assessment, and nobody has a calendar entry for it. The number comes largely from probation periods often running about that long, and from a general idea of a “first impressions” window. Both contain something true — early impressions are sticky, and there is a period where learning is expected. Neither means the clock stops.

In reality, most roles of any complexity take considerably longer to feel normal. Six months is common before you stop having to think about the basics. A year is normal in a complicated organisation, or a technical field with deep internal systems, or anywhere with a long project cycle where you have to see a full cycle before it makes sense. If you are at month four and still consulting your notes constantly, you are not behind. That is what month four looks like.

The genuinely useful part of the framing is only this: the first stretch is different from the rest of the job. You are permitted to be new. Use it — ask more than is comfortable, write everything down, meet people you have no immediate reason to meet, and resist the urge to prove yourself before you know what you would be proving.

Everything else comes later. Once you are established, doing work that is visibly yours, that is the ground from which you can start thinking about scope, progression, and eventually asking for a raise. But that conversation belongs to a version of you who knows how this place works, and in month two you are not that person yet.

Once you are established, the question changes from surviving to moving — and doing your current job well is not what does it. Learning to decline work without damage matters more than most new starters expect.

What a probation period can and cannot involve is set out by Acas, and it is worth knowing before you assume anything about yours.

If something goes wrong early, Acas explains how disciplinary and grievance procedures are meant to work.

Frequently asked questions

Is it normal to feel like a fraud in the first month?

Yes, and it is close to universal. You have been hired for judgement you cannot yet exercise, because exercising it requires context you do not have. The gap between what you were hired for and what you can currently do is uncomfortable and entirely expected. It closes. The signal to watch is direction — are you less lost than a fortnight ago? — rather than absolute competence.

Should I mention how things were done at my last job?

Sparingly, and never as a comparison. “At my last place we did it this way” invites the response that this is not your last place. Offering the same substance as a question works far better: “Have you tried doing X — or is there a reason that wouldn’t work here?” That gets you the history instead of a defensive reaction, and you often find out the idea was tried and failed for reasons you could not have guessed.

What if my manager is too busy to onboard me properly?

Common, and rarely personal. Take it on yourself: build your own list of people to meet and topics to understand, and ask your manager only for the things that genuinely need them — introductions, priorities, access. Use short, specific, pre-planned check-ins rather than open-ended time. A manager with no capacity will usually approve a plan you bring them even when they cannot make one for you.

How long should I wait before suggesting a change?

Long enough to answer three questions: why is it currently done this way, who set it up, and has anyone tried to change it before? If you can answer all three, the timing is probably fine regardless of the calendar. If you cannot, you are not ready, whatever week it is. In most roles that lands somewhere in the second or third month.

Should I socialise with colleagues even if I would rather not?

Some, early, more than you would naturally choose — then settle at whatever level suits you. The early period is when relationships form fastest and most cheaply, and the ones you build then make the rest of the job easier. You do not need to become anyone’s friend. Turning up occasionally, and being someone people have talked to outside a meeting, is enough.