3 ms·
I don’t quite understand this piece. Perhaps there is some exaggeration in the use of product and product manager in titles, but I think it’s superior to previo
by prepend 9y ago
I don’t quite understand this piece. Perhaps there is some exaggeration in the use of product and product manager in titles, but I think it’s superior to previous exaggeration in project management.
It seems like this author has a complaint against product management, but doesn’t quite explain who hurt him or why.
The recommendation is for various different titles to serve in the role- analyst, domain specialist, etc. But I think this is just syntax sugar for product manager. I don’t think you go to school to be a product manager. I think you go to school for a skill and then add product management skills (eg, be an engineer, learn product management to design products and lead teams). This approach is better to the leader being a project manager with no domain expertise but able to track schedules.
I don’t think it’s important what you call the product leader, it’s more important that you have someone with knowledge of the user and the problem domain “in charge” rather than just a procedural person following the project.
Finally, you need a metaphor for all products to help with oeganization. I prefer product over project as it better puts the user as the measurer of value (ie, if user is happy then project is succeeding) rather than the project itself which frequently can continue on intertia for some time without any user value.