Users can evaluate a page layout's intuitiveness by testing it as though it were the real application.  Using scenarios that reflect real-world tasks and goals, users can identify their expectations for functionality and content based on page layout, naming conventions and GUI attributes.

Method

Prototypes of interfaces for new system designs allow users to give critical feedback early in the design process. Testing the usability and value of a new website or application before coding begins can save programmers tremendous time in re-work and integrating awkward code for �additional� functionality. Users can recommend improvements in functionality, page layout and resource integration (dictionaries, formulary) into page design without upsetting the timeline for production and launch. A prototype test requires paper prototypes of interfaces. Paper prototypes are developed after user requirements analysis, before coding begins. 

Results

Paper prototype usability tests yield data of two kinds � quantity and quality.  Many users (quantity) may struggle with one element, and only a few users may struggle seriously (quality) with or have a strong negative reaction to a single element.  Both kinds of results are considered carefully to make the system more intuitive. The HCI specialist's report of findings directs the team discussion of what final changes should be made to the prototypes.

Timeframe

1 week to select and schedule users, one week to meet with each of 5 users (each user needs 60-90 minute sessions in their office), three days for interpretation of data and follow-up.