![]() ![]() Writing a good task scenario takes some practice: don’t lead the users, don’t make it impossible and have some predefined and specific success criteria (see Dumas & Redish chapter 12). You can’t improve a 100% completion rate, but you can improve a task that users struggle to complete and thought was difficult. Such subjective measures are especially helpful when you already have high completion rates. By improving the mean rating over time you can show how designs improved the user experience. What is largely a qualitative activity (looking for and describing design problems) is easily quantified by collecting simple pass/fail metrics and reporting completion rates.Īsking just a single question on how difficult users thought a task was to complete is also valuable. Watching just one user painfully struggle through a common-task can make a lasting impression on developers and product managers and makes for a persuasive highlight-video. ![]() By observing users attempting these tasks you can obtain a wealth of information on interaction strengths and weaknesses. In a usability test users are asked to complete a set of representative tasks. The gap in expectations can be a powerful predictor of usability problems–something recently seen on eBay. It turns out the task description reveals much of the task’s complexity, so users can predict actual task ease and difficulty reasonably well. Ask a user to complete a task and they can tell you how difficult it was to complete.īut can a user tell you how difficult the task will be without even attempting it?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |