Inadvertently see this book < website usability testing and optimization guide, although it was published in 2010, because a lot of content is a guide to work, reading down is helpful.
This book is not much, so read very quickly, today read the sixth and seventh chapters (HA, not in the order of chapters read)
Sixth: Find something to do for the testers (otherwise they don't know what to do or if they don't have a goal, it may not make sense)
1, first, specify a task list:
1, take a piece of paper;
2, List the 5-10 most important things visitors need to do in your site.
" You can't just say that you should really try." "A lot of people do not have the executive power in place, and my executive power needs to be improved."
It is important to note that the task of ensuring the test reflects the actual goal of the user, not what you think the user wants to do.
2. Determine which tasks to test:
After making the checklist, you need to determine which tasks to test this month.
Testing which tasks depend on many of the following factors:
A, which tasks are critical: what visitors must do on the site, such as when they want to buy a book for a visitor;
b, what tasks keep you awake at night? such as some confusing to the user function point;
C, other user studies indicate which features may not be easy to use? Customer service often hear the user problem is what, to have feedback system;
3. Turn the task into a scene:
Writing: Transforms a simple description of a task into a script that participants can read, understand, and follow.
4, set the constraint condition:
The main focus is on the participants to set constraints, such as:
A, do not use search;
b, stay on the website;
5, a pilot test of the situation:
Definition: After writing a story, it needs to be pre-tested, which is called pilot test;
Time: Complete within 15 minutes;
Objective: To ensure that the situational description is clear and clear;
Executor: Can let anyone do the participant;
6, print out the scene: for participants to use;
Personal experience:
Many organizations do not have usability tests, let alone some participants. But now some app products have actually started to use the product online, fill out the Product Experience report, the industry is progressing.
about writing task scenarios This work: it is still necessary, otherwise the participants have no experience of the target, and the content of the submitted report will be out of the way.
~~~~~~~~ not gorgeous split line, ^_^ ~~~~~~~~~~~
The seventh chapter: some tedious checklist:
"I like things that work, and in some cases checking the list really works. "
Objective: There are many things that must be done at a given time during the event, and there are many details that need to be tracked. You may remember to finish most of the work, butCheck list so you don't miss every single item, especially those things that everyone might forget. (Similar to the function of the Cue card)
Role: On the day of the test, the checklist allows you to keep all your attention on the participants without having to memorize the tedious details.
1, three weeks ago:
Determine what to test: Web sites, wireframes, prototypes, and so on.
Develop a checklist of tasks to test.
Determine what kind of participants you want to test with.
。。。
2, two weeks ago:
3, a week ago:
4, two days ago:
5, Test Day (before the first Test):
6, before each test:
7, when the participant signs on the video license form:
8 at the end of each test:
Personal experience:
This chapter is a detailed description of the test work and how the usability testing work is carried out.
For graduates or those who have just entered the test work, it is a good job description, detailing what you need to do every step of the process. (If you have a book that tells how good programmers work, it's nice to have a lot of people get started as soon as possible without detours)
Site usability Testing and Optimization guide-essay 2