This paper advocates for lo-fi prototyping and describes the process of creating, testing, and improving upon a prototype.

"Lo-fi prototyping works because it effectively educates developers to have a concern for usability and formative evaluation, and because it maximizes the number of times you get to refine your design before you must commit to code."

Advice for building a lo-fi prototype

Have arts&crafts supplies

Set a deadline

Make models with 'moving parts' to simulate interactivity

Advice for preparing for a test

Find test users--make them realistic

Prepare test scenarios

Practice: try testing on your own group first

Advice for conducting a test

The author suggests having 4 people with the following roles conduct the test:

Greeter

Faciliator

Computer (this person simulates the computer, by performing the actions of the interface)

Observers (who take notes, one problem per index card)

They suggest having a little more than an hour for these 3 phases:

getting ready (assure the user that this is confidential and that you're testing the prototype, not them)

conducting the test (NEVER tell the user how to do it)

debriefing (gather impressions from the tester, and thank them)

Evaluation

Sorting and prioritizing notes is very important. Agree, with the team, on suggested changes. The author suggests using post-it notes directly on the paper prototype itself.

Conclusions

While people may start with skepticism, they are always surprised by how much they learn, and how useful the technique is.