Re:Product Managers in Startups: What’s their Role?
by tptacek on Thursday October 15, 2009 @02:42PM
(#883976)
From what I can tell, list of bullet points aside, the difference between a good PM and a bad PM is that the good PM is constantly talking to customers and relaying what they say. I was and have worked with the "other" kind of PM that is very good at documenting and advocating for things, but that's not the job. The job is being on the phone.
Re:Product Managers in Startups: What’s their Role?
by mikeryan on Thursday October 15, 2009 @03:01PM
(#884016)
Yeah where this seems to break down is that there's a very gray line around what a Product Manager's job is as opposed to a Project Manager's job.
Unfortunately in many organizations these lines blur considerably.
Re:Product Managers in Startups: What’s their Role?
by krav on Friday October 16, 2009 @03:23AM
(#884963)
By the time any startup is using words like "stakeholders," it's no longer a startup.
Here's what I see a Product Managers Role to be.
1. Define the Product Features. Take input from all relevant stakeholders (Customers and execs) and translate this into a set of product features. Document and distribute. Clarify any concerns between stakeholders.
2. Clearly define features. An extension of point 1. Work with design and technical teams to make sure that the features are clearly defined for everyone working on the product.
3. Clearly Communicate Features. Document the heck out of the product features. PRDs, IA, UI Designs all need to be clearly documented. Then COMMUNICATE these features back to all stakeholders. If someone doesn't understand a feature its the PM's role to make sure they do.
4. Prioritize features. Even if you're not working in an agile approach at some point you will need to draw a line between MUST HAVE and NICE TO HAVE features.
5. Product Advocate. A PM is the champion for a product. It's important they believe in the necessity of what they are building and are willing and able to champion it internally and externally.