I think a question like ‘how would you define a PMs job’ is not easy to answer because a PMs job is often defined by its versatility and diverse scope of work based on timeline or pressures. Conventionally, we define what jobs are by the technical tasks or obligations the worker must complete. I think a PMs job is more defined by a responsibility over a business segment (product). There is not a specific set 0f technical abilities or tasks that every PM across every industry must complete, but there is a core responsibility over the product. That responsibility pushes the PM to pivot from checking in with the engineering team, to improving morale with the sales team, to even hopping in as a UX designer: there is really no segment under a product that is outside the PM’s scope.
This begs the question: does the PM title really fit the role of the PM? Might it be better to break the role down in several?
