The first ninety days set the reputation you spend the next two years living with. The mistake at both extremes is common: waiting to be told everything, or trying to redesign the system in week two. This is the middle path, and it is mostly about sequencing.
Month one: understand before you improve
Your first job is to build an accurate map. Everything you notice in month one that looks stupid probably has a history, and finding that history is the difference between a suggestion that lands and one that marks you out.
- Ask for a short call with everyone you will work with regularly. Ask what they do, what they need from your role, and what usually goes wrong.
- Keep a running list of everything you do not understand. Do not clear it too fast; it is the most valuable document you will own, and it becomes useless the moment you stop being new.
- Learn how work arrives, who prioritises it and what "done" means here.
- Find the person who knows where everything is. Every team has one.
In three months it will look obvious and you will have forgotten it ever did not. That list is also the best documentation the next new joiner will ever get.
Month two: ship something small and visible
Find a contained problem that someone is quietly annoyed about, and fix it properly. Not the biggest problem: a small one you can finish alone, that someone notices. This buys the credibility you will need later, and it teaches you how the place actually ships.
- A report someone rebuilds by hand every week.
- A step in a process that everybody works around.
- Documentation that is missing and that you needed in month one.
Month three: take ownership of something
By now you should be the person your team goes to for at least one thing. Choose it deliberately rather than accepting whatever drifts your way, and tell your manager you want it. Ownership is what turns a new joiner into a colleague.
The conversation to have early
In the first fortnight, ask your manager directly: what does good look like at three months, and how will we know. Written down and agreed, it removes almost all the anxiety of a new role, and it prevents the common failure where you work hard on the wrong thing.
| Ask | Why |
|---|---|
| What does success at 90 days look like? | Turns a vague probation into a checklist you can work against. |
| What should I not touch yet? | Saves you from the political landmine nobody warns new people about. |
| How do you prefer to hear about problems? | Every manager differs, and getting this wrong is the usual source of friction. |
Habits worth starting on day one
- Keep a weekly note of what you did and what changed because of it. It writes your review, and your next resume.
- Reply to what you were asked before adding what you noticed.
- When you are stuck, timebox it. Half an hour alone, then ask. Both extremes are expensive.
- Say what you are going to do, then do that. Reliability is the reputation that compounds fastest.
Key takeaways
- Month one is for mapping, not improving.
- Ship one small, visible fix in month two to earn credibility.
- Agree what success at ninety days means, in writing, in the first fortnight.
- Keep a weekly log; it becomes your review and your next resume.
Build the portfolio with people around you.
Udaan 90 is ninety days of structured, project-led learning with mentors and a cohort.
See Udaan 90