What Should I Test in a Prototype?

Whatever you most need to know is true before you spend the next dollar.

A prototype is at its best when it's answering specific questions rather than being a vague “let's see how it looks.” The most useful things to test usually fall into a few buckets: does it work, does it fit, does it feel right, and can it be made. Deciding what you need to learn before you build tells you what kind of prototype to make.

The Big Things Worth Testing

Function — does the mechanism or feature actually work
Fit — do the parts go together the way you expect
Ergonomics — does it feel right to hold and use
Appearance — does it look the way you intended
Manufacturability — are there obvious problems for making it

Test One Thing at a Time

Each round is clearer when it's chasing a specific question. Trying to prove everything at once makes it hard to know what a result is telling you — and tempts you to change too many things between rounds.

Let the Question Shape the Prototype

If you're testing function, you'll want something closer to production materials; if you're testing looks, a good appearance model matters more. The thing you're trying to learn decides the process, the material, and the detail.

Common Mistakes We See

Building a prototype with no clear question in mind
Testing appearance and function in a way that muddies both
Changing several things between rounds so results are hard to read

A Good Next Step

A short conversation can help you decide what each prototype round should test — and what kind of prototype answers it best.

Please keep your question general — no confidential product details are needed for the introductory consultation. If confidential review is needed later, an NDA can be arranged before a longer engagement.

Need Help With Your Specific Situation?

Book a 10-minute introductory consultation for $20 and ask one focused question about what to test in your prototype.

Book a 10-Minute Consultation — $20