|
|
|
|
|
by opportune
2159 days ago
|
|
I guess I have a hard time understanding how you would answer “what” questions in that position other than simply doing what customers asked. If you really didn’t need to add any new features other than what customers directly asked for I can kinda see how it would work. But how would you know how to advise customers on workarounds/that they are using the product wrong, or a future product roadmap, if you can’t see the product from a customer standpoint?
I’m sure you could be an effective project manager in that position but to lead a product’s development without fully understanding how it’s used is a bit suspect to me. |
|
My guess is--haven't really been a PM for other types of products--is that the relationship between the PM and engineering is probably different. I would certainly never have considered that I "led product development." And, yes, I did bring in requirements both from customers directly and from sales and I worked closely with engineering on defining the product. But actually--remember that product development cycles of big hardware were relatively long--after the initial requirements and basic design were worked out for a given system model--there often wasn't a huge amount for me to do until closer to launch when a lot of selling/marketing/pricing/etc. tasks had to get done. (I tried to plan my longer vacations during the quiet periods.)
To be clear, I wasn't just sitting around for months at a time as I was usually handling multiple products and involved in exploring new areas.
>if you can’t see the product from a customer standpoint?
As far as customers are concerned, big systems have a lot to do with specs, features, pricing, upgradability, etc. (And the availability of software.) They're not even maintaining them themselves.