Chapter 3: Managing Design Processes • 3.1 Introduction • 3.2 Organizational Design to Support Usability • 3.3 The Three Pillars of Design • 3.4 Development Methodologies • 3.5 Ethnographic Observation • 3.6 Participatory Design • 3.7 Scenario Development • 3.8 Social Impact Statement • 3.9 Legal Issues Introduction • In the beginning, users were geeks too • Today, most systems are not for geeks • Designs are improved through – Observation of users – Careful analysis of user tasks – Validation of design/ prototype – Continued user involvement • Goal should be to accommodate to the user • Managers must adapt textbook methods to their organization 3.2 Organizational Design and Support Usability • • • • • • High Level Commitment Convince Developers/ Managers Usability Group/Lab Role in Project Tools for Rapid Prototyping … this chapter focuses on design portion of project 3.3 The Three Pillars of Design • Guidelines Documents and Process • User Interface Software Tools • Expert Reviews and Usability Testing Guidelines Documents and Process • • • • Guidelines not decided in a vacuum Living Text Levels of Guidelines Each project has different needs, but guidelines should be considered for: – – – – – Words and icons Screen-layout issues Input and output devices Action sequences Training Words and icons • Terminology • Character set, fonts, font sizes, and styles • Icons, graphics, … • Use of color, emphasis Screen-layout • Menus, form fill-in, and dialog-boxes • Wording of messages • White space • Lists • Headers and footers Input and output devices • Major devices • Sounds, touch, … • Response time Action sequences • Direct-manipulation • Commands • Function keys • Error handling Training • Help • Training and reference materials 3.4 Developmental Methodologies • Six Stages of Logical User-Centered Design Methodology (Kreitzberg): • Stage 1: Develop Product Concept • Stage 2: Research and Needs Analysis • Stage 3: Design Concepts and Key Screen Prototype • Stage 4: Iterative Design and Refinement • Stage 5: Implement Software • Stage 6: Provide Roll-Out Support Stage 1: Develop Product Concept • • • • • • • Create high concept Business objectives Identify team Identify User population Prepare project plan Identify constraints Develop mockups to show non technical people Stage 2: Research and Needs Analysis • Partition the User Population • Break Job Activities into Tasks • Conduct Needs Analysis • Sketch Process Flow • Identify Major Objects • Research and Resolve Technical Issues Stage 3: Design Concepts and Key Screen Prototype • Create Specific Usability Objectives • Initiate Guidelines • Select Navigational Model and Design Metaphor • Identify Key Screens • Develop Prototype of Key Screens • Initial Reviews and Usability Tests Stage 4: Iterative Design and Refinement • Expand Key screen prototype • Conduct Heuristic and Expert Reviews • Conduct Full Scale Usability Tests • Deliver Prototype and Specification Stage 5: Implement Software • Develop Standard Practices • Manage late stage change • Develop online help, documentation, tutorials Stage 6: Provide Roll-Out Support • Training • Logging, Evaluation, Maintenance 3.5 Ethnographic Observation • Potential Dangers • Process: – Preparation – Field Study – Analysis – Reporting Preparation • Understand organization culture. • Familiarize yourself with the system • Set goals and prepare questions. • Gain access Field Study • Establish rapport. • Observe/interview users in their workplace and collect data. • Follow any leads. Analysis • Compile the data • Quantify data and compile statistics. • Interpret the data. • Refine the goals and the process used. Reporting • Consider multiple audiences and goals. • Prepare report with the findings 3.6 Participatory Design • More than just requirements and feedback • Plusses • Minuses • Must be managed • Appropriate level of user involvement could vary 3.7 Scenario Development • Day-in-the-life scenarios • Well established systems – can have data about frequencies of different scenarios 3.8 Social Impact Statement • potential impact on society • Produced early • Reviewed by panel and interested parties • Once approved, should be followed • At this point, merely a proposal Social Impact Statement • Describe the new system and its benefits. • Address concerns and potential barriers • Outline the development process. 3.9 Legal Issues • Privacy • Safety and Reliability • Copyright • Patents • Freedom of Speech • Access for Disabled End Chapter 3