Labs/Ubiquity/Usability/Usability Testing/How To: Difference between revisions

m
Line 91: Line 91:
====Paper====
====Paper====


Paper prototyping is the sliced bread of Usability. Sadly, very few practitioners use them. It's best to think of paper prototyping as the step in-between sketching a design and creating a mockup on the computer. It has all the advantages of sketching (cheap, fast to make, easy to change) and helps users open up to criticizing the design.
Paper prototyping is the sliced bread of Usability. It's best to think of paper prototyping as the step in-between sketching a design and creating a mockup on the computer. It has all the advantages of sketching (cheap, fast to make, easy to change), helps users open up to criticizing the design, and it's instantly interactive.


Part of the reason paper prototyping isn't used is that people think there must be some magic to it, some step they haven't thought about. The whole thing is silly, draw an interface and ask people to "use it." But it really is that simple.
Part of the reason paper prototyping isn't used is that people think there must be some magic to it, some step they haven't thought about. The whole thing is really as simple as it sounds: draw an interface and ask people to use it.


<video type="youtube" id="GrV2SZuRPv0" width="437" height="315" desc="1x Video [http://www.youtube.com/watch?v=GrV2SZuRPv0 Original Video]" frame="true" position="center"/>
<video type="youtube" id="GrV2SZuRPv0" width="437" height="315" desc="1x Video [http://www.youtube.com/watch?v=GrV2SZuRPv0 Original Video]" frame="true" position="center"/>
Line 99: Line 99:
The only time that paper prototyping isn't very useful is when the interaction is not restricted or response times are important. If you are trying to understand how users interact with a command line (unrestricted input) and that interaction depends on very fast speeds (like auto-suggest) it may be hard to get good information.
The only time that paper prototyping isn't very useful is when the interaction is not restricted or response times are important. If you are trying to understand how users interact with a command line (unrestricted input) and that interaction depends on very fast speeds (like auto-suggest) it may be hard to get good information.


And unfortunately, if you have to share your designs to a remote team most people do not give early design prototypes the respect they deserve. And unless you have a touch screen computer, sending the sketches to remote teams can be inconvenient.
Unfortunately, if you have to share your designs to a remote team most people do not give early design prototypes the respect they deserve. Unless you have a touch screen computer, sending the sketches to remote teams can be inconvenient and under-valued.


* UIE has some great great tips on paper prototyping and information on it's so powerful. [http://www.uie.com/browse/paper_prototyping/]
* UIE has some great great tips on paper prototyping and information on it's so powerful. [http://www.uie.com/browse/paper_prototyping/]
501

edits