All really good … IF you are working with products and features.
But, what if you are working with services? Where do you turn.
For nearly nine months, I’ve been working on defining a product management lifecycle for services. Sounds easy enough, use the lifecycles that others have defined: define it, package it, educate about it, and market it.
But, the services are more than products, they’re people.
In my case, the products I’m trying to create are inherently part of the people who are creating them. What I mean is, when a person leaves the company with their domain knowledge, then my product process falls apart. I have to start all over.
Frustating? yes. Impossible? Jury still out.
In the nine months, there has been some movement, but more stops and stalls. Fire fighting always seems to take place first. And, there is the eternal question: Aren’t we developing products from the inside out? All good product management training says to identify the problem the market has, solve that and you win. But, with people being the product, you need to capitalize on the domains you already own. These people were hired because they have an expertise that was needed/wanted by the market.
But packaging people is no easy feat! A simple lifecycle doesn’t apply, and when it does it changes rapidly before you can truly achieve the end goal. Any ideas from the outside?