3 ms·
I know it has been fashionable to have one, but why does a company truly need a Chief Product Officer anyway? Is it for creating revenue-generating ideas? Users
by OutOfHere 3y ago
I know it has been fashionable to have one, but why does a company truly need a Chief Product Officer anyway? Is it for creating revenue-generating ideas? Users essentially pay when they believe they receive immense value for their money. I don't think you need a CPO to tell you what will give users this value. You could just talk to the users or see their error logs if you don't already understand their pain. As I see it, the CPO role is just another parasitic prune-worthy role that delivers negative value because they keep piling on substandard new products at the expense of sacrificing the quality of existing products.
- wand3r 3y agoI'm speaking off the cuff but intuitively, like all roles, it obviously depends on the company and caliber of the person. What you are saying is kind of like, why does anyone need a CEO, employees generally know what to do. Maybe LEGO doesn't need a CPO because its a mature company with a brand and well defined product portfolio but a startup in a nascent technology needs someone with vision to design the experience and offering the company produces to meet customer needs. Edit: Also, this is seemingly who would "talk to users" and talk to engineers looking at the "error logs" as well as many other touch points to determine an overarching strategy.
- OutOfHere 3y agoCPOs never ever look at any error logs. In fact, if anything, by always pushing for new products, they come in the way of stabilizing current offerings. As I see it, the game of C*Os is to show they're driving change, but they bail with their golden parachute when the results of their changes turn out to be not so golden, and the company is made worse for having had them.