Summary of "Paper Prototyping" by Carolyn Snyder

The article by Carolyn Snyder introduces paper prototyping as a low-tech but highly effective method for usability testing, particularly for websites, web applications, and conventional software. The process involves creating screen shots or hand-drawn versions of interface elements and conducting usability tests with users who interact with these paper representations. A facilitator leads the session, while other team members observe and take notes, and one or two developers simulate the "computer" by manually responding to user actions.

The key benefits for designers and developers include the ability to test designs with users before coding, make fast changes, align with marketing expectations, and eliminate technology variables from usability testing. The simplicity of paper prototyping allows teams to bypass technical hurdles, such as code instability or server issues, ensuring that usability tests can proceed without disruption.

Reflection

Paper prototypes are highly flexible and don’t need to be polished, making them ideal for quick revisions during or between tests. From my experience, they are most effective for gathering early feedback on concepts, navigation, content, and functionality. However, they are less useful for testing technical aspects such as feasibility, response times, or visual details like color and fonts.

This reading emphasizes the importance of early usability testing to catch interface issues before investing significant resources in development. Paper prototyping, though simple, is an effective way to identify user needs and flaws early on, allowing teams to make quick adjustments based on feedback. It reinforces that prototypes don’t need to be perfect and that the focus should be on function and user understanding over aesthetics. The collaborative process of involving multiple teams early in usability testing ensures alignment before moving to development.