Date: | October 7, 2003 / year-entry #87 |
Tags: | history |
Orig Link: | https://blogs.msdn.microsoft.com/oldnewthing/20031007-00/?p=42253 |
Comments: | 1 |
Summary: | My pal Jason Moore discusses using paper prototypes as a fast way to get usability feedback. I found it interesting that by going low-tech, you actually get better feedback, because people are more willing to criticize a paper model than running code. (And another advantage of the paper model is that you can make changes... |
My pal Jason Moore discusses using paper prototypes as a fast way to get usability feedback. I found it interesting that by going low-tech, you actually get better feedback, because people are more willing to criticize a paper model than running code. (And another advantage of the paper model is that you can make changes on the fly. If during the session you get the idea, "Maybe if I did it this way," you can grab a piece of paper, write on it, and insert it into the session instantly. Try doing that with running code.) |
Comments (1)
Comments are closed. |
I can warmly recommend using Visio and its "Windows User Interface Template" for a very good compromise between speed and structure. Making changes in a user interface is almost as fast as drawing, and leaves a clean document you can actually use as part of the system specification when you and the customer have reached an agreement. It works just as well for web interfaces. We use it all the time.