Focusing on the Big Picture for Faster Product Development
Whenever you are working on developing a new product, it is important to get an understanding of the big picture or vision for the product in the marketplace. Is your product going to be only for one customer or is it expected to have broad applicability in the marketplace? Why is this so important? Management wants the greatest possible reward with the least amount of risk.
Your company’s management is challenged with the responsibility of getting the most from the dollars that are invested in the company. Without a solid understanding of the potential of your project, it can be hard for management to justify the expense of the development effort. They may choose to put more funding into another project that has done a better job of articulating the potential. Having multiple applications for your product, decreases the risk to the company that there will be no sales of your product because there are multiple applications where your product might work.
Oftentimes, the decision is to start commercialization either with a smaller market segment or with a smaller customer to get the bugs worked out of the product before a full-scale launch of the product to a larger application. It is very common that the first application that is targeted for a new product doesn’t pan out.
If there is a snag in getting the product to work in this first application, then a lot of time and effort can be poured into making it work when a better decision might be to move on to another application and use the learning to make a better product for a different application. By keeping the big picture in front of everyone, your team is more likely to move quickly to the next application, thus minimizing the costs.
Since the bigger applications are often farther down the development road, it is important to keep moving to those applications and using the smaller applications as intermediate steps on the path to the large applications and to long-term commercial success.
Without a clear understanding of the multiple possibilities for a product, communication to management of a shift to a new application for a product when the first one doesn’t pan out could appear as a desperate attempt to keep a project alive, rather than the next logical step on the development process.






