Three Common Questions on Improving Technical Knowledge for a PM

Last month, during the Performance Review sessions with my subordinates, discussions around improving technical knowledge came up more than one. It’s a common question among non-technical Product Managers: “What technical skills should I focus on? How do I know I’ve acquired enough technical knowledge for this role?“. While it’s widely believed that PMs should possess strong technical skills, defining what constitutes “enough” technical knowledge for a PM role can be unclear.

To be candid, there’s no one-size-fits-all answer to this question. Different companies can have different expectations and requirements for PM qualifications. Let’s delve into a couple of key questions on this topic based on my experience as a non-technical background PM:

Question 1: Do we need technical knowledge to become a Product Manager?

In fact, technical knowledge is not always a strict requirement, particularly in less-technical product domains, such as mobile applications for productivity tools or e-commerce platforms.

However, it’s crucial to note that lacking a certain level of technical understanding can prevent us from advancing our career. As Product Managers, we are responsible for steering a product from ideation to market launch and beyond. Insufficient technical know-how can impede problem-solving, decision-making, and effective communication with development teams.

Question 2: As a Product Manager, how do I know I need to improve my technical knowledge?

One great way to tackle this question is by reflecting on your own performance. If you find that your lack of technical expertise is holding you back from fulfilling the PM role, it’s a clear signal to enhance those skills. Take me, for example: when I get stuck in certain projects, and constantly rely on the Product Leader and Technical Lead for decision-making, I know it’s time to level up my skills in those areas.

Additionally, don’t underestimate the power of peer feedback. Listen to what your colleagues have to say about your technical proficiency and be open to constructive criticism. If multiple feedback instances point to a need for improvement, it’s time to take action. I’ve personally experienced tremendous growth thanks to their insightful feedback.

Question 3: As a Product Manager, what specific technical skills should I acquire?

The specific technical skills required can vary widely depending on factors like industry focus, company culture, and the nature of the product itself. In some cases, especially for products with highly technical components or in tech-focused companies, a deeper understanding of technology may be non-negotiable. In other cases, particularly for more business-oriented products, a basic understanding may suffice, and other skills such as market analysis, user research, and project management may take precedence.

For those interested in improving their technical expertise, I’ve written an article on the topic titled How to Improve Technical Expertise as a Non-tech Product Manager here.

Final Words

In conclusion, while there are diverse opinions on the required level of technical expertise for a PM, there is no one-size-fits-all answer. What matters most is how your chosen path supports your advancement in the PM realm.

However, while prioritizing to enhance the technical skills is valuable, do not overlook the importance of refining other vital competencies such as communication, strategic thinking, and stakeholder management. By consistently sharpening our skillset, we pave the way for excellence in the ever-evolving landscape of product management.