Product Manager Debate
Cluster centers on debates distinguishing product managers from project managers, questioning their value, roles, and necessity in software teams, with many arguing engineers can handle product decisions without dedicated PMs.
Activity Over Time
Top Contributors
Keywords
Sample Comments
OP is talking about product mangers. Why are there so many comments about project managers
Exceptional engineers can PM their own work. For everyone else there's product management.
Sounds a lot more like a project or program manager than a product manager.
Oof. Dunno about "product manager == leadership"
Thats what Product Managers and Project Managers do ..
What you're describing is a role fulfilled by a product manager, rather than a traditional people manager.
Iām curious about which type of products you have been working on and what type of product decisions the engineers you have been working with have done. Because your experience is the opposite of mine. Engineers who understand anything to business and product management are extremely rare. And people who are good at it and genuinely interested in it usually move to this role (or create their company!). Also, as described in this article (interesting read btw), a lot of PMs are actually just proj
It sounds like you had a project manager, not a product manager. A good product manager is very valuable.
Product Managers today are many times attempting to be shitty tech leads rather than actual product managers, which is a completely different job. If a product manager has more than a superficial opinion about what engineering is doing, then they are not a product manager (more than by title). They should feed the why and when to engineering, nothing more. When do the market opportunities exist and why? Collect and feed the data to engineering (as well as other stakeholders). They should not be
Many companies have a separate "Product Manager" role for that business, so that the brilliant engineers can brilliant SENIOR implementors. Have a dedicated professional worry about the customer impact, product requirements, etc., along with other non-programming tasks that many developers understandably prefer not to get bogged down in.