Trailblazers like Google, Salesforce, and Adyen have mastered the iterative development approach to product management, during which they first develop products simple enough to bring to market quickly but innovative enough to attract early adopters. After receiving valuable customer feedback, the developers change and improve, bringing forth a new version sure to stand out.
The excitement of having all the bells and whistles bombard engineering with an endless number of product feature requests, but loading products up with too many features causes them to be bloated and can significantly slow down the development process, prohibitively increase costs and potentially result in a product that doesn’t actually fulfill the needs of its intended customer. So herein lies the dilemma - now what’s the solution?
Developers should compartmentalize the product’s vision around three or four themes. For instance, in the case of PredictSpring Modern POS, innovation is focused around mobility, omnichannel, clienteling and consumer experience.
Themes may also depend on the use case. Depending on the vertical from apparel & footwear, health & beauty, home furnishing or telco, there will be changes in the feature set. It’s ok to develop different manifestations of the same platform to meet the needs of different industries provided they use the same underlying building blocks, resulting in lower cost of software development which is passed on to the customer.
Here are the questions product managers should ask when defining the product roadmap:
Interested in learning more? Read the full article and additional content from our founder and CEO Nitin Mangtani in his regularly featured articles on Forbes.