Enhanced descriptions from Syndetics:

There has been some solid work done in the area of User-Centered Design (UCD) over the last few years. What's been missing is an in-depth, comprehensive textbook that connects UCD to usability and User Experience (UX) principles and practices. This new textbook discusses a theoretical framework in relation to other design theories. It provides a repeatable, practical process for implementation, offering numerous examples, methods, and case studies for support, and it emphasizes best practices in specific environments, including mobile and web applications, print products, as well as hardware.

Table of contents provided by Syndetics

• Preface (p. xiii)
• Acknowledgments (p. xv)
• Authors (p. xvii)
• Chapter 1 Introduction to User-Centered Design (p. 1)
• Takeaways (p. 15)
• References (p. 17)
• Chapter 2 Origins (p. 19)
• 2.1 Studying Human Capability and Accommodation: The World Wars and After (1914-1976) (p. 21)
• 2.2 Making the User Relevant: The Personal Computer (1977-1994) (p. 27)
• 2.3 Integrating Iterative Usability into Business: The WWW (1995-2006) (p. 30)
• 2.4 Understanding and Designing for the User's Ubiquitous Computing Experience: Mobile, Wearable Smart Devices, and Beyond (2007-) (p. 33)
• Takeaways (p. 38)
• References (p. 40)
• Chapter 3 UCD Principles (p. 43)
• 3.1 The 10 UCD Commandments (Principles) (p. 44)
• 3.2 Thou Must Involve Users Early (p. 45)
• 3.3 Thou Must Involve Users Often (p. 46)
• 3.4 Thou Must Design for Use in Context (p. 47)
• 3.5 Thou Must Keep It Simple (p. 49)
• 3.5.1 Experts (p. 50)
• 3.5.2 Willing Adopters (p. 50)
• 3.5.3 Mainstreamers (p. 50)
• 3.5.4 Prioritize (p. 51)
• 3.5.5 Remove (p. 51)
• 3.5.6 Relocate (p. 51)
• 3.5.7 Hide (p. 52)
• 3.6 Thou Must Be Polite (p. 52)
• 3.7 Thou Must Know Your Users (p. 54)
• 3.8 Thou Must Give Users Control (p. 55)
• 3.9 Thou Must Remember to Design for Emotion (p. 56)
• 3.10 Thou Must Trust, but Verify-Triangulation Is the Key (p. 59)
• 3.11 Thou Must Discover before Designing and Delivering, and Thou Must Know That Discovery Never Ends, Even after Delivery (p. 60)
• 3.12 Rabbit (p. 62)
• Takeaways (p. 63)
• References (p. 65)
• Chapter 4 Research Users (p. 67)
• 4.1 Existing Data Analysts (p. 69)
• 4.1.1 Google Analytics and Statistical Data (p. 70)
• 4.1.2 User Forums and Customer Support (p. 72)
• 4.2 Observation (p. 74)
• 4.2.1 Site Visits (p. 74)
• 4.2.2 Fly on the Wall (p. 76)
• 4.2.3 Shadowing (p. 77)
• 4.3 Emotion Assessment (p. 78)
• 4.3.1 Emotion Heuristics (p. 78)
• 4.3.2 Enjoyability Survey (p. 79)
• 4.3.3 Method of Scoring for the Enjoyability Survey (p. 80)
• 4.3.4 Microsoft Product Reaction Cards (p. 80)
• 4.4 Self-Reporting Methods (p. 80)
• 4.4.1 Focus Groups (p. 81)
• 4.4.2 Surveys (p. 82)
• 4.4.3 Interviews (p. 84)
• 4.4.4 Diary Studies (p. 84)
• 4.5 Designer Analysis (p. 86)
• 4.5.1 Affinity Diagrams (p. 86)
• 4.5.2 Use Cases (p. 88)
• 4.5.3 Task Analyses (p. 90)
• 4.5.4 User Matrices (p. 92)
• 4.6 User and Use Diagrams (p. 94)
• 4.6.1 User Flows (p. 94)
• 4.6.2 User Journey Maps (p. 95)
• 4.6.3 Storyboarding (p. 98)
• 4.6.4 Card Sorting (p. 100)
• 4.6.5 User Profiles and Personas (p. 101)
• 4.7 Eyeguide Focus Case Study (p. 103)
• Takeaways (p. 106)
• References (p. 107)
• Chapter 5 Assess the Situation (p. 121)
• 5.1 Functional Analysis (p. 121)
• 5.2 Environmental Analysis (p. 127)
• 5.3 Organizational Analysis (p. 132)
• 5.4 Competitor Analysis (p. 135)
• 5.5 Materials Analysis (p. 138)
• 5.6 Content Analysis (p. 139)
• Takeaways (p. 143)
• References (p. 145)
• Chapter 6 Balance and Filter Design Features (p. 147)
• 6.1 Filtering Features (p. 149)
• 6.2 Talking to Clients (p. 157)
• Takeaways (p. 158)
• References (p. 158)
• Chapter 7 Build Out an Operative Image (p. 161)
• 7.1 Using the MVP (p. 162)
• 7.1.1 Creating an MVP (p. 163)
• 7.2 Paper Prototyping (p. 166)
• 7.2.1 Creating a Paper Prototype (p. 167)
• 7.2.1.1 First: Build Your Paper Prototype (p. 167)
• 7.2.1.2 Second: Define Goals for Your Paper Prototype (p. 168)
• 7.2.4.3 Third: Gather Materials for User Interaction (p. 169)
• 7.3 Example Paper Prototype (p. 169)
• 7.4 Medium-Fidelity Wireframe (p. 172)
• 7.5 Higher Fidelity Prototype (p. 174)
• 7.5.1 Focus Hi-Fi Prototype (p. 175)
• 7.6 Involving Users in Prototyping (p. 182)
• 7.6.1 Design Studio (p. 182)
• 7.6.2 Concurrent Design (p. 185)
• 7.6.3 Collaborative Prototype Design Process (CPDP) (p. 186)
• Takeaways (p. 187)
• References (p. 188)
• Chapter 8 Test the Design (p. 191)
• 8.1 Defining and Measuring with Usability Testing (p. 191)
• 8.2 Choosing a Usability Test (p. 192)
• 8.2.1 A/B Testing (p. 192)
• 8.2.2 Formative Testing (p. 193)
• 8.3 Creating a Test Plan (p. 194)
• 8.3.1 Test Goals (p. 196)
• 8.3.2 Context for Testing (p. 197)
• 8.3.3 User Profile (p. 198)
• 8.3.4 User Recruiting (p. 199)
• 8.3.5 Test Procedure (p. 200)
• 8.3.5.1 Description of Design for Testing (p. 200)
• 8.3.5.2 Test Environment (p. 200)
• 8.3.5.3 Team Roles (p. 201)
• 8.3.5.4 Test Tasks (p. 202)
• 8.3.6 Data Collection Methods (p. 203)
• 8.3.6.1 See (p. 203)
• 8.3.6.2 Say (p. 203)
• 8.3.6.3 Do (p. 204)
• 8.3.7 Data Analysis (p. 207)
• 8.4 Conducting Your Test (p. 208)
• 8.4.1 User Interaction (p. 208)
• 8.4.2 Test Script (p. 208)
• 8.4.3 Error/Observation Notes (p. 211)
• 8.5 Analyzing Your Data (p. 212)
• 8.6 Why You Need Usability Testing (p. 214)
• Takeaways (p. 215)
• References (p. 216)
• Chapter 9 RIDE (Report, Iterate, Deploy, Evaluate) (p. 225)
• 9.1 Report (p. 226)
• 9.1.1 Report Format (p. 232)
• 9.1.2 Types of Reporting (p. 232)
• 9.1.2.1 Informal Deliverable to Test Team (p. 232)
• 9.1.2.2 Presentation Format (p. 234)
• 9.2 Icerate (p. 236)
• 9.3 Deploy and Evaluate (p. 237)
• Takeaways (p. 237)
• References (p. 238)
• Chapter 10 International UCD (p. 239)
• 10.1 What Is International UCD? (p. 239)
• 10.2 Researching International Users (p. 240)
• 10.3 Understanding International Use Situations (p. 242)
• 10.4 Choosing between Internationalization and Localization (p. 243)
• 10.4.1 Internationalization (p. 243)
• 10.4.2 Localization (p. 245)
• 10.5 Designing for Internationalization (p. 247)
• 10.6 Designing for Localization (p. 248)
• 10.7 Building and Testing Prototypes for International Users (p. 249)
• 10.7.1 Minimum Viable Products (MVPs) (p. 249)
• 10.7.2 Paper Prototyping (p. 250)
• 10.8 Conducting Usability Tests with International Users (p. 252)
• 10.8.1 Location (p. 252)
• 10.8.2 Translation and Localization of Scenarios and Tasks (p. 253)
• 10.8.3 Method Selection (p. 253)
• Takeaways (p. 254)
• References (p. 255)
• Chapter 11 Hardware UCD (p. 257)
• 11.1 Team Dynamics in Hardware Development (p. 259)
• 11.2 Materials, Tools, and Costs (p. 261)
• 11.3 Prototype Iteration and Testing (p. 261)
• 11.4 Low-Fidelity, Partial Prototypes Are Just Fine (p. 262)
• 11.4.1 Avoid Too Much White Space (p. 266)
• 11.4.2 Get Out of the Building (GOOB) (p. 266)
• 11.4.3 Remember That Simple Is Better (p. 266)
• 11.4.1 Make Sure You Have Enough Stuff (p. 267)
• 11.4.1 Use Tools of the Trade for Higher Fidelity Prototypes (p. 267)
• References (p. 267)
• Chapter 12 Print UCD (p. 269)
• 12.1 Researching Users (p. 269)
• 12.2 Assessing the Situation (p. 271)
• 12.3 Balancing User Needs (p. 271)
• 12.4 Building an Operative Image (p. 272)
• 12.5 Testing (p. 274)
• 12.54 Iterating with Print (p. 279)
• References (p. 280)
• Chapter 13 Mobile UCD (p. 281)
• 13.1 Reduce, Minimize, Simplify (p. 282)
• 13.2 Case Study in Mobile UCD Application (p. 282)
• 13.2.1 NPS Geysers-The First Officially Sanctioned Mobile App for Yellowstone National Park (p. 282)
• 13.2.2 About Dr. Oppegaard (p. 282)
• 13.2.3 Would You Describe the NPS Geyser App and Its Features? (p. 283)
• 13.2.4 Who Were the Target Users? (p. 285)
• 13.2.5 Where Is It Used? (p. 287)
• 13.2.6 What User Research Did You Carry Out to Understand Their Needs and Wants? (p. 288)
• 13.2.7 What Work Did You Do to Assess the Situation(s) of Use? (p. 291)
• 13.2.8 What Challenges Did You Face in Balancing User Needs and Wants with Environmental, Material, and Other Factors? (p. 292)
• 13.2.9 How Many Prototypes Did You Create and of What Levels of Fidelity? (p. 292)
• 13.2.10 What Was the Value for You of Testing Users in Realistic Situations Using Prototypes of Your Product? (p. 293)
• 13.2.11 What Best Practices Can You Suggest to Readers with Regard to Building Mobile Applications? (p. 293)
• References (p. 294)
• Chapter 14 UCD Teams (p. 295)
• 14.1 Types of Teams (p. 296)
• 14.1.1 Dedicated UCD Team, Dedicated UCD Organization (p. 296)
• 14.1.2 UCD Representative as Part of Dedicated or Ad Hoc Development Team (p. 297)
• 14.1.2.1 Dedicated Development Team (p. 297)
• 14.1.2.2 Ad Hoc UCD Team (p. 298)
• 14.2 UCD Team Roles (p. 299)
• 14.2.1 Lone Wolf UCD (p. 299)
• 14.2.2 UCD Team Manager (p. 300)
• 14.2.3 Team Management Best Practices (p. 300)
• 14.2.3.1 Put It in a Plan (p. 300)
• 14.2.3.2 Put On a Show (p. 301)
• 14.2.3.3 Put Users on Your Team (p. 302)
• 14.2.3.4 Put the Right Skills on Your Team (p. 302)
• 14.2.3.5 Put In Time to Practice Sharing, Experimenting, and Solving Together (p. 303)
• 14.2.3.6 Put It on the Board (p. 303)
• 14.2.3.7 Put Everything on the Table and Talk about It Openly (p. 304)
• 14.2.3.8 Put Yourself in the Right Position to Advocate for Your Team (p. 304)
• 14.2.3.9 Put Away Old Ways of Thinking about How to Work (p. 305)
• 14.3 Effective Team Member Qualities (p. 306)
• References (p. 307)
• Chapter 15 UCD Tools and Technologies (p. 309)
• 15.1 User Research Tools (p. 310)
• 15.1.1 Pendo (p. 310)
• 15.1.2 SurveyMonkey (p. 310)
• 15.1.3 Other User Research Tools (p. 311)
• 15.2 Product Prototyping Tools (p. 311)
• 15.2.1 Axure (p. 311)
• 15.2.2 Pencil Project (p. 311)
• 15.2.3 POP (p. 313)
• 15.2.4 Other Prototyping Tools (p. 313)
• 15.3 User Testing Tools (p. 314)
• 15.3.1 Techsmith Morae (p. 314)
• 15.3.2 Silverback (p. 314)
• 15.3.3 UserTesting (p. 314)
• Index (p. 317)

Author notes provided by Syndetics

Dr. Brian Still has more than 15 years of industry experience, working in both the private and governmental sectors, as a technology developer, manager, and evaluator. He has directed the TTU Usability Research Lab since 2006, managing a number of user experience (UX) design and testing projects for a wide range of clients, and generating a number of publications, including a highly respected collection, Usability of Complex Systems: Evaluation of User Interaction, edited with Michael Albers and published by CRC Press in 2011. In the same year Dr. Still spun off a startup from TTU, Grinbath (now called EyeGuide), based around eye tracking technology he helped invent and patent. For the last 4 years EyeGuide has made (drawing on sound UX design principles) three different eye tracking research and control systems, selling them to clients around the world.

Dr. Kate Crane is an assistant professor of technical communication at Eastern Washington University. Her current research focuses on document modality and usability, but her larger interests include usability testing, eye-tracking methodology, and user-centered design (UCD). In addition to her own research, she has worked on UCD and usability projects for EyeGuide and the University of North Texas Libraries' Portal to Texas History. Dr. Crane previously served as the assistant director of the Usability Research Lab at Texas Tech University, where she earned her PhD in technical communication and rhetoric.