Usability intro 419
0 likes558 views
The document discusses usability and defines it as the effectiveness, efficiency, and satisfaction with which users can achieve tasks. It notes that high usability means a system is easy to learn and remember, efficient, visually pleasing, and fun to use, and quick to recover from errors. It emphasizes that usability is about designing and writing with end users in mind through revision and testing. The focus is on writing professional documents like status reports, evaluations, summaries, and reports in this class.
Usability intro 419
- 2. Usability (n): The effectiveness, efficiency, and satisfaction with which users can achieve tasks in a particular environment of a product. Wednesday, January 18, 12
- 3. High usability means a system is: Wednesday, January 18, 12
- 4. easy to learn and remember Wednesday, January 18, 12
- 5. efficient, visually pleasing, and fun to use Wednesday, January 18, 12
- 6. quick to recover from errors Wednesday, January 18, 12
- 7. Wednesday, January 18, 12
- 8. If your audience finds your document difficult to use, it doesn’t mean that they’ve failed. Wednesday, January 18, 12
- 9. It means that you failed them. Wednesday, January 18, 12
- 10. Things should be obvious. Wednesday, January 18, 12
- 11. • Where to click • How to search • How to navigate individual pages Wednesday, January 18, 12
- 12. Bad design is one thing, but ... Wednesday, January 18, 12
- 13. context is another part of the problem. Wednesday, January 18, 12
- 14. We’d like to think of our readers as... Wednesday, January 18, 12
- 15. Wednesday, January 18, 12
- 16. Wednesday, January 18, 12
- 17. This almost never happens. Wednesday, January 18, 12
- 18. Wednesday, January 18, 12
- 19. Wednesday, January 18, 12
- 20. Wednesday, January 18, 12
- 21. Wednesday, January 18, 12
- 22. Users look feverishly for anything that is: Wednesday, January 18, 12
- 24. vaguely resembles what they’re looking for Wednesday, January 18, 12
- 25. is clickable. Wednesday, January 18, 12
- 26. Usability is mostly common sense. Wednesday, January 18, 12
- 27. We don’t read screens. Wednesday, January 18, 12
- 28. We don’t read screens. We scan screens. Wednesday, January 18, 12
- 29. We don’t make optimal choices. Wednesday, January 18, 12
- 30. We satisfice. Wednesday, January 18, 12
- 31. satisfying + sufficing = satisfice Wednesday, January 18, 12
- 32. Why not look for the best choice? Wednesday, January 18, 12
- 33. 4 Wednesday, January 18, 12
- 34. 1. We’re usually in a hurry. Wednesday, January 18, 12
- 35. 2. There’s not much of a penalty for guessing wrong. Wednesday, January 18, 12
- 36. 3. Weighing options may not improve our chances. Wednesday, January 18, 12
- 37. 4. Guessing is more fun. Wednesday, January 18, 12
- 38. Your job is to take all this into account. Wednesday, January 18, 12
- 39. Designing and writing with end-users in mind Wednesday, January 18, 12
- 40. Designing and writing with end-users in mind Wednesday, January 18, 12
- 41. Revising with end-users in mind Wednesday, January 18, 12
- 43. We’re not fixing websites in this class. Wednesday, January 18, 12
- 44. We’re making recommendations Wednesday, January 18, 12
- 45. about effective revision. Wednesday, January 18, 12
- 46. but in the process, Wednesday, January 18, 12
- 47. you’ll write. a lot. Wednesday, January 18, 12
- 48. Professional Writing Wednesday, January 18, 12
- 49. Status Reports Heuristic Evals Testing Materials Executive Summaries Testing Reports Performance Evals Wednesday, January 18, 12
- 50. This is also a class about Wednesday, January 18, 12
- 51. work. Wednesday, January 18, 12
- 52. Working ... professionally. in distributed environments. Wednesday, January 18, 12