1. World Usability Day Ignite! Session Fixing The Trouble with Computers: User Centered Design, Development, and Deployment Jay Edwin Gillette Center for Information and Communication Sciences Ball State University

2. Fixing The Trouble with Computers Influential books in a professional career: Thomas K. Landauer (1995). The Trouble with Computers: Usefulness, Usability, and Productivity. Cambridge, MA: MIT Press.

3. Landauer: The Trouble with Computers is bad design, bad human interface Productivity increases with computers is an unproven, overrated thesis; jury is out, though CW says it must be so  advanced by “technology experts” like Alan Greenspan; (ICT people may know better)  how many hours have you spent “saving time” using computers? The reason information & communication technology (ICT) is counter-productive is bad design [MS software]  JEG “most American business works at C level”

4. Characteristics of Design: Tom Peters “Design is...” (Examples from Essay 98 in The Pursuit of Wow! ) 1. 200,000 different things to 200,000 different people. 5. An easy-to-use FedEx airbill. 14. A visceral understanding that design is a/the way to differentiate a product or service. 21. An attitude about life. nn. [You say]...

5. Characteristics of Design--Design is: Creative Personal Social Maya Lin: “Everything you need it to be, not everything you want it to be.”

6. User-Centered Design vs. System- Centered Design User-Centered = “User-driven” design, focus on the user –What’s good for the user System-Centered design, focus is on what’s good for the system –User must adapt to the system, not system adapting to the user

7. Landauer’s Concept of UCD3 UCD3 violates the first rule of acronyms [one meaning rule] UCD3 = –User-Centered Design –User-Centered Development –User-Centered Deployment UCD3 is a cycle, with the user in common

8. Usefulness and Usability Landauer (pp. 141-144) Usefulness—does it help? Usability—how “easy” is it to use? (that is, how effectively can the user use it?)

9. User-Centered Design Methods Landauer (key Chapter 12) “This chapter says most of what needs reading before getting started. The best next step is doing. Nobody has a magic formula beyond the general kinds of activities in which to engage. Little extra knowledge is essential.” [p. 277]

10. Formative vs. Summative Design Evaluation Landauer (key section, p. 281) Formative evaluation guides changes Summative (“summary”) evaluation tests “how good” the finished system is “Iterative development = formative design evaluation”

11. Landauer’s Task Analysis Learn the Job Consult the Users Use Subject Matter Experts (SMEs) Conduct Time & Motion Studies Consult Normal Business Records

12. “Fixing The Trouble with Computers: User Centered Design, Development, and Deployment” Contact: Dr. Jay Edwin Gillette Center for Information and Communication Sciences Ball State University Muncie, IN 47306 USA 765.285.1889 jaygillette@bsu.edu © 2012 by Jay Edwin Gillette