Work2XL wrote:Long before prototyping, you should get a general idea of market size, competition and have a decent idea of the manufacturing cost.
What I'm trying to say is do ALL of the legwork BEFORE you spend a dime. A thorough business plan that YOU write yourself with HONEST information is worth it's weight it gold.
This is actually something I've wondered about a bit. Sometimes it seems useful to create a rough prototype so that the function and flaws of the product can be understood. I guess the real question is what are the organization methods for this, and which situations do they suit best?
For example with a toy I would probably create it first and test it with a small trusted audience second. In this case prototyping would preclude market research...which should be much more extensive than the steps above by the time the toy gets to market.
I would probably label this a tangible driven product. This would be "tangible driven" because interaction with the product would obviate it's need/appeal. Market research is often flawed and limited by the accurate imagination of those surveyed. This innovative product is created in spite of market research. Consider Henry Ford: "If I had asked people what they wanted, they would have said faster horses."
With computer software I would probably look at the market first, figure out the user/client needs and build the product to suit that if there was an obvious need. I would label this a market driven product.
Are there any other categories, or guidelines that would be useful when looking at it this way?