What is Product Development? This is a question that has nagged at me since I started working for Creo Quality. It certainly seems like something that I should know the answer to, since I am working for a company that deals in product development. Alas, the answer had thus far eluded me. So, I set out on a quest to determine for myself what Product Development actually was. So far, I have talked to someone in the industry, checked out websites such as ehow.co and answers.com, and also looked at detailed papers that had been written by experts on the subject. I learned about something called the Fuzzy Front End, and what the difference between is between breakthrough products as opposed to platform products and incremental products. I was surprised at the wealth of information that existed on the subject.
To start off, I asked Jon Speer, Creo Quality’s founder, a few key questions. He spoke to me about the importance of planning and being able to define your objectives and have a process that is reproducible. He also stressed that although planning is important, you don’t want to overplan and get caught up in the process of planning. You must keep your objectives in mind and remember that every project has a beginning, middle, and end.
One of the papers I read was by Kenneth Crow and reiterated most of what Jon said and, like Jon, stressed the importance of the process being repeatable. An interesting point that he made was that the typical duration of most projects “range from six months to six years. As a result, development personnel don’t have the opportunity to learn from and to refine the development process through repeated use on an individual basis. With the rapid pace of technology evolution, the hiring of many young engineers in some industries, high turn-over rates, it is not unusual to see development personnel with keys roles in a development project, but who have not gone through a full development cycle on a prior project within their companies. In short, many development personnel have little understanding of or practical experience with any standard product development process in their companies”. He uses this concept as one of the reasons the process must be reproducible. “The process must be characterized and documented. Unless it is, it will be difficult to assure understanding and agreement on what the process in fact is, difficult for all development personnel to understand the process in a consistent manner, and difficult to communicate that process to new personnel.”
I plan on continuing my search for the meaning of Product Development. In future blogs, I will share with you what I have learned. If you know any good sources of information, please feel free to contact me and share that knowledge with me. This Product Development newbie could use all the help she can get.

