First 90 days
Things that you should do in your first 90 days at a new company:
- Create your 4 weeks plan with your manager.
- Introduce yourself to members of your team.
- Form a connection with key stakeholders; set up recurring 1-1s with them.
- Get a peer/buddy to help you get onboarded. If you don’t have one, ask your manager to nominate someone.
- Get your hands dirty asap.
- Take ownership; don’t wait for things to come to you.
- Your reputation will be made in the first 90 days. People generally form opinions quickly. Coming to meetings late? People will remember. Put your best foot forward.
- Don’t be invisible. Find the biggest problem (that you can take off someone’s plate) and fix it. Ideally that someone should be your manager. Again, just ask; don’t wait for your manager to come to you. People love doers.
- Get started with some process work till you are ready to pick your first major project. The first PM intern in my team, who eventually ended up joining the team, created our PM onboarding plan that I still use today to onboard new members. My own first project was to create a bunch of dashboards to cut down time needed for RCAs.
- Assume good intentions. People want to help, but you gotta make the first move.
- As part of your 90-day plan, clearly define success metrics with your manager.
- Set up 1-1s with not just your manager, but all key stakeholders you will be working with on a regular basis. People are generally busy, so what you can do is to have an initial intro meeting and request a monthly meeting where you can update them on your work.
- Ask your manager this question: Assume after 6 months I have failed in my role. What could have gone wrong? Work with your manager on how you can combat these risks.
- Understand the culture of the team: Do they prefer email over slack? How do they escalate problems? Is sending a Slack message on a Saturday night frowned upon?
- Don’t try to change the culture from Day 1. I have lost count of the times I said “but we used to do X like Y in my previous company Z” when I joined Gojek, before a dev reminded me that if what I did in my previous companies was perfect and everything was golden, then I would not have switched jobs. Burn. Learn why things are the way they are before you recommend any change. The way we run standups today is not the same as how we did it 2 years back. New people came, brought fresh ideas with them. We tried variations as experiments. Kept the bits we liked.
- Ask: What are things that no one talks about but knows because they are implicit? If you form a good relationship with your peers they will let you know.
- Understand the working style of your manager and other key stakeholders.
- Understand the key priorities for the company and your team; what are P0s for this quarter?
- Work with your manager to write an intro email to the company announcing you. Ideally, you should write a self-intro mail and then ask your manager to send it. Make their life easy.
- Get added to all Slack/Google groups.
- If you are a new PM then read a lot of the existing PRDs, tech and design specs, and charter docs.
- Understand how the company sets goals.
- Ask what are the: must-dos, should-dos, and nice-to-dos. Example. If you are a PM in my team then you have to attend all standups and IPMs. They are non-negotiable; must-dos. If there is a tech huddle for your project then attending it is a should do. You may choose to skip it only if it is clashing with another must-do meeting. Attending tech implementation discussions is a nice-to-do.
- Shadow other PMs (if you are a PM). If a new PM joins my team, I ask them to join the project channels of other PMs in my team, attend their standups and IPMs. Learning through osmosis is great.
- Work on multiple parallel tracks of learning. For my PMs in my team, I encourage them to work on the following tracks:
- 4 weeks plan (standard for any new joiner)
- short term
- medium term
- long term
- Learn how we execute
- Get context on the onboarding project
- Understand the tech stack
- From Pranav: Give your team a few quick wins. This helps you understand the product better and builds the team’s confidence if you.
- From Pranav: Understand what motivates individuals in the team - why are they here?
Read: The first 90 days(an amazing book) that I have gifted to my friends joining a new team or company.