The first three months in a new job are the only time you will ever be expected to know nothing. That makes them unusually valuable, and unusually easy to waste.
Most people arrive wanting to prove they were the right hire. So they work long hours, say yes to everything, and try to look useful before they understand how anything works. It feels productive and it is the most common way to start badly. The people who settle in fastest do almost the opposite: they spend their early weeks learning, pick one small thing to do well, and get to know more people than their job strictly requires.
This guide covers the whole period — what to sort out before your first day, what to learn in week one, how to find the priorities that actually matter, how to deliver an early win, how to pass probation, and how to tell if the job is not what you were promised.
What the First 90 Days Are Really For
It helps to know what you are being judged on, because it is rarely your technical output. In most jobs the early assessment comes down to three things.
- Can you learn quickly? Nobody expects you to know the work yet. They are watching how fast you pick things up and whether they have to explain the same thing twice.
- Are you easy to work with? Can people give you information, ask you for things, and get a straight answer? This matters more than most new starters realise.
- Did you deliver anything? Not something large. Just clear evidence, by about month two, that you have started contributing rather than only absorbing.
Notice that two of the three are about behaviour rather than skill. A new starter who learns fast and is pleasant to deal with gets a great deal of patience on the technical side. The reverse is not true.
Before Your First Day
A little preparation removes most first-day stress, and the practical things are the ones people forget.
Confirm the simple details in advance: what time to arrive, where to go, who to ask for, whether you need identity documents, and what people actually wear. Asking these questions is normal and nobody minds answering them.
Then do a small amount of reading. Look at the company's recent announcements, its main products or services, and the public profiles of the people you will work with closest. Fifteen minutes is enough. The aim is not to impress anybody with research; it is to arrive with enough context that the first conversations make sense.
Finally, sort out your own logistics before you start — the commute, childcare, anything that has to change. The first week is a bad time to be solving those for the first time.
Your First Week: Learn, Do Not Perform
The temptation in week one is to look capable. Resist it. Your only real job this week is to understand how things work and who does what.
Ask more questions than feels comfortable. There is a short window where every question is expected and forgiven, and it closes faster than people think. A question that is completely normal in week one is slightly awkward in month three. If asking in front of a room is the part you find hard, our guide to speaking up in meetings covers how to get into the conversation.
Write everything down. Names and roles, systems and logins, how a piece of work moves from request to finished, the words the company uses for its own processes. You will be given far more information than you can hold, and a notebook means you only have to ask once.
Say yes to introductions, and keep your opinions to yourself for now. You will spot things that look inefficient in your first fortnight, and some of them genuinely are. But you cannot yet tell which are mistakes and which are solutions to problems you have not met. Note them down and raise them in a month, when you will know which is which and people will be far more willing to listen.
Questions Worth Asking Early
Good questions do more than gather information. They tell people you are thinking about the right things. These are worth asking in your first week or two.
- "What would a good first three months look like to you?" Ask your manager this directly. Their answer is the standard you will be measured against, and it is often different from your job description.
- "What are the most important things happening this quarter?" This tells you which work carries weight and which is routine.
- "Who should I get to know outside this team?" Managers usually name people you would never have found on an organisation chart.
- "What do new people here usually get wrong?" Ask a colleague rather than your manager. The answers are specific, honest and genuinely useful.
- "How do you prefer to be kept updated?" Some managers want a weekly summary, others want nothing until something is wrong. Guessing this causes a surprising amount of friction.
Weeks Two to Four: Find the Priorities That Actually Matter
Every job has a written description and a real one. By the end of the first month you want to know the real one.
The fastest way to find it is to write down what you believe your top three priorities are, show the list to your manager, and ask them to correct it. This takes ten minutes and it is the single most useful conversation of your first month. People are often surprised by how much the list changes.
Once you know the priorities, turn them into something you can actually check. "Get up to speed" is not a goal; "handle the weekly report on my own by the end of month two" is. The SMART goal builder will turn a vague intention into a target with a date and a measure attached.
If you want a fuller structure for the whole period, the career development plan builder maps out a 30, 90 and 180-day path, and our sample career development plans show what a finished one looks like. Both work just as well for settling into a role as for planning a move out of one.
Deliver One Small, Visible Win
Somewhere around weeks four to eight, finish something. It does not need to be impressive. It needs to be finished, useful, and noticed.
Small and complete beats large and ongoing, because an unfinished project proves nothing while a small finished one proves you can be relied on. Fixing a process that irritates everybody, taking over a task your team has been avoiding, or writing the documentation that has never existed are all ideal early wins. They are low risk, genuinely appreciated, and entirely within your control.
Avoid two traps. Do not pick something so large that it is still unfinished at your probation review. And do not quietly reorganise something that belongs to somebody else, however much it needs doing — being new is not a licence to rearrange other people's work.
When it is done, mention it once, plainly, in a normal update. That is enough. Nobody likes a new colleague who announces every small achievement, but work that nobody knows about cannot help you either.
Get to Know People Beyond Your Own Team
Most new starters meet their immediate team and stop. That is a mistake, because a great deal of what you will need — information, approvals, favours, context — sits with people in other departments.
Try to have a short, friendly conversation with one new person each week for the first couple of months. Not networking in any formal sense; just fifteen minutes to understand what they do and how your work touches theirs. Ask how your team's work affects them and what usually goes wrong between you. People answer that question generously, and it is often the most useful thing you learn all month.
These conversations also teach you how the organisation really works, which is never quite what the chart suggests. Our guide to handling office politics covers how to read where decisions actually get made and how to stay out of trouble while you learn.
Set Your Working Pattern Before It Sets Itself
Whatever you do in your first month quietly becomes what people expect of you. Answer messages at eleven at night in week two and that becomes your normal. It is much easier to set a sustainable pattern now than to pull one back later.
This does not mean doing less. It means being deliberate about when you work and when you do not, and being reliable within those hours rather than permanently available outside them. Nobody notices a new starter who is consistently good between nine and six. Plenty of people notice one who burns out in month four.
Our work-life balance tips cover how to hold a pattern once you have set it, and if you are not sure what the culture expects, our guide to asking about work-life balance has the questions worth putting to colleagues as well as interviewers.
Close the Skill Gaps Quickly
Almost every new job involves something you cannot yet do. A tool you have not used, a process you have never run, a subject you only half know. Name these early rather than hoping they go unnoticed.
Saying "I have not used this system before, is there anything I should read or anyone I should sit with?" in week two is completely unremarkable. The same admission in month five is a problem, because by then you were supposed to know. New starters are given enormous latitude to be ignorant and almost none to have been hiding it.
For gaps that need real study rather than a short explanation, our guide to learning a new skill while working full time covers how to make progress in short evening sessions without exhausting yourself in a month when you are already tired.
Probation and Your First Review
Many jobs have a probation period, often three or six months, during which either side can end the arrangement with little notice. It is worth knowing the length of yours and what it actually involves, because the terms vary a great deal between employers and countries. Your contract or staff handbook will say.
Passing is usually straightforward if you have done the things above, but two habits make it considerably safer. Ask for feedback before anyone offers it — a five-minute "is there anything you would like me to do differently?" at the end of month one removes nearly all the risk of a nasty surprise at month three. And keep a short private note of what you have finished, which takes two minutes a week and makes the review conversation much easier.
If the review does not go well, that is recoverable far more often than it feels at the time. Our guide to handling a bad performance review covers how to separate fair criticism from unfair, how to respond in writing if you need to, and how to build a plan that visibly changes things.
If the Job Is Not What You Were Promised
Occasionally the honest conclusion is that the role was described inaccurately. The work is different, the team is not what you were shown, or something you were assured about turns out not to exist.
Give it a little time first. Weeks one to four feel strange in every job, and plenty of people who nearly resigned in month one were perfectly happy by month four. Genuine problems look different from ordinary discomfort: a duty you specifically asked about and were told was not part of the role, pay or hours that do not match what was agreed, or behaviour you are not willing to work around.
If it is real, raise it clearly with your manager once before deciding anything. Some of these are misunderstandings and get fixed. If nothing changes, leaving early is not the disaster it feels like, and a short stay is easier to explain than most people fear — our guide to writing a CV that gets interviews covers how to present it without it looking like a problem.
Mistakes New Starters Make
- Trying to prove yourself in week one. Nobody expects output yet, and rushing it mostly produces work that has to be redone.
- Saying yes to everything. It feels helpful and leaves you with a collection of jobs nobody else wanted, none of which were your actual priorities.
- Comparing everything to your old employer. Occasionally useful, quickly tiresome. "At my last company we did it this way" wears out fast.
- Hiding confusion. Pretending to follow something you did not understand costs far more later than the small embarrassment of asking now.
- Only talking to your own team. It is comfortable and it leaves you without the relationships that make the job easier in month six.
- Waiting to be told what matters. Some managers never spell it out. If nobody has told you what a good first three months looks like, ask.
None of this requires working late or being the most talented person in the room. The first ninety days reward something much simpler: learn fast, ask early, finish one useful thing, be easy to deal with, and make sure you and your manager agree on what the job actually is. Do that and the rest of the role tends to look after itself.