![]() How should the functionality be designed? Some users may dismiss a functionality they tried not because it’s a bad idea, but because it was too hard to use as designed. Keep in mind that users cannot easily separate design from inherent usefulness. Combine that subjective data with objective data on how easily and how well the task was actually completed (allowing for the fact that any task is easier the second time through). Once they’re done, re-interview them, asking them to compare doing the task with and without the functionality. If the users don’t use the functionality, point it out to them, and instruct them re-do the task with the functionality. Interviewing the users after the test will settle which it is. Or maybe they didn’t realize it’s there, which is a separate problem to address. If they don’t use the functionality, then maybe the users believe it’s unnecessary. Is the functionality needed or appreciated? To get the users and the data focused on a specific functionality, have users use the prototype for a task you select that should use that functionality. Instead, have them use the prototype so they (and you by your measures) know what it’s like to use the product. That’s asking them to imagine what it would be like to use the product, which yields unreliable data. Don’t show users a prototype and ask them what they think of it. The solution is to do a proper usability test. Simply not showing the rest of the GUI.Graying out every other aspect of the GUI.I then see two basic ways of making the user focus on this functionality, when evaluating it. I could then make three different versions of this. The first group could focus on a the presentation of historical data, fx a plot with some buttons for zooming and sliding. If there are five functionalities that I need tested, I could make five groups of prototypes. So what I hear being recommended is that in some way I should present prototypes that focus solely on the aspects I want to evaluate. For instance the user will comment on the graphical aesthetics, maybe even comment on colours and font face. ![]() Not even when instructed to do focus on specific aspects. What I hear is that if a complete, or rather complete, prototype is presented, the user will comment on irrelevant things, and not be able to give useful feedback on the functionalities. One type of evaluation is, for each functionality, whether it is actually needed or appreciated and how it should be constructed. ![]() When building prototypes one would like evaluation from users. I've heard about this issue from different people and written sources. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |