User Experience Re-Mastered Your Guide to Getting the Right Design- P8

User Experience Re-Mastered Your Guide to Getting the Right Design- P8: Good user interface design isnt just about aesthetics or using the latest technology. Designers also need to ensure their product is offering an optimal user experience. This requires user needs analysis, usability testing, persona creation, prototyping, design sketching, and evaluation through-out the design and development process.
Nội dung trích xuất từ tài liệu:
User Experience Re-Mastered Your Guide to Getting the Right Design- P8 336 User Experience Re-Mastered: Your Guide to Getting the Right Design Figure 11.4 shows the same icons, with a reduced affordance for clicking because they are on a sloped image. It seems that the reduction in affordance was not enough to tell the participant that he should not click on these icons. Making Decisions with Qualitative Data Working with qualitative data is a process of making decisions that start with thinking about what to note in the evaluation (collecting the data), continues through the collation and review process, and then influences your summary (analysis and interpretation). Those decisions need to be made in the light of the following factors: ■ The differences between the participants in your evaluation and the real users. For example, your test participants might have more experience of the system than the real users, or they might lack specialist domain knowledge. ■ The differences between your test environment and the users’ environment. For example, you may have had to stop the test while you solved a configura- tion problem in the system, or the room where you conducted the test might be much quieter or noisier than the users’ environment. The same decisions apply to the data from your pilot test. It is even more likely that your pilot participant is different from your real users, so you need to be more cautious about drawing conclusions from the pilot data. The actual pro- cess of examining your qualitative data to identify usability defects depends very much on your user interface and on what happened in your evaluation. In prac- tice, it is usually quite easy to spot the important problems and find the causes for them. It often helps to speed up the work of reviewing your qualitative data if you establish a coding scheme. A coding scheme is any method of assigning a group, number, or label to an item of data. For example, you might look first for all the data about icons, then for everything about the meaning of labels, then for remarks about navigation. Some practitioners establish their coding schemes in advance, perhaps from a list of heuristics or from an inspection of the UI. Others derive a scheme from the pilot test. However, evaluations frequently surprise even the most experienced practitioner, and it is quite usual to find that the coding scheme needs to be modified somewhat when you start interpreting the data. It is also typical to find that some of the data are inconclusive, cannot be retrieved, or have been badly written down. If your only data from an evalua- tion were derived from a video recording and the tape cannot be read, you have a disaster – which is why we place so much emphasis on taking paper notes of some kind along with any electronic data collection. Generally, your chances of deciphering what a comment meant (whether from bad writing or clumsy phrasing) are much better if you do the analysis promptly and preferably within a day of the evaluation sessions.Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark. Analysis and Interpretation of User Observation CHAPTER 11 337 INTERPRETATION OF USER-OBSERVATION DATA Once you have analyzed your data – for example, by grouping them according to a coding scheme – your final step is interpretation: deciding what caused the defects that you have identified and recommending what to do about them. In Table 11.4, we suggest a template for gathering defects and interpretations. Again, some sample data have been entered into the table for the purposes of illustra- tion. For the example task, because the defect is related to the first action of the task and the task cannot be accomplished until the user chooses the right menu item, we have assigned a severity rating of “High ...