Viewing entries tagged with 'prototype testing'
This time of year always gets me thinking about the nature of great products. Recently I was forwarded an article on Apple and the caption of a photo of an iPhone had this great line "Pleasure is Not the Absence of Pain."
In several earlier articles I have talked about aspects of prototypes. I’ve talked about using them as the basis for your product spec, and how to use them to test out your ideas on target users, and why I prefer high-fidelity prototypes to their lower-fidelity cousins. In this article I’d like to highlight the top 10 major benefits of prototyping, and talk about some of the mechanics of building and using prototypes.
Readers of these articles know that I view the high-fidelity prototype as the primary means of describing the product to be built. I have written elsewhere why a prototype is significantly more useful to the product team than the typical paper-based specification. However, that's really the secondary benefit. The primary reasons to create a high-fidelity prototype are to help you gain a much deeper understanding of your product, and ulimately so that you can actually test your ideas with real users before you have your engineering teams take months to go build something that you have no real evidence will serve its purpose.
The past few newsletters have had references to what I call "Product Validation." This refers to verifying that the product spec (PRD) is describing a product that you know will be successful, but doing so without actually building out and deploying the product.