Browsing articles from "March, 2013"
Mar 12, 2013

Prototype Testing

Have you ever poured your heart and soul to help test and perfect a product that, after launch, flopped miserably? Not because it was not working right but because it was not the right product.

Are you currently wasting your time testing a new product or feature that, in the end, nobody will use?

Testing typically revolves around making sure that we have built something right. Testing activities can be roughly described as “verifying that something works as intended, or as specified.” This is critical. However, before we take steps and invest time and effort to make sure that something built right, we should make sure that the thing we are testing, whether its a new feature or a whole new product, is the right thing to build in the first place.

Spending time, money and effort to test something that nobody ends up using is a sheer waste of time.

What is prototype testing? Here’s a somewhat formal definition – the dry and boring kind you’would not find in a dictionary:

Testing the initial appeal and actual usage of a potential new product by simulating its core experience with the smallest possible investment of time and money.

Make sure – as quickly and as cheaply as you can – that you are building the right it before you build it right.
My thinking on prototype testing evolved from my experiences with Agile and Test Driven Development. It applies some of the core ideas from these two models and applies them further upstream in the development cycle.


March 2013
« Nov