Rendering the rough sketch of a software screen on paper gives users a way to test the software, identify their expectations for functionality's responses, and still feel free to make changes to page layout, language and navigation.

Method

Using post-it notepaper, scissors and a thorough knowledge of interface conventions and design options, a site is architected and then designed screen by screen so that the user can literally see what the software will look like when it is built. 

Results

The image (right) shows how many pages get developed to reflect the sequence of steps a user might go through to complete a task using software.  Paper prototyping allows the team to anticipate engineering resource management and database integration issues, as well as reduce need for training when user responses to the prototypes are resolved.

Timeframe and Preparation

Prototyping happens once use cases or UEDs are done, near the end of the design process.  With a team of usability prototypers who know the intended workflow, prototyping can be finished in a few weeks. Before handing off to coders, paper prototypes can and should be tested with users to clean up the taxonomy and increase the flow of pages and available functionality within each page.

Additional Reading

Paper Prototyping: The Fast and Easy Way to Design and Refine User Interfaces, Carolyn Snyder (2003).