Projuct:
Often a
single project is executed and individuals or other departments recognize that the project could be redeployed in another application, or potential market. However the scale along with many other key business elements are yet to be determined and thus a formal product development process would crush
something that
may be re-deployed
7-10 times in the course of time, and thus it squelches the chance of development. A "Projuct" is the concept to take a preexisting project that has been executed and using the core concept and materials less the customer influenced or customized elements and re-offering it as a proven concept with the expectation that the "Projuct" will have a limited
run of opportunities.
Products are standard and have minimal options, while Projucts are unformed beyond the core concept and standard elements and unlike products are not meant for high volume. This fluidity and understanding of limited
run, allows for the core concept to remain while letting the peripheral aspects to become what is needed for the application or market.
Commonly a Projuct is developed to the following
level and that is where the development stops, unless the volume increases and case for formal product development can be made.
Development
level:
- Develop Whitepaper for core concept
- Develop brief presentation
- Develop
YouTube or other published media point for concept
-
Train sales
force on concept, for them to identify other opportunities
