Sticky pads are the perfect prototyping tool.
Fine, but how does it work in practice?
How does one prototype a web application?
- Know the theory.
why paper prototypes are effective.
Read Jakob Nielsen's excellent instructions on conducting a
Discount Usability Test.
- Print an empty browser screen, in landscape.
Enlarge the print to an A3 size, so it easily accommodates a A4 page.
- Create a
paper prototype for each screen.
Each screen is a landscape A4 sheet with sticky pads.
- Divide the tasks among 2 IT specialists:
- The first one plays the role of 'webserver', puts down a new page after every click.
- The second one plays the role of interviewer.
all the user's comments,
- Prepare a number of assignments (3 - 5) for the tester.
- Make the assignments realistic, a good representation of daily tasks.
high frequency functions
preferably, the functions that make up 80% of the daily tasks.
- Make it easy for the user to focus completely on the user interface.
Supply all required information for the assignments, including sample values.
Assign a day off to employee J.H. blok on Tuesday 4 December.
Generate a duty roster for january 2002.
At first when they see the paper prototypes, users smile.
The first sticky pads cause guffaws.
- Explain the purpose of the session: testing the design.
Stress it explicitly that you are not testing the individual.
Encourage the user to think out loud, to comment on the design without holding anything back.
Explicitly ask the user to mention everything that seems difficult, anything that raises a question in his mind.
- Ask the test person to do the assignments one by one, preferably in a set order.
The interviewer records
all the comments, without any filtering.
This will make the user feel that his comments are important.
All this writing can't be in vain.
It is a stimulus to give even more comments.
- Thank the user for his valuable input and say goodbye.
However, within a minute or two they have completely forgotten that they are clicking sheets of paper.
They click from page to page and start complaining when
the server doesn't put down a new page fast enough.
Could it get more real?
After 3 to 5 sessions the problems reported are so small that further testing does not make any sense.
The design is sufficiently developed, stable enough to start
- Afterwards the two IT specialists discuss the comments.
- Improve the design.
Shift sticky pads to change the screen layout.
Replace unclear widgets.
Split or combine screens.
- Repeat the session with more users.
Problems experienced earlier should be solved.
Bigger problems make way for smaller ones.
Till next week,