3 months into my PM role at Microsoft, I realized something shocking - I knew nothing about being a PM!
Sure, Iâd worked closely with PMs as a software engineer for years.
I admired their ability to bring clarity, align teams, and drive impact.
I thought transitioning into the role would be smooth.
But the reality? Itâs been humbling, messy, and incredibly rewarding.
Here are 5 lessons Iâve learned the hard way in my first 90 days as a PM:
1ď¸âŁ You donât need to have all the answersâfocus on asking the right questions.
As an engineer, I was wired to find solutions. But as a PM, the real skill lies in asking questions like:
⢠âWhat problem are we solving?â
⢠âHow does this align with our goals?â
⢠âWhat does success look like?â
The answers often unlock clarity for the entire team.
2ď¸âŁ Prioritization is your most powerful (and painful) skill.
Everything feels urgent, but not everything is important. Iâve learned to:
⢠Ruthlessly prioritize based on impact vs effort.
⢠Say ânoâ (or ânot nowâ) without guilt.
If everything is a priority, nothing is.
3ď¸âŁ Meetings are your battlefieldârun them like a pro.
Meetings can make or break progress. I now treat every meeting like a product:
⢠Set a clear agenda. Why are we here?
⢠Drive outcomes. Decisions > discussions.
⢠Follow up. A meeting without action items is just a chat.
A well-run meeting can save weeks of back-and-forth.
4ď¸âŁ Your engineers are your biggest alliesâbuild trust with them.
I spent my first month learning how to communicate with my dev team:
⢠Donât just drop requirementsâexplain the why.
⢠Be curious about technical challenges; it builds empathy.
⢠Celebrate small wins. It keeps momentum high.
A strong PM-engineering partnership is the backbone of a great product.
5ď¸âŁ The ambiguity never endsâembrace it.
Thereâs no perfect playbook in product management. Iâve learned to:
⢠Make decisions with incomplete data.
⢠Iterate quickly and learn from failures.
⢠Stay calm when things donât go to plan.
Ambiguity isnât a bugâitâs a feature of the role.
3 months in, Iâm still figuring things out.
Iâve stumbled, learned, and grown more than I expected.
But the one thing Iâm super happy about is that I love the role and made the right decision for myself!
To those whoâve been in my shoes:
Whatâs your biggest lesson in your first few months as a PM?
Iâd love to hear your thoughtsâletâs learn together!
Sure, Iâd worked closely with PMs as a software engineer for years.
I admired their ability to bring clarity, align teams, and drive impact.
I thought transitioning into the role would be smooth.
But the reality? Itâs been humbling, messy, and incredibly rewarding.
Here are 5 lessons Iâve learned the hard way in my first 90 days as a PM:
1ď¸âŁ You donât need to have all the answersâfocus on asking the right questions.
As an engineer, I was wired to find solutions. But as a PM, the real skill lies in asking questions like:
⢠âWhat problem are we solving?â
⢠âHow does this align with our goals?â
⢠âWhat does success look like?â
The answers often unlock clarity for the entire team.
2ď¸âŁ Prioritization is your most powerful (and painful) skill.
Everything feels urgent, but not everything is important. Iâve learned to:
⢠Ruthlessly prioritize based on impact vs effort.
⢠Say ânoâ (or ânot nowâ) without guilt.
If everything is a priority, nothing is.
3ď¸âŁ Meetings are your battlefieldârun them like a pro.
Meetings can make or break progress. I now treat every meeting like a product:
⢠Set a clear agenda. Why are we here?
⢠Drive outcomes. Decisions > discussions.
⢠Follow up. A meeting without action items is just a chat.
A well-run meeting can save weeks of back-and-forth.
4ď¸âŁ Your engineers are your biggest alliesâbuild trust with them.
I spent my first month learning how to communicate with my dev team:
⢠Donât just drop requirementsâexplain the why.
⢠Be curious about technical challenges; it builds empathy.
⢠Celebrate small wins. It keeps momentum high.
A strong PM-engineering partnership is the backbone of a great product.
5ď¸âŁ The ambiguity never endsâembrace it.
Thereâs no perfect playbook in product management. Iâve learned to:
⢠Make decisions with incomplete data.
⢠Iterate quickly and learn from failures.
⢠Stay calm when things donât go to plan.
Ambiguity isnât a bugâitâs a feature of the role.
3 months in, Iâm still figuring things out.
Iâve stumbled, learned, and grown more than I expected.
But the one thing Iâm super happy about is that I love the role and made the right decision for myself!
To those whoâve been in my shoes:
Whatâs your biggest lesson in your first few months as a PM?
Iâd love to hear your thoughtsâletâs learn together!