Question: How do you decide to release a new version of a product?
My question is specific to products used by almost everyone in the world — products like Windows, MS-Word, Adobe Reader. For such products, how does product manager decide for the next release of such products?
Notice that these products are already at a level that almost everyone using it is more-or-less satisfied with them. For example: Having released Microsoft Office 2003, how would the product manager decide that we need Microsoft Office 2007?
Answer from Nick Coster of brainmates: This is a problem that faces the product manager of any product that has matured, become a commodity, or both. For these types of products it can be tempting to keep looking for new features to keep adding to the original product. From the product manager’s perspective this keeps you employed — right? Well… no, not if customers start to look for simplification or the product becomes over engineered and cumbersome.
As the product manager, the first step to take is to make sure that you understand your customer. Define who you think them to be. Segment the markets that you are serving in to smaller groups that have similar behavioural requirements. Even for these mass market products there will be groups that use them differently. Do lawyers use Word in a way that is different than students? What are those differences in their goals?
Now look for the specific needs of each of these groups? Are they being met by your product? Are there any areas that your customers have to find other solutions to use before they can reach their goals? These may be the features that you are looking for.
Alternatively, do the customers know how to use all of the features that are available already? Are there features that are never used? Your next release may either make these more accessible or remove them altogether.
Word’s upgrade cycle has never really delivered any significant feature enhancements for my use. The tool bars have changed over time, but beyond the core text formatting capability and spell check, the rest of the upgrade has been unnecessary. This hasn’t stopped me from making the changes over time. Microsoft introduces compatibility issues in older versions by releasing new versions. Usually just enough customers also tend to have a need to use the latest version. Combining these together can create a demand for a software product, although it is more likely to frustrate customers than delight them.
Finally, if your product is mature, everyone likes it, and it does everything that your customers want and is preferred to the competition — then LEAVE IT ALONE. You don’t have to keep making changes for the sake of change. Instead, look for a new market where it can solve new customer problems.