๐ Want to learn about Product Management? Check
One Month PM. We run cohort-based Live-Learning on PM Foundations, Growth PM, Web3 PM, AI PM, No Code, UX Design and Data for PM. Every program starts at โฌ99(+VAT).
Search for โProduct Managerโ roles on Linkedin and youโll find infinite variations: PM, PO, Program Managers, Project Managers, etc. But are they all the same? I picked 3 typical roles and tried to define what each one mean:
For this I am using 4 variables:
1๏ธโฃ What each role owns, i.e. youโre truly accountable for
2๏ธโฃ What each role uses for planning, i.e. what will you be working with every single day or week
3๏ธโฃ Who each role deals with on the day-to-day, i.e. which relationships will influence success in your job
4๏ธโฃ What success looks like for each role, i.e. how you can deliver and grow within the roleโs career pathย
Letโs dive in:
1๏ธโฃ Ownership:
- ๐๐ซ๐จ๐ฃ๐๐๐ญ ๐๐๐ง๐๐ ๐๐ซ๐ฌ own a project with a beginning and end, which when delivered should be done.
- ๐๐ซ๐จ๐๐ฎ๐๐ญ ๐๐ฐ๐ง๐๐ซ๐ฌ own a set of feature requirements and the delivery of epics, increasing the productโs capacity to add value.
- ๐๐ซ๐จ๐๐ฎ๐๐ญ ๐๐๐ง๐๐ ๐๐ซ๐ฌ own the product, the value delivered to users, and ultimately the P&L of that product for the company.
2๏ธโฃ Planning:
- ๐๐ซ๐จ๐ฃ๐๐๐ญ ๐๐๐ง๐๐ ๐๐ซ๐ฌ use a Gantt chart project plan, including dependencies, critical path and tasks associated with delivering a project.
- ๐๐ซ๐จ๐๐ฎ๐๐ญ ๐๐ฐ๐ง๐๐ซ๐ฌ use a backlog of issues, stories and tasks, normally created by a PM or by the team, that compose the Roadmap.
- ๐๐ซ๐จ๐๐ฎ๐๐ญ ๐๐๐ง๐๐ ๐๐ซ๐ฌ use a Product Roadmap, outlining the narrative, opportunities and solutions that more likely get the product to its goals.
3๏ธโฃ Relationships:
- ๐๐ซ๐จ๐ฃ๐๐๐ญ ๐๐๐ง๐๐ ๐๐ซ๐ฌ deal with every stakeholder assigned to the project. If youโre not contributing, youโre out of their scope.ย
- ๐๐ซ๐จ๐๐ฎ๐๐ญ ๐๐ฐ๐ง๐๐ซ๐ฌ deal with engineering, design and product managers responsible with executing on the product
- ๐๐ซ๐จ๐๐ฎ๐๐ญ ๐๐๐ง๐๐ ๐๐ซ๐ฌ deal with stakeholders, customers, and everyone building product, guaranteeing alignment between the decisions and value
4๏ธโฃ Success:
- ๐๐ซ๐จ๐ฃ๐๐๐ญ ๐๐๐ง๐๐ ๐๐ซ๐ฌ succeed when they deliver the shortest critical path and the project on time
- ๐๐ซ๐จ๐๐ฎ๐๐ญ ๐๐ฐ๐ง๐๐ซ๐ฌ succeed when they have properly defined requirements, and a smooth path of features to production
- ๐๐ซ๐จ๐๐ฎ๐๐ญ ๐๐๐ง๐๐ ๐๐ซ๐ฌ succeed when they progress towards Product-Market-Fit, delivering retained, happy customers to the company
Hopefully this helps differentiate the roles and expectations. Even though I don't believe in the PO role, I respect that companies have their own cultures, but let's not make someone a PO and expect them to do the PM work.
Hey, Andre! Can you please elaborate on this piece from the very end of this article:
...I don't believe in the PO role...
Why don't you believe in it? Who then should do the PO tasks? etc. I'm really interested in your opinion. If you wrote about it somewhere already, please give me a link, as I couldn't find it.