Bridging the Gap: How to Improve Technical Expertise as a Product Manager

In the past few weeks, I had a insightful conversation with my engineering friends about the Metric Layer concept and its impact on the Data Industry. As we explored this topic, we began discussing the technical knowledge required for Product Managers (PMs) in general, and specifically for those in the Data Industry.

”This is a complex area that requires a lot of technical knowledge. I think you should improve your technical skills,” he said.

I was intrigued by his comment and asked, ”What specific technical skills should I acquire? How do I know I have enough technical knowledge for that area?”

It’s a common belief that PMs should have strong technical skills, but what constitutes enough technical knowledge for a PM position can be unclear. After reflecting on my own product experience, I’ve realized that there are a few crucial factors to consider when assessing this skill:

1. External Factors:
   • Product domain, or the specific industry or product that you are currently working on, or are interested in working on in the future
   • Project complexity, or the specific project within that product you are currently working on
2. Internal Factors
   • Your specialized PM type
   • Your PM level, or specific level within that product organization that we are currently at, or aspire to hold.

Product Domain

As a Product Manager, I often hear statements like ”Product X requires more technical knowledge and skills than Product Y”. However, in my experience, this comparison is often meaningless because each product has its own unique technical requirements. The fact that products are different doesn’t necessarily mean that one requires more or less technical understanding than the other - it simply means that the requirements are not the same.

To determine whether we have the necessary technical qualifications for a PM role, I recommend focusing on the technical concepts that are essential to develop and maintain that specific product. With this approach, we can assess our current knowledge and identify areas where we need to improve. For example, if we’re developing a mobile app, we need to have a good understanding of mobile platforms, user interfaces, and app performance. On the other hand, if we’re building a SaaS platform, we need to have expertise in cloud computing, APIs, and data security, etc.

I bet you might wonder, ”Aren’t APIs and data security more technically advanced than mobile platforms?” Yes, they may appear that way to those who haven’t studied them before. In my view, domain knowledge is the trait we can change. The most challenging aspects are those we haven’t had the opportunity to learn yet, rather than what we haven’t learned already.

Project Complexity

Even within the same product, the required technical expertise can vary significantly across different areas, or projects. Let’s take Holistics as an example. In my company, a project focusing on improving system security may require more technical knowledge and skills than one focused on enhancing user experience.

So, as Product Managers, we have to gain a deep understanding of the projects or areas we’re responsible for, including the technical aspects. This knowledge empowers us to make well-informed decisions, establish effective communication with our teams, and ultimately steer our projects and products toward success.

Here’s a friendly tip: If you ever catch yourself feeling a bit lost in the system design of your project or can’t quite grasp what the engineers are saying, it might be a sign to brush up on your technical skills.

PM Types

The truth is, not all PM roles are created equal. Holding a different perspective can pose challenges, potentially hindering your career progress. In an upcoming post, I’ll explore this concept more deeply to provide greater insight.

It’s worth noting that various PM roles may demand distinct skill sets, which may include differing levels of technical understanding. For instance, a Growth PM role may not necessarily require the same technical knowledge as a Core PM position.

PM Level

Lastly, it is important to note that the level of technical expertise required can also differ depending on the PM level you are in within the product. For example, a senior PM who oversees an entire squad or product area will need to possess more technical knowledge than a junior PM who focuses on a specific aspect of the product.

As a PM grows in their career, they will take on increasingly complex responsibilities and projects. This growth comes a greater need for technical knowledge and skills to effectively manage the product and team.

Sum up

To be a successful Product Manager, it’s important to have strong technical skills. However, determining the necessary technical knowledge can be complex. Based on my own product experience, there are a few internal and external factors PMs should consider. By focusing on those factors, PMs can develop a targeted plan to improve their skills and stay relevant in their roles.