Hallway usability testing: How much of the UI do you actually make functional? -
Most of you make your app completely or fully functional while doing the usability test? Or do you just make sure the link or flow chain properly? Or do you just come on paper and go with it?
I would like to test at the beginning of a prototype and am trying to find a good balance. But at the same time I worry that some non-functional parts can not really give representative results.
Thank you.
Applicability testing, hallway or otherwise, only requires functionality that you need to test. In more utility tests, you should go with its prototype and make your own development at that point where it can answer those questions. For example, if you need to test if users understand the order of the sort order for the table, then all you need is a paper picture in the table that shows the sort signal (table content blurry) and Describes how the table is resolved. If you need it, then all you need is a bunch of web page, empty except empty, which is linked through the navigation menu.
You only need pages for tasks that your users give. If you are testing IA, you only need pages on the standard path. If you are also testing error retrieval, you need the pages of the standard path along with the entire navigation controls. If you are also testing to detect the error, then you also need content on the pages.
You can emulate functionality even when it's easy to do. For example, if the user can detect a desired sort order in the probe, for example, when the user clicks the non-functional control to sort the table, you can say, "OK, by doing this you can It will get "and you move the mouse and select a bookmark that shows the table in a new type of order.
In the hallway test, if the user breaks the fidelity envelope, then you can simply say, "I have not created that part yet. Let's go back to A, and walk from there. "Of course, you should take care that the user has made a wrong turn in the work done for them. I have no problem with users who complain about non-functional features when I tell them that this is an incomplete prototype and we are just testing UI for X, Y, and JE at this time. .
For the less devoted prototype, I often call them users instead of "prototype" instead of indicating "mockup" or "drawing" with less functionality. You can put explicit placeholders in unavailable content (for example, "Blah, Blah, Blah ...", "Todo: About the Picture of the Product Here."). If a user commentes on something outside the loyalty envelope (for example, "this symbol should be red in height"), just note it, and say the subject is under development (e.g., "Thank you. We are not trying to figure out how to organize this site. "
Utility testing is really necessary with limited-fidelity prototype for practical design for most projects. Otherwise, you ruin a lot of work to develop those things that have to be repaired.
Comments
Post a Comment