He began his presentation with a reference to the "old days" when a developer's attitude was that people should be grateful just to be able to use a computer; usability was not a priority. User-centered design (UCD), a more popular concept in recent years, has been a big step forward. Key elements of UCD include:
- Focus on users' needs, tasks & goals
- Spend time on initial research (observations) and requirements (user-defined)
- Emphasize an iterative design process
- Evaluate system using real users
- Learnability (on Web, this has to be a matter of seconds)
- Efficiency of use (important if product will be used often)
- Memorability (important if product will be used intermittently)
- Errors (caused by system not being designed well enough to prevent them)
- Subjective satisfaction
His other major points that afternoon related to the ideal number of users to test with. For years we've heard him say 4-6 users, and that's still his message today. Elaborate tests are costly and intimidating; discount methods with 4-6 users can be quick, cheap and more practical. He strongly advises doing more iterative testing with small groups, rather than one large test, strengthening his argument with charts and graphs, and using terms like Lambda, which I strained my brain to understand. He adds that, while some of what each user does during a test will be different, some will be the same, and a pattern will emerge. Once a pattern is established, adding more users really doesn't add much value. I have personally experienced this as a test facilitator and observer, and I can tell you, by the 5th or 6th user, the findings start to get really boring...little new information emerges at that point.
Stay tuned for a run-down on Day 2!
No comments:
Post a Comment