All related (5)
Navin Ganeshan
Head of Driver Products, Amazon Relay, AmazonMay 30

In a word, abstraction. A technical PM is usually NOT the most advanced technical person on a team. However, they are able to break through sufficient tech layers to be able to contextualize the tech in the overall product development. They are able to draw the bigger picture of how components fit together, what technology elements are critical. And how to think about investment in each technical area - sucvh as build/buy/partner. In this way, they're not competing with others on technical know-how, but using it as an essential area of overlap to allow easier communication and collaboration.   

A techical PM is simply able to engage in more meaningful planning, discussions and collaboration on technology areas with other counterparts. 

 

Devika Nair
Director of Product, Oracle Cloud Infrastructure, OracleJuly 20

In my opinion, you can be successful in any role by not having the expertise if you recognize it and are willing to learn. The product manager is generally not the most technically advanced person on the team, but they bring in other expertise and experience to the team (e.g., customer data, market insights, etc).

What has helped me is identifying key experts in the organization and leaning into them. I've usually not found a single technically "advanced" person on any of my teams. Different members of the team might have expertise in different areas. PMs with the expertise to identify these members and leveraging their knowledge can be successful in any role.

Vasanth Arunachalam
Director, Technical Program Management, Meta | Formerly Microsoft
It could be a combination of any of these things - * Look at data (dashboards, customer feedback channels, internal partner team feedback) to check progress (on product success, platform performance) -Take any actions necessary (filing bugs, resolving a SEV) * Supporting your cross functional team to deliver on roadmap projects -Brainstorm product and technical solutions. -Sprints, design reviews, code reviews -Removing blockers * Look at data to proactively surface opportunities, hot spots, technical bottlenecks etc * 360 communications often tailored meticulously fo...
Navin Ganeshan
Head of Driver Products, Amazon Relay, Amazon
(Reposting this from a related question)  A technical product manager at Amazon is generally referred to as a Product-Manager-Technical (PM-T). A PMT can have ownership over a product, a functional area or even a program, but their primary focus is on formulating the vision, the strategy and roadmap for that area. They are also ultimately responsible for the end metrics of adoption, quality and effectiveness of the features they deliver. They are also the primary customer champions synthesizing their current pain-points, as well as anticipating future needs. They develop concept document...
Devika Nair
Director of Product, Oracle Cloud Infrastructure, Oracle
Two constant challenges for me in any product role has been finding the right way to say no. This could be to your customers asking for a particular feature or your organization that has decided to prioritize certain aspects differently.  The best way to overcome this challenge is by having your facts and data clear. For example, it is easy to convince leadership about your prioritization rationale if you have data to back up your claims, whether it is potential revenue or customer impact.