Professional Documents
Culture Documents
Ferriter
From: Jesse Shuman
Re: instructions and Usability Report
Date: 03/7/2018
I created a set of instructions over how to properly tie a neck tie. I choose this topic because
I’ve been to countless events in my lifetime where a tie was required. I can remember the first
time I had to tie a tie on my own for a social event. I spent the whole night looking up tutorial
videos and trying to follow confusing diagrams to get the tie right before the next morning. I
decided to enlighten the ones who still don’t know or may be interested to know for the future.
After I created the instructions I also made a set of questions for the subjects to answer before
they attempted to follow the directions. I also formed another set of questions for after they
completed the task. I took four rounds of trials to gather notes over the ease and difficulties the
subjects experienced over the task. I used these notes to improve the instructions. With the
revised set of instructions, I did three more trials. I received more notes and recommendations.
Methodology
I chose to use retrospective think aloud protocol. In this strategy, the subject can focus on the
task at hand then rather than diverting their attention to answering questions. Explaining their
thought process like they would in concurrent protocol could affect their ability to complete to
task. As where in retrospective thick aloud, all the questions and feedback are saved for once
the trial is completed. “May add little value to usability tests beyond what can be derived from
users’ observable behavior” (Hertzum, 2016, p. 3). I agree with Hertzum that not much more
can be pulled from classic thinking aloud that you couldn’t observe yourself. It is easy enough to
see when a subject is stuck on a step, without them saying anything. “RTA method, on the
other hand, proved significantly more fruitful in revealing problems that were not observable”
(Haak, 2003, p. 11). Haak said retrospective think aloud is more can provide more feedback
then concurrent. Both concurrent and retrospective are useful in the right setting. If I had
chosen to do a longer trial concurrent think aloud might would be a better method so the
people wouldn’t forget a thought they had mid-trial. Since my instructions were short and
relatively simple, I decided retrospective protocol was the best option.
Retrospective think aloud protocol provided more than enough feedback to improve upon the
instructions. With the revised copy of instructions, 67% could complete the task. The pictures
were a big success and helped improve the usability rate. Some of my word choices could be
seen as a failure, considering it continued to complicate the process on the revised instructions
for the subjects. With all the data I have gained from usability testing, I’m sure I could perfect
the instructions with a few more alterations.
References
Haak, M. V., & Jong, M. D. (2003). Exploring two methods of usability testing: concurrent versus
retrospective think-aloud protocols. IEEE International Professional Communication
Conference, 2003. IPCC 2003. Proceedings. doi:10.1109/ipcc.2003.1245501
Geisen, E., & Bergstrom, J. R. (2017). Usability and Usability Testing. Usability Testing for Survey
Research, 1-19. doi:10.1016/b978-0-12-803656-3.00001-4
Appendices
Pre-test
1. Have you ever been to an event wear ties have been required for the men?
2. Have you ever successfully tied a tie?
3. Can you complete the task without the instructions?
Post-test
1. Were the instructions easy to follow?
2. Was there one step that was particular harder than the rest?
3. Do you think you can successfully tie a tie on your own now?
4. Are you more likely to wear a tie now?
5. Any further recommendations?