The first ninety days set your reputation, and reputations are sticky. Most people spend the period trying to look busy. The better strategy is to spend it learning fast, building a small number of relationships properly, and shipping one visible thing.
Days 1–30: learn, do not fix
The strongest temptation in a new job is to point out what is wrong. Resist it for a month. You do not yet know which problems are ignorance and which are constraints someone already fought over and lost.
Understand how work actually flows. Where does a request enter the team, who approves it, where does it get stuck? Draw it on one page. If nobody has ever drawn it, that page alone will make you useful.
Meet people deliberately. Book fifteen minutes with everyone your work touches, including the people outside your team who receive your output. Three questions: what do you need from my role, what has gone wrong here before, and who else should I talk to? Take notes and refer back to them later — people notice.
Find out how you will be judged. Ask your manager directly, in week one: "What would make you say at the end of my probation that this hire clearly worked?" Write down the answer verbatim. Ask again at day 45 to check it has not moved.
Learn the vocabulary. Every organisation has internal terms, system names and acronyms. Keep a running glossary. It shortens your ramp-up more than any training course.
Days 31–60: deliver one visible thing
Pick a single deliverable that is small enough to finish, useful enough to be noticed, and clearly yours. A cleaned-up report, a documented process, a fixed recurring failure, a first customer win. Not a strategy document nobody asked for.
While you deliver it:
- Communicate progress before you are asked. A short weekly note to your manager listing what you did, what is next, and what is blocked. This is the single highest-return habit of the whole period, and most people skip it.
- Start raising observations, carefully. By now you have earned the standing to ask "is there a reason we do X this way?" Ask it as a genuine question. Half the time there is a reason.
- Check your calibration. Ask your manager at around day 45 for informal feedback. Do not wait for the formal probation review to discover you are off track.
Days 61–90: consolidate and set the next horizon
Finish and hand over the visible deliverable properly, with documentation someone else could pick up. Then propose what you will do next, framed against the thing your manager told you in week one.
Before the probation review, prepare a one-page summary: what you delivered, what you learned about the function, what you propose for the next quarter, and any support you need. Bringing that document changes the meeting from an assessment into a planning conversation.
The mistakes that actually cost people
- Criticising the previous person in the role. Everyone in the room worked with them.
- Going quiet when struggling. Managers forgive not knowing; they do not forgive finding out late.
- Rebuilding something before understanding why it exists.
- Over-promising in week two to prove enthusiasm, then missing it in week six.
- Ignoring the administrative parts — expenses, timesheets, mandatory training. Small failures here shape the impression of your reliability out of all proportion.
- Only building relationships upwards. The people who will actually determine whether your work succeeds are usually peers and the team next door.
If it is going wrong
Sometimes the job is not the job you were sold. Raise it early and specifically: "The role was described as X and the work has mostly been Y. Can we talk about how that settles?" Employers can often fix a mismatch in the first quarter that becomes unfixable at month nine. And if it cannot be fixed, finding out at day 60 is far better than at day 300 — including for how the role reads on your CV.