Title Goes Here

Managing Design ProcessesSession 03Course: T0593 / Human Computer InteractionYear: 2012

3OutlineOrganization Design and Support UsabilityThe Four Pillars of DesignDevelopment MethodologiesEthnographic ObservationParticipatory DesignScenario DevelopmentSocial Impact Statement for Early Design Review4Organizational Design and Support UsabilityDesign is a creative activity whose aim is to establish the multi-faceted qualities of objects, processes, services and their systems in whole life cycles. (ICSID International Council of Societies of Industrial Design)Design is inherently creative and unpredictable. Interactive system designers must blend knowledge of technical feasibility with a mystical esthetic sense of what attracts users. hared languageOrganizational Design and Support Usability (Cont.)One Method to Characterize design (Rosson and Carrol, 2002) is:Design is a process. The design process is nonhierarchical. The process is radically transformational. Design intrinsically involves the discovery of new goals.

56The Four Pillars of Design

7The Four Pillars of Design (Cont.)User Interface RequirementsSoliciting and clearly specifying user requirements is a major key to success in any development activity Laying out the user-interface requirements is part of the overall requirements development and management processUser interface requirements describe system behavior

The Four Pillars of Design (Cont.)Guidelines documents and processes Each project has different needs, but guidelines should be considered for: Words, icons, and graphics Screen-layout issuesInput and output devices Action sequences Training

3-8The Four Pillars of Design (cont.) User-Interface Software Tools

One difficulty in designing interactive systems is that customers and users may not have a clear idea of what the system will look like when it is done. Since interactive systems are novel in many situation, user may not realize the implications of design decisions. unfortunately, it is difficult, costly, and time-consuming to make major changes to systems once those systems have been implemented.

Sophisticated tools such as Suns Java provide cross-platform development capabilities and a variety of services.3-910The Four Pillars of Design (Cont.)Expert Reviews and Usability Testing

In addition to a variety of expert review methods, test with the intended users, surveys, and automated analysis tools are proving to be valuable.Procedures vary greatly depending on the goals of the usability study, the number of expected users, the danger of errors, and the level of investment11Development MethodologiesThere are dozens of advertised development methods, one of them is The Rapid Contextual Design Method (Holtzblatt et al.).The rapid contextual design method involves the following steps:1. Contextual Inquiry2. Interpretation sessions and work modeling3. Model Consolidation and affinity diagram building4. Persona Development12Development Methodologies (cont.)The rapid contextual design method involves the following steps (cont.):5. Visioning6. Storyboarding7. User environment design8. Interviews and evaluations with paper prototypes and mock-ups.

13Ethnographic ObservationPreparationUnderstand organization policies and work culture. Familiarize yourself with the system and its history. Set initial goals and prepare questions. Gain access and permission to observe/interview.

Field StudyEstablish rapport with managers and users. Observe/interview users in their workplace and collect subjective/objective quantitative/qualitative data. Follow any leads that emerge from the visits. 14Ethnographic Observation (cont.)AnalysisCompile the collected data in numerical, textual, and multimedia databases. Quantify data and compile statistics. Reduce and interpret the data. Refine the goals and the process used.

ReportingConsider multiple audiences and goals. Prepare a report and present the findings.

15Participatory Design(Source : Pearson Addison Wesley, 2010)

16Participatory Design (cont.)Controversial More user involvement brings: more accurate information about tasks more opportunity for users to influence design decisions a sense of participation that builds users' ego investment in successful implementation potential for increased user acceptance of final system 17Participatory Design (cont.)On the negative side, extensive user involvement may: be more costly lengthen the implementation period build antagonism with people not involved or whose suggestions rejected force designers to compromise their design to satisfy incompetent participants build opposition to implementation exacerbate personality conflicts between design-team members and users show that organizational politics and preferences of certain individuals are more important than technical issues 18Participatory Design (cont.)

19Scenario DevelopmentDay-in-the-life scenarios: characterize what happens when users perform typical tasks can be acted out as a form of walkthrough may be used as basis for videotape useful tools table of user communities across top, tasks listed down the side table of task sequences flowchart or transition diagram 20Social Impact Statement for Early Design ReviewDescribe the new system and its benefitsConvey the high level goals of the new system. Identify the stakeholders. Identify specific benefits21Social Impact Statement for Early Design Review (cont.)Address concerns and potential barriersAnticipate changes in job functions and potential layoffs. Address security and privacy issues. Discuss accountability and responsibility for system misuse and failure. Avoid potential biases. Weigh individual rights vs. societal benefits. Assess trade-offs between centralization and decentralization. Preserve democratic principles. Ensure diverse access. promote simplicity and preserve what works. 22Social Impact Statement for Early Design Review (cont.)Outline the development processPresent and estimated project schedule. Propose process for making decisions. Discuss expectations of how stakeholders will be involved. Recognize needs for more staff, training, and hardware. Propose plan for backups of data and equipment. Outline plan for migrating to the new system. Supporting Materialswww.infodesign.com.au/ftp/ParticipatoryDesign.pdf23Q & A24