Viewing entries tagged with 'user testing'

The Most Important Thing

Posted by marty cagan on May 10, 2011

Tags: , ,

There are several skills and activities that are important when coming up with great products.  In my last article, I argued for the absolute necessity of having good data about how our products are actually being used. 

Read the full post

High-Fidelity Prototypes

Posted by Marty Cagan on April 29, 2008

Tags: , , , ,

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.

Read the full post

Prototype Testing

Posted by Marty Cagan on October 1, 2007

Tags: , , ,

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.

Read the full post

Prototype Testing

Posted by Marty Cagan on October 1, 2007

Tags: , ,

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 ultimately 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.

Read the full post