AMA: Salesforce Senior Director of Product, Einstein AI, Deepak Mukunthu on Technical Product Management

The role of a technical product manager (TPM) is different from other product managers in that TPMs typically have a deeper technical background and are responsible for managing the development and implementation of technical products or features. TPMs work closely with engineering teams to ensure that product features are designed and built in a technically feasible way and that they meet the needs of both customers and the business. They are responsible for understanding the technical requirements of a product or feature, and for making decisions about the technical direction of the product. Product managers, on the other hand, may be responsible for managing the development of non-technical products, such as consumer goods or services. They may not have the same level of technical expertise as a TPM, but they are still responsible for understanding the needs of the customer and the business, and for managing the product development process from ideation to launch.

Aspiring technical product managers should consider developing the following skills and background: 1. Technical expertise: A strong understanding of technology and the ability to communicate effectively with technical teams is essential for technical product managers. Familiarity with coding languages, software development methodologies, and industry-standard tools can help aspiring technical product managers gain credibility with their teams. 2. Customer empathy: Technical product managers should have a deep understanding of their customers' needs and pain points. They should be able to conduct customer research and use this information to inform their product development decisions. 3. Business acumen: Technical product managers should have a good understanding of the business context in which their products operate. This includes understanding the competitive landscape, market trends, and financial metrics. They should be able to use this information to make informed decisions about their product development priorities. 4. Analytical skills: Technical product managers should be able to analyze data, draw insights from it and use it to make informed decisions. 5. Communication skills: Technical product managers need to be able to communicate effectively with both technical and non-technical stakeholders. They should be able to explain complex technical concepts in a way that is easy for non-technical stakeholders to understand, and be able to negotiate and influence stakeholders to achieve their product goals.

Based on my experience, here are some common mistakes I've seen new TPMs make: 1. Focusing too much on features and not enough on customer needs: It's easy to get caught up in building new features, but it's important to remember that the features you build should ultimately solve customer problems. 2. Not prioritizing effectively: New TPMs may struggle with prioritizing effectively, leading to delays or features that don't deliver the desired impact. 3. Lack of communication: Not communicating effectively with your team and stakeholders can lead to misunderstandings, missed deadlines, and other issues. 4. Micromanaging: It's important to trust your team to do their jobs and avoid micromanaging their work.

Both Technical Product Managers (TPMs) and Product Managers (PMs) have important roles to play in product development. The primary difference between the two is that TPMs typically have a stronger technical background and are more focused on the technical aspects of product development, while PMs tend to have a broader focus on the overall product strategy, market positioning, and customer needs. Individuals who have a strong technical background and enjoy working closely with development teams may be better suited for a Technical Product Manager role. TPMs need to be able to understand complex technical issues, communicate effectively with developers, and have a good understanding of the development process. Individuals who have a broader focus on the market and customer needs, and enjoy working closely with cross-functional teams such as marketing, sales, and customer support, may be better suited for a Product Manager role. PMs need to be able to identify customer needs, prioritize features based on market demand, and develop a product roadmap that aligns with the company's overall strategy.

Being the most technically advanced person on the team is not necessarily a prerequisite for a technical product manager to be helpful. While technical knowledge is certainly important, the role of a technical product manager involves more than just technical expertise. They are not expected to do everything a software engineer would do. Here are some ways in which a technical product manager can be helpful even if they are not the most technically advanced person on the team: 1. Customer empathy: Technical product managers bring a deep understanding of their customer's needs and pain points. They conduct customer research and use this information to inform their product development decisions. 2. Strategic thinking: A technical product manager can help the team think strategically about the product and its goals. They can help prioritize features and ensure that the product aligns with the company's overall strategy. This involves understanding the market, the competition, and the needs of the users. 3. Product roadmap: A technical product manager can help create a product roadmap that aligns with the company's overall strategy. They can work with stakeholders to prioritize features and ensure that the product is delivered on time. 4. Clear communication: A technical product manager can bridge the communication gap between the technical team and non-technical stakeholders. They can help translate technical jargon into language that non-technical stakeholders can understand and vice versa. This can ensure that everyone is on the same page and can contribute to the project in a meaningful way. 5. User research: A technical product manager can help gather user feedback and conduct user research. They can work with the UX team to understand user needs and ensure that the product is designed with the user in mind.

The day-to-day activities of a Technical Product Manager (TPM) can vary depending on the company they work for, the products they are responsible for managing and the stage of the product lifecycle. Here are some common tasks that a TPM might perform: 1. Gathering requirements and defining product features 2. Conducting market research and analysis 3. Collaborating with cross-functional teams 4. Prioritizing product features and issues 5. Writing product specifications 6. Participating in sprint planning and reviews 7. Testing and validating products 8. Managing product releases 9. Monitoring product performance and metrics 10. Keeping up with industry trends and emerging technologies

Here are some of the key competencies that a technical PM should possess: 1. Understanding of data and analytics concepts: A technical PM should have a basic understanding of data and analytics concepts such as data modeling, data warehousing, data governance, and data visualization. They should be able to understand the data requirements of the project and communicate with data analysts and data scientists. 2. Ability to read and interpret data: A technical PM should be able to read and interpret data to gain insights into the project's progress and performance. They should be able to use data to make informed decisions about the project and communicate insights to the project team. 3. Familiarity with data analytics tools: A technical PM should be familiar with data analytics tools such as Excel, Tableau, and SQL. They should be able to use these tools to analyze and manipulate data and generate reports. 4. Understanding of data security and privacy: A technical PM should have a basic understanding of data security and privacy requirements. They should be able to ensure that the project complies with relevant data security and privacy regulations. 5. Collaboration with data analysts and data scientists: A technical PM should be able to collaborate effectively with data analysts and data scientists. They should be able to communicate project requirements and understand the technical constraints of the project. Overall, a technical PM should have a basic level of data and analytics competencies to manage projects that involve data and analytics effectively. They should be able to understand data requirements, analyze data, and collaborate with data analysts and data scientists to ensure the project's success.

The ideal product manager-to-engineer ratio can vary depending on the nature and complexity of the products being developed, the size and stage of the organization, and other factors such as the development process, company culture, and resources available. However, a common rule of thumb is to aim for a ratio of 1 product manager to 8-10 engineers. This ratio provides enough product management oversight and guidance to the engineering team while allowing engineers to have enough autonomy and ownership over their work. As the organization scales, this ratio can be adjusted to maintain the appropriate level of oversight and support for the engineering team.