- Kane Morgan
A product manager’s main role is to answer which software we should build, which parts we should build first. Making these decisions require having a broad understanding of user needs, business needs, organization culture and conventions (especially for enterprise or b2b tools) as well as technical effort and constraints. I love being a PM because it requires breadth of skills in many areas rather than deep technical understanding in just one area. PMs should have the ability to see the forest, abstract complex issues into achievable targets for the engineering team. PMs should have the ability to identify essential needs of users, should have intuition for how to interpret user research data, and distill actual essential needs from plethora of data that can suggest way too many things.