The first three months in a job shape how colleagues see you for years. Not because you are expected to transform anything, but because people form opinions quickly about whether you listen, deliver and are easy to work with.
Here is a plan that works whether you are starting your first job or your fifth.
Weeks 1 to 2: learn how things really work
Your only job at this stage is to understand the place.
- Meet people. Ask for 20 minutes with everyone you will work with. Ask what they do, what they need from your role, and what frustrates them.
- Learn the systems. Where does the data live? Which tools matter? What is the approval process?
- Read the history. Old project documents and meeting notes explain why things are the way they are.
- Write everything down. You will never have fresher eyes for what is confusing, and that document becomes useful when the next person joins.
- Ask what good looks like. Request examples of excellent work from your role, and keep them.
Resist the urge to suggest improvements in week one. Observations land much better once people know you understand the context.
Weeks 3 to 6: find the first win
Look for something small, visible and genuinely useful: a report nobody has time to produce, a process that breaks every month, a backlog that needs clearing.
Pick something you can finish in two or three weeks, agree it with your manager, and deliver it properly. An early, complete win buys you credibility for bigger things.
At the same time:
- Confirm your priorities with your manager in writing after each check-in.
- Learn the team’s rhythms: when decisions are made, who needs to be consulted.
- Start a record of what you deliver. It becomes your case at review time, as described in our guide to asking for a promotion.
Weeks 7 to 12: take ownership
Now you can take responsibility for something ongoing: a recurring report, a customer segment, a part of the product.
- Offer improvements, framed as questions rather than verdicts: “I noticed we re-key this data twice. Is there a reason, or would an export work?”
- Build relationships outside your immediate team.
- Ask for feedback explicitly: “What would you like me to do differently?” Most people will not volunteer it.
- Check your 90-day goals against what you were told at the start, and raise any gaps early.
Habits that build trust quickly
- Do what you said, when you said. Reliability outweighs brilliance in the first months.
- Flag problems early. A late warning costs far more than an awkward early one.
- Write clearly. Short updates, clear decisions, no jargon.
- Say “I don’t know yet, I’ll find out.” It is a strength, not a weakness.
- Learn names and remember context. People notice.
Working with AI tools in a new job
Find out the rules before you use anything. Ask what tools are approved, what data can go into them, and who reviews AI-assisted work. Then use them where they help and verify everything, as described in our guide to AI skills employers want.
If something feels wrong
Occasionally the job is not what was described. Give it a fair chance, raise specifics with your manager, and keep notes. If it is genuinely misrepresented, our guide on what to do when you hate your job covers how to plan your next step calmly.
Frequently asked questions
How much should I speak up in early meetings?
Contribute, but weight your words toward questions in the first few weeks. Ask about things you genuinely do not understand; it signals attention rather than ignorance.
What if I was hired to change things?
Then your mandate is explicit, and you should still spend the first two weeks listening. Changes land better when you can explain why the current way exists and what it costs.
Should I keep applying elsewhere after starting?
Generally no, unless the job turns out to be fundamentally different from what you accepted. Give it the first 90 days, then reassess with our guide to career goals.
