1. ©2001 Southern Illinois University, Edwardsville All rights reserved. Today Putting it in Practice: CD Ch. 20 Monday Fun with Icons CS 321 Human-Computer Interaction

2. ©2001 Southern Illinois University, Edwardsville All rights reserved. Practicing Participatory Design Design the Process No single process works for every problem Know the intent of each step and choose which ones fit the project  What point are you coming into the project? –At the beginning, somewhere in the middle, at the end?  Is this a new system or a re-design of an existing one?  What access do you have to the users?  How much time is devoted to design?

3. ©2001 Southern Illinois University, Edwardsville All rights reserved. The Techniques Contextual Inquiry Interpretation Sessions Work Models Consolidated Models Affinity Diagram Visioning Story Boards UED/UI Paper Prototypes

4. ©2001 Southern Illinois University, Edwardsville All rights reserved. Design Principles: Principle of Data Ground all design action in explicit understanding of the users and how they work Use concrete data to derive the understanding  Contextual Inquiry  Work Models  Affinity Diagram Use concrete data to justify design  Vision (Work Redesign)  Story Board  Paper prototyping More than just “User Friendly”

5. ©2001 Southern Illinois University, Edwardsville All rights reserved. Design Principles: Principle of Team Develop a shared understanding and a common team focus Use external representations to develop a common vision  Interpretation sessions, affinity diagram, work models, UED  “Working-on-the-Wall” Bring different perspectives together  X-func team: cross functional team Effective team work depends on being able to manage team meetings  Define roles  Define the process  Maintain focus  Maintain team memory

6. ©2001 Southern Illinois University, Edwardsville All rights reserved. Design Principles: Principle of Design Thinking Alternate between working and reflecting Reflecting provides a check of coherent structure, consistency, and completeness Reflecting reminds the team about what each step reveals. Each transformation acts like a walkthrough of the design  From raw data to the interpretation  From the interpretation to a vision  From a vision to a design  From a design to a usability test

7. ©2001 Southern Illinois University, Edwardsville All rights reserved. INTENT STEPCUSTOMER DATADESIGN THINKINGTEAM AND ORGANIZATION Contextual Inquiry  Gather detailed data needed for design  Discover implicit aspects of work that would normally be invisible  Put technical experts in the customer data  Stimulate the recognition of implications for design  Build the team through shared experiences  Collect concrete data to resolve conflicts Interpretation Sessions  Use the while team’s perspective to see what matters in the work  Capture all aspects of one customer’s work efficiently  Manage the good of insight from all team members  Capture design ideas as they come  Share preliminary design ideas to start cross-pollination  Bring multiple perspectives to bear on the data  Teach team members the perspectives of other organizations  Keep everyone engaged in processing the data Work models  Create a coherent representation of work practice  Record actual user data to check the system  Distinguish between opinions and real data  Reveal aspects of work that matter for design  Capture elements of work in a tangible form  Feed market stories, scenarios, and planning  Create a culture in which concrete data is the basis for making decisions Affinity diagram  Organize data across all customers to reveal scope of issues  Provide a review of the data prior to consolidating and visioning  Identify holes in the data  Push from point fixes to systemic solutions  Introduce inductive thinking  Allow individuals to develop their responses to the data  Share design ideas without evaluation  Drive consensus about what the data means  Make data easy to share  Make key customer issues stand out Create the first step toward corporate knowledge of their customer Work model consolidation  Create one statement of the customer population  Show common structure without losing variation across customers  Reveal implications for design through dialog with each model  Create a map of customer population for planning, sharing, and reuse  Make it possible to validate understandings with customers

8. ©2001 Southern Illinois University, Edwardsville All rights reserved. INTENT STEPCUSTOMER DATADESIGN THINKINGTEAM AND ORGANIZATION Vision  Respond to the data with new work practice designs  Shift the team's focus from tools to work practice  Create a coherent response by reacting to the data rapidly  Generate divergent options before deciding on one  Separate evaluation from generation of ideas  Develop design ideas together as a team  Defuse ownership in ideas Storyboards  Redesign work practice, not technology  Ground redesign in consolidated data  Ensure redesigned work  practice hangs together  Work out details of vision sequentially  Let designers think in the U1 without committing to it  Create a public representation of a task for sharing and checking  Enable parallel design work in small teams User Environment Design  Design the user's experience of the system to be coherent  Allow different user scenarios to be checked in the system  Make the system work model explicit  Show relationships between parts of the system  Find errors in system structure before coding  Drive later object modeling  Separate out the UI conversation  Make the system structure explicit and sharable  Show the relationship between systems  Provide a tool for planning and coordinating multiple systems and teams  Provide a high-level specification Paper prototyping  Check system structure and user interface with customer  Let the customer communicate in their own language  Get an additional layer of detailed data about actions within the system  Check sales point of potential  Provide a fast way to check design alternatives  Learn to separate UI from structural implications  Create and test ideas quickly to prevent over-attachments  Ensure a shared understanding of what customers find valuable  Share ideas in terms that customers and management can understand

9. ©2001 Southern Illinois University, Edwardsville All rights reserved. Senior Project Please remember what you learn here for Senior Project HCI Lab is available for Senior Project Check out Senior Projects at: http://www.cs.siue.edu/SeniorProjects/index.htm