Presentation+Design+Summary

> Usability Testing: Methodology and Limitations (Chris) > > Employing Mockingbird software as a prototype platform, Virti-Cue users were asked to complete a series of tasks aimed at functionality and intuitiveness. Choosing from three main icons on the home page, users traced a number of pathways to complete each task. Users selected a story from the local device or cloud architecture, edited an existing story, and created a new story incorporating video, audio and text. > Observations were recorded in a checklist format documenting user reactions and experiences pertaining to functionality and intuitiveness. A talk aloud process also generated valuable feedback on the user experience. When the testing phase was complete, users were asked to complete a short response form with open-ended questions requesting additional feedback. > > While we were pleased with the breadth and overall quality of responses we received, we encountered a number of shortfalls in our methodology. First, the linearity of Mockingbird made it difficult to replicate the authentic user experience we had intended with this product. Second, the checklist format was difficult to navigate and a free-flowing documentation style was substituted in its place. Third, some users expressed they were uncomfortable with the talk aloud process. We tried to ease their discomfort with an explanation and rationale of the process, however, it was not something users were particularly at ease with. Last, we felt users would have benefitted from a completed exemplar to demonstrate the end product and what we were asking users to work toward.