Lecture 5 – User-oriented Design Mark Woehrer CS 3053 - Human-Computer Interaction Computer Science Department Oklahoma University Spring 2007 [Taken from Stanford CS147 with permission] CS 3053 - Mark Woehrer -
Learning Goals for Today • Have an overview of the Interaction Design process in general and the specific way it will be applied in this course • Have a broad understanding of what “Design” means for this course • Learn a first level of detail about the steps we will be employing in the project • Understand how users can be involved in the design process CS 3053 - Mark Woehrer -
User Centered Design • Users’ tasks and goals are the driving force behind development • Users are consulted throughout development • All design decisions are taken from within the context of the users, their work, and their environment CS 3053 - Mark Woehrer -
What is Design (Kelley) • Not just problem solving – Creative leap • Messy – No right answer • Takes a point of view – or many • Calls for vision and multiple minds • Open attitude – many solutions • Learned from experience with reflection • Requires a feel for the materials • Starts with broadening, followed by narrowing • Requires ongoing mindfulness CS 3053 - Mark Woehrer -
Design phases (IDEO) • Understand - broad direction • Observe - character maps • Visualize and Predict - story boards • Evaluate and Refine - user testing, iterative model • Implement - pragmatic aspects CS 3053 - Mark Woehrer -
Simple Iterative Model NEEDS DESIGN EVALUATE IMPLEMENT • Modified from p. 186 in Interaction Design CS 3053 - Mark Woehrer -
Needs Analysis NEEDS DESIG N EVALUATE IMPLEMENT CS 3053 - Mark Woehrer -
Contextual Inquiry (ID p.296) • Designer is apprentice to Interviewee • Context - Interviewee’s workplace • Partnership - Interviewer is not in control • Interpretation - Shared understanding • Focus - Discussion is pertinent to the design CS 3053 - Mark Woehrer -
Contextual Inquiry Interviews (ID p.299) • Short, 2-3 hours • Focused • Inquire about work behaviors, designer does not participate • Intention is to design a new system http://www.usability.gov/methods/contextual.html CS 3053 - Mark Woehrer -
Capturing the Data • Observer’s head • Written notes • Sketches and photos of the setting • Audio (or even Video) CS 3053 - Mark Woehrer -
Idea Generation NEEDS DESIG N EVALUATE IMPLEMENT CS 3053 - Mark Woehrer -
Brainstorming • Group vs. Individual Creativity • More Ideas == More Creative == Better • Limited Time • Keep a Record • Brainstorm in Section this week! Brainstorming is not just a good idea but an inexhaustible source of inspiration and fresh thinking (IDEO) CS 3053 - Mark Woehrer -
The Rules According to IDEO • Be Visual • Defer judgment • Encourage Wild Ideas • Build on the Ideas of Others • Go for Quantity • One Conversation at a Time • Stay Focused on the Topic CS 3053 - Mark Woehrer -
Exploring Design Ideas NEEDS DESIG N EVALUATE IMPLEMENT CS 3053 - Mark Woehrer -
Sketches From a previous cs147 project… CS 3053 - Mark Woehrer -
Storyboards http://www.storyboards-east.com/sb_dismoi.htm CS 3053 - Mark Woehrer -
Storyboards CS 3053 - Mark Woehrer -
Storyboards CS 3053 - Mark Woehrer -
Flipbook CS 3053 - Mark Woehrer -
Flipbook CS 3053 - Mark Woehrer -
Flow Diagrams From a previous cs147 project… CS 3053 - Mark Woehrer -
Woah Nelly…! • Sketches, Storyboards, Flipbooks, Diagrams • What’s the Di fg erence? • When to use them? • Why to use them? • Who’s the audience? • Deliverable: Storyboard only • But, try as many as you can http://www.stanford.edu/class/cs147/project/04-storyboards.html CS 3053 - Mark Woehrer -
Recommend
More recommend
