Paper prototyping uses hand-drawn interface sketches to simulate the interaction experience of a digital product, allowing teams to test ideas with real users before writing a single line of code. The method was described in detail by Carolyn Snyder in her 2003 book of the same name, and it remains one of the most cost-effective and insightful prototyping techniques available. Its very roughness is a feature: users are less inhibited about criticising a paper sketch than a polished digital prototype, which produces far more honest and useful feedback.
What It Is
In a paper prototype, each screen or state of an interface is drawn on a separate sheet of paper or index card. During a test session, a facilitator plays the role of the 'computer,' swapping screens in response to the participant's actions. The participant interacts with the paper screens as if they were a real interface, pointing or tapping where they would click or touch. A second team member records observations and notes problems. The session reveals navigation failures, label confusion, and incorrect mental models at a fraction of the cost and time of digital prototyping.
How to Run It
Sketch the key screens of your interface on paper at approximately device size, using markers for clarity. Prepare additional sheets for error states, popup overlays, and secondary screens. Write a set of test tasks that represent the most important user goals. Run five to eight test sessions with participants representative of your target users. During each session, the facilitator gives a task, the participant attempts it using the paper screens, and the computer operator swaps sheets to simulate the interface response. After each session, debrief with the team and note the most critical problems before running the next session.
When to Use It
Paper prototyping is most valuable early in the design phase, before digital prototyping begins, when the team has a concept to test but has not yet committed to a specific interface structure. It is especially effective when testing navigation, labelling, and information architecture because these structural elements are easy and cheap to revise at the paper stage but expensive to change once digital implementation has begun. Use it whenever quick, cheap, and honest user feedback is more important than visual realism.
Tips for Success
Keep sketches rough and clearly hand-drawn. A prototype that looks too polished signals to participants that the design is finished, which suppresses the critical feedback you are looking for. Prepare more screens than you think you will need: error states and edge cases that you did not anticipate will frequently come up in testing. Assign the computer role to someone who can swap screens quickly and smoothly without breaking the participant's focus. Debrief after each session rather than waiting until all sessions are complete.
