COSC3461 User Interface Design in the Workplace

3461 Human Factors - Textbook Definition n Human factors is the discipline that tries to optimize the relationship between technology and the human (Kantowitz and Sorkin, 1983). n The goal of human factors is to apply knowledge in designing systems that work, accommodating the limits of human performance and exploring the advantages of the human operator in the process (Wickens, 1984).

3461 Human factors work (which encompasses UI design) has a rich history in life critical fields including: military aviation medical However, for most consumer products are being marketed little to no human factors work has been conducted.

3461 UI work during the product cycle is often not conducted to cut costs, even though not doing so leads to much greater costs in terms of higher customer support, slower market acceptance, and lower consumer satisfaction. (ex. Nortel in laid off every human factors professional in its organization.) Overemphasis in being first to market. (Newton vs. Palm Pilot)

3461 About Face (1995) Alan Cooper There is a conflict of interest in the world of software development because the people who build it are also the people who design it. If carpenters designed houses, they would certainly be easier or more interesting to build, but not necessarily better to live in. The architect, besides being trained in the art of what works and what doesn't, is an advocate for the client, for the user. (p. 23) Eventually, we will see a bifurcation in the industry: Designers will design the software and engineers will build it. This is currently considered a luxury by those development shops that haven't realized the fiscal and marketing advantages that come with professional software design. (p. 2f.)

3461 Organization- (User-Centered Roles) n Graphic Designers n GUI Programmers (Software Developers) n UI Designers n Usability Testers n Technical Writers/Documentation n Marketing

3461 Comparing the skills (Graphic Designers, GUI Programmers, UI Designers, Usability Testers, Technical Writers, and Marketing) (1 of 6) Graphic Designer n Creating recognizable images, intuitive symbols n Aesthetic appeal n Making best use of the available display medium n Conveying function graphically n Visual consistency n Layout Adapted from Johnson, J. (2000) GUI Bloopers, p.419

3461 Comparing the skills (Graphic Designers, GUI Programmers, UI Designers, Usability Testers, Technical Writers, and Marketing) (2 of 6) GUI Programmer n Programming, implementation, internal architecture n Knowledge of GUI toolkit n Maximizing performance n Understanding technical constraints on implementation Adapted from Johnson, J. (2000) GUI Bloopers, p.419

3461 Comparing the skills (Graphic Designers, GUI Programmers, UI Designers, Usability Testers, Technical Writers, and Marketing) (3 of 6) UI Designer n Task analysis, conceptual design n UI design with task flow and context n Specifying real-time responsiveness criteria n Assessing conformance to usability standards n Layout Adapted from Johnson, J. (2000) GUI Bloopers, p.419

3461 Comparing the skills (Graphic Designers, GUI Programmers, UI Designers, Usability Testers, Technical Writers, and Marketing) (4 of 6) Usability Tester n Ability to recruit participants, users n Usability evaluation, usability testing n Knowledge of “thinking aloud” protocol and “active listening” n Conduct surveys, panel sessions, focus groups, interviews, observational studies n Statistical analysis, experimental design

3461 Comparing the skills (Graphic Designers, GUI Programmers, UI Designers, Usability Testers, Technical Writers, and Marketing) (5 of 6) Technical Writer (Documentation) n Ability to develop customer/market driven documentation n Screen readability and organization n Strong writing skills, ability to convey highly technical information clearly n Variety of presentation methodologies

3461 Comparing the skills (Graphic Designers, GUI Programmers, UI Designers, Usability Testers, Technical Writers, and Marketing) (6 of 6) Marketing n Knowledge of customer (vs. user!) n Economic Trend Analysis n Political and Social Analysis n Product and Service Analysis n Market Potential Analysis n Knowledge of Packaging, Pricing, Distribution, Advertising, Promotion, Publicity n Development of Overall Strategy

3461 Examples of the kind of work UI Designers are trained to do: n Reduce the number of commands in an application from several hundred to 48 n Flatten its menu hierarchy from four levels to two n Decrease the total number of windows from 23 to 11 n Eliminate half of the mouse actions formerly required to complete a common task n Revise the menu commands to be consistent n Rewrite error messages that provide solutions rather than merely describe problems Adapted from Johnson, J. (2000) GUI Bloopers, p.417

3461 Usability Testing- Definition Usability testing is a method by which users of a product are asked to perform certain tasks in an effort to measure the product's ease-of-use, task time, and the user's perception of the experience. Changes are made to the application or site based on the findings of the usability tests. Usability test participants are encouraged to think aloud and voice their every opinion. Usability testing is best used in conjunction with a user-centered design process, a method by which a product is designed according to the needs and specifications of users. Adopted from

3461 The User-Centered Design Process n Three major components: –Early focus on users and tasks –Empirical measurement –Iterative design n In practice software development often involves incremental changes rather than the creation of an entirely new product n Variety of process models in use, will now show one of them

3461 User-Centered Design Process (Usability Engineering Lifecycle) Requirements Analysis Design, Testing, & Development From Mayhew, Deborah J. (199) The Usability Engineering Lifecycle

3461 Requirements Analysis (1 of 2) From Mayhew, Deborah J. (199) The Usability Engineering Lifecycle

3461 Requirements Analysis (2 of 2) From Mayhew, Deborah J. (199) The Usability Engineering Lifecycle n User Profile : A description of the specific user characteristics relevant to UI design. n Contextual Task Analysis : A study of user’s current tasks, work-flow patterns. n Platform Capabilities and Constraints : Hardware, operating system, toolkits. n Usability Goal Setting : Minimal acceptable user performance and satisfaction criteria defined. n Style Guide : Documentation of Requirements Analysis

3461 Design/Testing/Development (1 of 4) From Mayhew, Deborah J. (199) The Usability Engineering Lifecycle

3461 Design/Testing/Development (2 of 4) From Mayhew, Deborah J. (199) The Usability Engineering Lifecycle n Work Reengineering : User task redesign, reorganization of functionality, and work-flow design. No user interface design in this step n Conceptual Model Design : Based upon previous tasks high-level design alternatives are generated. n Conceptual Model Mockups : Generate low-fidelity mock-ups for selected subsets of product functionality. n Iterative Conceptual Model Evaluation : Low- fidelity user testing with redesign & reevaluate iterations.

3461 Design/Testing/Development (3 of 4) From Mayhew, Deborah J. (199) The Usability Engineering Lifecycle n Screen Design Standards : Development of a set of product-specific standards and conventions for all aspects of detailed screen design. n Screen Design Standards Prototyping : Implement a running prototype for selected subsets of product functionality based on the Screen Design Standards. n Iterative Screen Design Standards Evaluation : Formal usability testing with redesign/reevaluate iterations until all major usability bugs are eliminated and usability goals seem within reach.

3461 Design/Testing/Development (4 of 4) From Mayhew, Deborah J. (199) The Usability Engineering Lifecycle n Detailed User Interface Design : Detailed design of the complete product user interface based on Conceptual Model and Screen Design Standards detailed in the Style Guide. n Iterative Detailed User Interface Design Evaluation : Formal usability testing conducted during product development to include unassessed subsets of functionality and categories of users.

3461 The most important factor leading to the development of usable software is: n An understanding of user needs n The right development team n In-house design standards n Early usability testing 4 Management buy-in

3461 Bottom-line Benefits of User- Centered Design Process n Greater profits due to more competitive products/services n Decreased overall development and maintenance costs n Decreased customer support costs n More follow-on due to satisfied customers From Mayhew, Deborah J. (199) The Usability Engineering Lifecycle

3461 Designing for Ease of Use Three Models n User’s Conceptual Model n Designer’s Model n Programmer's Model

3461 User’s Conceptual Model n A mental image that each user subconsciously forms as he or she interacts with the system. People create mental models by putting together sets of perceived rules and patterns in a way that explains a situation. n When users first interact with a new interface, they are likely to attempt to understand its operation in terms of roles and relationships they already understand (metaphors)

3461 Designer’s Model n The interface components and relationships intended to be seen by users and intended to become part of each user's conceptual model are described in the designer's model. This model represents the designer's intent in terms of components users will see and how they will use the components to accomplish their tasks. n The designer's model identifies objects, how those objects are represented to users, and how users interact with those objects. User oriented objects are defined in terms of properties, behaviors, and relationships with other objects.

3461 Programmer’s Model n Describes the system internals used to implement the designer's model. n For example, the designer's model might include a directory object that consists of people's names, addresses, office numbers, and so forth. The programmer’s model of the directory object might consist of records in a file, with one record for each directory entry; or, it could be a complex organization of multiple records from multiple files. n The programmer’s model implementation details from the should not be evident in the designer's model and are therefore transparent to users.