Bertrand Duperrin's Library tagged productmanagement →  View Popular, Search in Google

It is much easier to use product managers to create a repeatable process. After all, there is much less passion involved. For many markets, it may not be worth Apple-style design. People often wonder for Enteprise software whether it matters, for example. But I don’t buy my PM friend’s argument. Talent of all kinds is always scarce. A decision to eschew finding talent for a repeatable process creates mediocrity.

productmanagement productdesign culture microsoft process repeatableprocess userexperience

Everyone is low on talent. Many are missing, or, simply can't afford the connection between the market and development. So why not have an outside-in community product manager for your social software? What does that mean? Traditional product managers work alongside the development team. They are responsible for a multitude of tasks, including gathering, prioritizing, managing and conveying requirements and priorities from their stakeholders to the development team. That's a lot of stuff for someone to do with decreasing resources. So how about having a counter-part whose sole purpose is to represent the outside stakeholders - like Principle, End Users and Partners.
[...]
So the primary responsibility for the Community Product Manager is to filter, manipulate & translate that Social Content 2.0, derived from the stakeholders, into the language of the product manager and the development team. If everyone gets along, this should not only reduce the workload of the over-burdened product manager but also infuse the community's Social Content 2.0 into the product's development lifecycle. This is the aim of outside-in software development.

productmanagement productdevelopment communities communityproductmanagement socialsoftware enterprisesocialsoftware communitymanagement