Developing products is an important part of what Thinknostic is all about. We build commercial software products for our clients as well as develop our own product ideas. The product development process both energizes and invigorates us by encouraging us to use techniques we might not otherwise use and apply disciplines we might not otherwise have.
Creating a new product requires inspiration, innovation and a keen sense of what consumers want. This is where Product Management begins. The term “Product Management” seems to mean different things to different organizations. I like to think of the role as being the primary liaison between the software team, the marketing team and the business team. In many cases the Product Manager may have been recruited from or asked to also lead one or more of those teams and this might explain why the role has no universally accepted definition.
First and foremost the Product Manager is a representative for the products market for all important team decisions. It also involves acting as a liaison between the software team when dealing with customers and acting as a representative of both when dealing with the business and financial side of things.
The Product Managers accountability is to deliver the right product. That means they are trying to delivery maximum value to the customers. The Project Managers accountability is to deliver the product right. That means they will be striving for defect free code, delivered on time and to budget. These roles are co-dependent and their goals should be complementary however there are times when trade-offs need to be negotiated. For example incorporating new features late in the delivery cycle can jeopardize the availability date, destabilize the code or blow the budget. On the other hand not having the feature might mean losing an important customer or missing a new market segment. The most critical part of Product Management is figuring out who your customers are, and what they need.
How we fit Product Management into thinkWRAP
At Thinknostic we aim for commercial quality at prototype speed. This means short release cycles and quick rapid feedback. Neither ours nor our customers budgets are unlimited so our focus must always be on maximizing customer value and that means that our product managers need to be priority setters. They must be very effective at information gathering, synthesis and dissemination so that opportunities to improve consumer value can be quickly assessed, prioritized and communicated to the development team.
There are many aspects of thinkWRAP that make the Product Management discipline even more important. There is a need to get an up-front understanding of the products value as perceived by the consumer, and continually validate and refine that throughout the project. Priorities must be adjusted as our perception of reality evolves. A thinkWRAP project treats completion dates and budgets as fixed unless the business decides otherwise. That makes scope or features the major variable. Deciding which features provide the maximum value requires extensive customer input, experience and sound judgement throughout the project. That is the core responsibility of the Product Manager.
April 20, 2007 at 8:41 pm
Mike:
I find it interesting that the word “profit” and “profitability” never appear anywhere in your description of what responsibilities lie with a Product Manager. How would you evaluate and/or integrate this statement into your thinking:
“First and foremost, a Product Manager is responsible for ensuring the Profitability of Product(s) under their purview”
Foggy
April 26, 2007 at 4:53 am
Hey Mike,
While the excitement and adventure of creating a new product demands the creativity and innovative skills that you describe, my underlying definition of a “product” is something that will provide a common, repeatable and *packaged* solution that meets a defined set of business needs facing a larger community of customers (i.e. a market segment). The challenge of the product manager is to adapt the direction of the product’s capability to address the market’s evolving needs (which for an emerging product is often represented by the next potential customer’s “needed to close the sale” needs), while “staying the course” with the product roadmap. This is the difficulty: balancing the enticement of the next sale against the overall vision for the product. For this to be successfull, the product roadmap needs to be aligned with a business roadmap: what emerging best practices can be facilitated or enabled by the new software product? Only by placing a well thought-out, business-driven “stake in the ground” can a product create a series of customer success stories that will drive mass adoption of the product in the marketplace.
-D
November 26, 2007 at 11:39 am
Really makes you think, doesn’t it?