4 ms·
I've worked with quite a few POs over the years; good and bad. We used to call them project managers and it's more or less the same thing. As soon as you are as
by jillesvangurp 7y ago
I've worked with quite a few POs over the years; good and bad. We used to call them project managers and it's more or less the same thing. As soon as you are asking when questions instead of what questions, you are managing a project.
One thing that I've learned over the years is that product management is often effectively a junior management position and actually should not be a management role at all.
That puts things in perspective in terms of their authority. I've ended up coaching PMs on my team more than once in terms of helping them understand what the product was (often non trivial for new PMs joining an existing team), what kinds of things are easy technically and what kinds of things are not. Even just understanding that there is low hanging fruit to pick (i.e. opportunities for them to look good) is non trivial, etc. All the good ones I've worked with were quick on their feet in learning who to talk to and who to take advice from. A good project manager does not need to be a domain expert to be effective. They just need to learn to ask the right questions.
Ultimately, knowledge-sharing between all the stakeholders in a project (including the customer) is key. PMs acting as bottlenecks can actually be a problem when they are inexperienced. I've more than once had situations where a PM asked me "can you estimate building X please because customer Foo needs this ASAP" where we ended up having a discussion about why building X was actually important, what customer Foo was asking for vs. what they actually needed and us both deciding that actually building something else is a much better way of helping customer Foo. Asking the why questions is always important for both engineers and PMs.
That's why it's important for them to be free to do that and why the proper job title is Product Owner, not Product Manager. In the organizational hierarchy this sits at the same level as the tech leads he's working with in the same team. As soon as you have engineers reporting to PMs, it's a problem and if they have no-one reporting to them, they are not managers.