Articles

The effective selection of product ideas

In the years I have spent with my teams developing new products, the thing I have regretted most was creating very well, technically and in terms of the way they were executed, products with modest commercial results despite having very motivated teams.

Indeed, there is no greater waste and source of demotivation than engaging teams of competent, close-knit people in projects with little or no result for the company. And a similar waste is optimizing a product that is already obsolete or destined to become obsolete soon.

This leads several people outside the development process to think that winning products are developed by exceptional or above-average teams. In fact, I have personally found that this is not always true, and it has been a disappointment for me to see the success of a product from a commercial standpoint associated with the reputation of the development team.

In these cases, the greatest criticism should be placed on the Product Owner, but in private companies with a strong owner’s footprint, the role of the PO is often very difficult. Companies have often grown because of the commercial flair of their top management, and it is a very difficult job to try to objectify more of the choices of products to be developed and even more of those not to be developed.

For these reasons, it was very important for me to try to reduce this great waste of resources by building a minimal, no-frills process for developing a product.

The initial selection of product ideas is extremely important, and I have been able to see in practice that employing Canvas boards encourages a healthy discussion among the people best suited to assess market impact by involving top management. Doing so reduces the number of unsuccessful projects in the market.

In these very early stages, the Vision Canvas proves very effective because it focuses on market-oriented questions and business expectations while leaving costs aside. It allows you to be relatively fast and avoids the initial over-selection.

Indeed, it is better to invest a few months in a phase of exploring ideas even if they are not fully promising, than to fail a product that will later prove successful.

Leave a Reply

Your email address will not be published. Required fields are marked *

Other insights into Agile product development that you might be interested in

Discovery & Construction

Product Discovery Product Construction

I talk to you about innovative product development, inspired by the book “
Inspired: How to Create Tech Products Customers Love ” by Marty Kagan. There is a big difference between leading companies and others in the product creation process. The key concept is “product discovery”: exploring and testing ideas before investing heavily. This is integrated with “product delivery” or “construction.” The author of the book stresses the importance of prototypes, which in HW I prefer to call “pretotypes,” and tools such as Lean Canvas and Story Mapping. There is too much focus on Scrum, when instead it is important to create truly useful functionality. The book is recommended for those who want to truly innovate.

Read More "

The pretypes i.e., the forerunners of the product

Pretypes are quick and inexpensive demonstrators to test key ideas before creating complete prototypes. I am talking about an automated palletizing project where we made a pretotype of the most critical component, which was the tray, in just 15 days. We saved several months and significant investment. This pretotype allowed us to validate the best materials with which to build the final tray.

Read More "

What is the Agile Factory – StoryTime Interview

In this interview with Antonio Panareo of Story Time, we talked about the agile innovation factory that I established during my last corporate experience. Establishing this agile factory was a real gamble and I talk about the experience I had with my teams.

Read More "