
New innovators often delay prototyping because they want it to be good. They polish, perfect, and add features — and by the time anyone sees it, they’ve invested too much to hear honest feedback. Experienced innovators do the opposite. They build something rough, quickly, because they know a prototype is really a question.
What do you need to learn?
Before building, name the question. Will people understand how to use this? Does the mechanism actually work? Would anyone pay for it? Each question calls for a different prototype. A paper sketch can test understanding. A rough mechanism can test feasibility. A simple landing page or sign-up sheet can test demand.
Build the cheapest thing that answers it
Cardboard, tape, sticky notes, a few lines of code, a role-play — the materials matter less than the speed. The less a prototype costs, the easier it is to throw away when the answer is “no,” and the more willing you are to try again.
Test with real people
A prototype only answers questions when someone else interacts with it. Watch quietly. Resist explaining. The moments where users hesitate, get confused, or use it differently than you expected are the most valuable data you’ll collect.
Then ask the next question
Each round of testing should leave you with a sharper idea and a new question. Over time, prototypes get more detailed because your understanding has earned it. That’s iteration — not a straight line from idea to product, but a series of questions answered one at a time.


