Few would disagree that the iPod saved Apple from bankruptcy, but it was not just about the idea of a digital music player. There were at least 20 other digital music players on the market long before Apple started the project. Apple understood at a very deep level that the requirement of “easy-loading songs” was extremely important, and they developed the concept of iTunes as a result of that understanding. We all know the results. Imagine if they had said, “We don’t need to worry about a conceptual design. We know what we need already—we just need to focus on getting it to work.” If the mission was singularly focused on getting a prototype to “work”, then Apple and the iPod would both be on the waste heap of yet another failed startup/product just like all the other digital music players/startups on the market at that time. Apple’s Conceptual Design for the iPod is largely responsible for saving what would eventually become the most valuable company in the world.
If only all startups were as focused on Conceptual Design. Too often they focus on just getting a prototype, or getting it to work, long before any ideas about the Conceptual Design have been considered. This is unfortunate as good Conceptual Design is not all that complex and can be mastered with basic processes and some simple rules.
Conceptual Design sets 90% of the development cost, unit cost, performance, usability, number of fires you will have down the road, etc. Ninety percent of the success of a product is determined in the Conceptual Design phase – not in the detail design phase. It is the most leveraged part of the development processes. Get this wrong and everything after can be a colossal waste of time and money—something small companies can rarely afford to do.
Your sheet should look something like this:
|Requirement||Rank||Concept 1||Concept 2||Concept 3||Concept 4|
This will take a little time to set up and to get everyone to understand, but it will be well worth the effort. The magic of this processes is that it focuses the team on debating one requirement and one concept at a time. Is this requirement more important than this other one? Will this concept be better than this other one in exceeding this requirement. Too often, teams get to overwhelmed and confused because they try to talk about everything at once, or miss important aspects of certain concepts because they are too focused on how well a concept will perform on some other requirement. Focusing on one box at a time brings clarity and objectivity to the conversation and decision making.
Here are a few other things to keep in mind when doing Conceptual Designs:
A product is only going to be as good as its Conceptual Design, no matter how well the detail design is done. Using a proven methodology for conducting a Conceptual Design is a good start – especially for small companies and startups.