Building Confidence as a New PM
28 May, 2021

Sr. Product Manager at Box
Problem
When I joined a new company as a PM I initially thought it was going to be pretty straightforward as the team already had an existing roadmap. Plus, most of the engineers in my team had more than ten years of experience. I still found myself in a difficult position. Why? The reason is that I soon realized that just because we had a roadmap, didn’t mean it was the right one. I initially assumed that the engineers knew what they were doing. To pinpoint the problem, it was: how would I know what to build? Plus, how do I gather the confidence to talk to and convince somebody who knows much more than me?
Actions taken
In terms of action, I did not hesitate to talk to our VP about how I should deal with the situation. The outlook that he gave me was something that will always stick with me. He said, “We hired you precisely because we wanted to bring in a new perspective.” This boosted my confidence and I started visualizing the product from my lens instead of what had historically been there.
Next, I spoke to as many stakeholders as I could. Starting from other product managers, engineers, support team, QA, sales, etc. Needless to mention that I also communicated with our customers. We talked to customers about issues they were facing and gradually iterated on the roadmap we had. That’s all I did for a month or two; I gathered information and perspective from all sides.
The third action was identifying small areas of the product that needed change and improvement. Intrinsically, identify small areas of strengths and weaknesses, make changes, and measure the impact as we proceed. You don’t have to make big sweeping changes to make an impact. This was crucial in bringing the team along with me and building my credibility.
Lessons learned
- Know your strengths as a PM. PM’s have a breadth of knowledge that no one else in your company has. Always understand and leverage your individual talents.
- Never be afraid to try new things. Try to be as transparent as you can. Be cognizant of the fact that things may not happen precisely as you planned them. If you already have an existing roadmap that you have no idea about, it does not mean you have to execute it.
Discover Plato
Scale your coaching effort for your engineering and product teams
Develop yourself to become a stronger engineering / product leader
Related stories
3 February
This was not a high point in my career. It's a story of single metric bias, how I let one measure become a 'source of truth', failed to manage up and ended up yelling at one of the most respected engineers in my team.

Alex Shaw
Chief Technology and Product Officer at Hive Learning
10 December
Supporting principles on why being data led (not driven) helps with the story telling.
Vikash Chhaganlal
Head of Engineering at Xero
30 November
When you grow fast, its normal to focus on Value delivery aka "Feature Releases". Too many releases too soon will inevitably lead to piling tech debts and before you know, inefficiencies creep in, performances goes down, and ultimately any new release takes too long. Sounds familiar? Then read on..

Ramkumar Sundarakalatharan
VP - Engineering at ITILITE Technologies
14 October
Teams have tremendous impact on the products on they build. T.E.A.M definition - Together Everybody Achieves More is true. A collaborative and empowered team builds great product versus the good ones.

Praveen Cheruvu
Senior Software Engineering Manager at Anaplan
13 October
A high performance team refers to “ a group of goal-focused individuals with specialized expertise and complementary skills who collaborate, innovate and produce consistently superior results.”

Praveen Cheruvu
Senior Software Engineering Manager at Anaplan