1. University of Washington HCDE 518 & INDE 545 UCD Process HCDE 518 & INDE 545 Winter 2012 With credit to Jake Wobbrock, Dave Hendry, Andy Ko, Jennifer Turns, & Mark Zachry

2. University of Washington HCDE 518 & INDE 545 Agenda  Announcements  Lecture & Discussion – UCD Process  Break – 5 mins  Project Info  Next class  Group

3. University of Washington HCDE 518 & INDE 545 UCD PROCESS

4. University of Washington HCDE 518 & INDE 545 Why a Design Process?  It helps us get started with a proven tack  It prevents “designer's block”  It keeps us directed toward a final product  It helps us stay on schedule and within cost  It helps us measure design progress  It helps us communicate where we are to others  It prevents us from omitting important steps  It is more reliable than intuition  It forces us to iterate!  It helps us keep the user first!

5. University of Washington HCDE 518 & INDE 545 Designers' Expertise…  …lies not in the thing he or she is designing  e.g., shopping carts, cell phones, pencils  You do not have to be a widget expert to be a designer of a widget-manufacturing interface  In fact, if you were, it would probably stifle you (Why?)  These people suffer from their expert blind spots  Think of helping your parents with computers  Instead, you must be an expert in the process of design

6. University of Washington HCDE 518 & INDE 545 What is Designed?  Artifact view: The object, device, or system that is designed  Holistic view: The interaction, the flow, the user's experience is designed  all potential users (often > 1)  all other stakeholders  manuals  tutorials  help systems  customer support  …  Think in terms of users' goals  Artifacts have no goals  People have goals!  Keep users in the center in the beginning, middle, and end

7. University of Washington HCDE 518 & INDE 545 Design Process? NO! WRONG!

8. University of Washington HCDE 518 & INDE 545 Design Requires Iteration

9. University of Washington HCDE 518 & INDE 545 Stage Goals Learn about stakeholders Discover goals and needs How is it done now? What is wanted? What else has been tried? Generate lots of ideas Grasp issues and potential solutions Produce something tangible Identify challenges Uncover subtleties Discover problems Assess progress Determine next steps Build final product Ramp up marketing, support, and maintenance

10. University of Washington HCDE 518 & INDE 545 What about Engineering?  What about writing production-level code?  What about quality assurance (QA)?  Bug fixing?  Feature requests?  Feature creep?  The software design process and the software engineering processes must work together

11. University of Washington HCDE 518 & INDE 545 Investigate

12. University of Washington HCDE 518 & INDE 545 Why investigate?  You cannot design apart from the world in which your users and design will live

13. University of Washington HCDE 518 & INDE 545 Investigation Questions  Identify users  Identify stakeholders  What are the requirements?  How do they do it now?  How long does it take?  What do they want?  What do they need?  What else have they tried?  Is there already another solution?

14. University of Washington HCDE 518 & INDE 545 Ideate

15. University of Washington HCDE 518 & INDE 545 Ideation  Ideation = “idea generation”  Volume matters most!  To increase the chances for success by considering a huge volume of ideas in a systematic way  One of the worst things you can do is go with the first idea that you get  You can always come back to it later

16. University of Washington HCDE 518 & INDE 545 Prototype

17. University of Washington HCDE 518 & INDE 545 Why prototype?  It is hard to evaluate something that does not exist  It is hard for users to react to abstract concepts  Prototyping brings subtleties and nuances into the light  Begin to wrestle with the technical constraints

18. University of Washington HCDE 518 & INDE 545 Evaluate

19. University of Washington HCDE 518 & INDE 545 Evaluation, why do we need it?  Automated procedures can find bugs, but not usability problems  (active research area, but hard!)  You can't iterate without knowing what to fix, leave, or remove  Answers both questions:  Did we build the right thing?  Did we build it right?

20. University of Washington HCDE 518 & INDE 545 Evaluation Drives Iteration  If problems are in user performance  Probably need to return to prototyping phase  If problems are in conceptual model and how users understand it  Probably need to return to ideation phase  If problems are in usefulness or appropriateness  Probably need to return to investigation phase

21. University of Washington HCDE 518 & INDE 545 Produce

22. University of Washington HCDE 518 & INDE 545 Production  “Production” refers to all steps required to go from a functional prototype to a release candidate  Software architecture  Programming, building  Manufacturing  Help systems  Manuals  Training  Customer support  Marketing  Branding  Distribution

23. University of Washington HCDE 518 & INDE 545 Design Processes  There is no agreement on an exact design process  For each process shown  What do you like about it?  What do you not like about it?  What is missing?  What is superfluous?

24. University of Washington HCDE 518 & INDE 545 Moggridge 07 Design Process What do you like about it? What do you not like about it? What is missing? What is superfluous?

25. University of Washington HCDE 518 & INDE 545 ISO 13407 (from Maguire) What do you like about it? What do you not like about it? What is missing? What is superfluous?

26. University of Washington HCDE 518 & INDE 545 Dix 04 What do you like about it? What do you not like about it? What is missing? What is superfluous?

27. University of Washington HCDE 518 & INDE 545 Simple View What do you like about it? What do you not like about it? What is missing? What is superfluous?

28. University of Washington HCDE 518 & INDE 545 Apple What do you like about it? What do you not like about it? What is missing? What is superfluous?

29. University of Washington HCDE 518 & INDE 545 HCDE 518 class model What do you like about it? What do you not like about it? What is missing? What is superfluous?

30. University of Washington HCDE 518 & INDE 545 Comparing the Processes  What do they all have in common?  What seem to be the main components?

31. University of Washington HCDE 518 & INDE 545 Summary  Design is a highly iterative process  Design processes must keep the user’s interests central  Design starts with understanding the user  Designs are never truly perfect - They can always be improved.  It is a skill to know when to stop iterating and call a design “finished”

32. University of Washington HCDE 518 & INDE 545 Break – 5 minutes

33. University of Washington HCDE 518 & INDE 545 Project Components  P0: Design Question, Team Form – 1%  P1: User Research & Personas – 10%  P2: Ideation & Sketching – 5%  P3: Lo-Fi Prototype – 9%  P4: Hi-Fi Prototype – 10%  P5: Design Spec w/ Evaluation – 10%

34. University of Washington HCDE 518 & INDE 545 P0 – Design Question & Team Form  Determine your project design question & at least 3 research questions  More at end of lecture on how to do this  Complete team form  http://courses.washington.edu/hcde518/project/ P0-TeamForm.doc http://courses.washington.edu/hcde518/project/ P0-TeamForm.doc  Due next Wednesday, January 18th

35. University of Washington HCDE 518 & INDE 545 P1: User Research & Personas  Define stakeholders  Choose 3 user research methods and apply them to your problem  e.g., interviews, contextual inquiry, survey, observations, diary studies  Come up with design requirements  Design at least 3 personas

36. University of Washington HCDE 518 & INDE 545 P2: Ideation & Sketching  As a group, brainstorm at least 30 ideas for potential solutions to your users’ problem  Use methods from class to help narrow down the sketch ideas to the best three

37. University of Washington HCDE 518 & INDE 545 P3: Lo-Fi Prototype + Eval  Construct a prototype of your most promising solution ideas using paper, cardboard, etc.  Do an evaluation of the prototype with 3+ users

38. University of Washington HCDE 518 & INDE 545 P4: Hi-Fi Prototype + Eval  Fix issues then construct a prototype closer to final representation  Can be whatever method you choose  We will discuss numerous types in class  Powerpoint, Photoshop, software, interactive, video, etc.  Does not have to be functional, just represent actual user experience  Deliverable is in-class presentation + demo

39. University of Washington HCDE 518 & INDE 545 P5: Design Specification  Write up a final design spec outlining details of your design solution and the rationale behind them  Your audience would be engineers who would actually build the product

40. University of Washington HCDE 518 & INDE 545 General Advice  Spend a lot of time gathering information  Do what makes sense, not what you know how to design for  Look for ways to leverage stakeholder's interests  Face time is worth a lot, try to work with other group members around if you can  Have a specific stakeholder, design for someone in particular

41. University of Washington HCDE 518 & INDE 545 DESIGN QUESTIONS

42. University of Washington HCDE 518 & INDE 545 What is a Design Question?  Usually asks how something which doesn’t already exist can solve a problem  Often starts with “How can…?”  Examples:  How can technology help reduce stress surrounding everyday home life?  How can we design something to help keep up with home maintenance?

43. University of Washington HCDE 518 & INDE 545 Design Questions vs. Research Questions  These are all design questions  How can busy parents find time to relax and reduce anxiety?  How can technology promote healthy sleep habits?  How can we reduce information overload?  How can college students manage their many distractions and find time to concentrate?  How can mobile technology promote leisure activities?  What is a way to support individuals while on vacation?  Why type of technology can promote meditation and focus and reduce stress?  The answer to them is a thing (artifact, system, etc.)  Research questions are different  The answer to these are knowledge  How do people currently relax?  What are things that people bring with them on vacation?  What are the major sources of distraction for college students?

44. University of Washington HCDE 518 & INDE 545 What is a design question that has these things as a result?  Cell phones for older people  The HCDE 518/INDE 545 website  A USB drive  Scissors  A toaster  World of Warcraft

45. University of Washington HCDE 518 & INDE 545 Specificity -> Scope  How specifically you word your design question will affect how much you need to do and how many people you need to design for  For your project, you'll need to scope your design problem to something you can complete this quarter  Obviously, you can't solve the problem of information overload in the next 8 weeks  This can be done by choosing a part of the problem and/or narrowing it down to a more specific audience

46. University of Washington HCDE 518 & INDE 545 Evolution of Questions  Your question may not stay exactly the same throughout the project  Your user research may show that it's not actually a problem, or that technology is not the solution  You may find that your scope is too large or too narrow  Your design question can evolve over time, and become more or less specific, but you should always have a current design question your whole team agrees upon

47. University of Washington HCDE 518 & INDE 545 Be Picky About your Design Questions  Once you have a draft of a design question, take a look at each word  How do you define it? Is it necessary? Would a different word or phrase make it more clear or change the scope?

48. University of Washington HCDE 518 & INDE 545 Research Questions  Remember, the answer to these is “knowledge” as opposed to “a thing”  What do you need to know in order to come up with the answer to your design question?  Often who, what, when, where, why, how…  Good general research questions:  What is the current practice?  Who is going to use this?  What are their needs?  Again, specificity will help make your life easier

49. University of Washington HCDE 518 & INDE 545 What are some research questions for…?  How can technology help reduce stress surrounding everyday home life?  How can we design something to help keep up with home maintenance?  How can we produce a safe and secure home?  How can we keep a separation between home and work life?

50. University of Washington HCDE 518 & INDE 545 Next Class Topics  Wednesday, January 18th  Design Methods  Upcoming Work  P0  R2

51. University of Washington HCDE 518 & INDE 545 GROUP MEET & GREET TIME