User-centered approaches to interaction design By Haiying Deng Yan Zhu.

Slides:



Advertisements
Similar presentations
Testing Relational Database
Advertisements

Division of Information Management Engineering User Interface Laboratory 11 Fall 09 Human Interface UI Evaluating Design Proposals for Complex Systems.
Culture and Leadership
Virtual University - Human Computer Interaction 1 © Imran Hussain | UMT Imran Hussain University of Management and Technology (UMT) Lecture 20 User Research.
User-Centered Approaches to Interaction Design Keith Mogensen Ronen Waisenberg.
Chapter 9 User-centered approaches to interaction design By: Sarah Obenhaus Ray Evans Nate Lynch.
Methods: Deciding What to Design In-Young Ko iko.AT. icu.ac.kr Information and Communications University (ICU) iko.AT. icu.ac.kr Fall 2005 ICE0575 Lecture.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Tuesday Consolidation Reading: CD Ch.s 8, 9, & 10 Modeling & Interpretation.
INFO 420Chapters 4 and 5 1 SW Project Management Organization and Scope INFO 420 Glenn Booker.
William H. Bowers – Understanding Users: Qualitative Research Cooper 4.
ACTIVELY ENGAGING THE STAKEHOLDER IN DEFINING REQUIREMENTS FOR THE BUSINESS, THE STAKEHOLDER, SOLUTION OR TRANSITION Requirements Elicitation.
User-centered approaches to interaction design
COMP 6620 Chapter Presentation Karthik Vemula. Agenda:-  User Centered Approach  Basic Activities of Interaction Design.  In Class Assignment.
Information & Interaction Design Fall 2005 Bill Hart-Davidson Session 7: teams present research plan + a sequence diagram from phase 2 homework; Affinity.
Empowering Staff Through Institute Planning (ESTIP) Executive Workshop Institute Name: XXXXXX Presenter: XXXXXX Date: XXXXXX.
1 User Centered Design and Evaluation. 2 Overview Why involve users at all? What is a user-centered approach? Evaluation strategies Examples from “Snap-Together.
User-centered approaches to interaction design. Overview Why involve users at all? What is a user-centered approach? Understanding users’ work —Coherence.
User-Centered Design and Development Instructor: Franz J. Kurfess Computer Science Dept. Cal Poly San Luis Obispo FJK 2005.
Information & Interaction Design Fall 2005 Bill Hart-Davidson Session 6: analyzing work practices – rationale and challenges; the 5 Contextual Design work.
4. Interaction Design Overview 4.1. Ergonomics 4.2. Designing complex interactive systems Situated design Collaborative design: a multidisciplinary.
Contextual Design. Purpose for us An example A term often used, with varying levels of precision.
User-centered approaches to interaction design. Overview Why involve users at all? What is a user-centered approach? Understanding users’ work —Coherence.
1 User Centered Design and Evaluation. 2 Overview My evaluation experience Why involve users at all? What is a user-centered approach? Evaluation strategies.
4. Interaction Design Overview 4.1. Ergonomics 4.2. Designing complex interactive systems Situated design Collaborative design: a multidisciplinary.
Chapter 15 Ethnographic Designs
socio-organizational issues and stakeholder requirements
User Centered Design Lecture # 5 Gabriel Spitz.
Chapter 9 Teamwork and Team Performance Teams are worth the work.
Charting a course PROCESS.
Systems Life Cycle A summary of what needs to be done.
Lecture 7: User-centered approaches and Introducing evaluation.
Z556 Systems Analysis & Design Session 9 ILS Z556 1.
Gary MarsdenSlide 1University of Cape Town Human-Computer Interaction - 8 Prototyping Gary Marsden ( ) July 2002.
Advanced Topics in Requirement Engineering. Requirements Elicitation Elicit means to gather, acquire, extract, and obtain, etc. Requirements elicitation.
Chapter 10 THE NATURE OF WORK GROUPS AND TEAMS. CHAPTER 10 The Nature of Work Groups and Teams Copyright © 2002 Prentice-Hall What is a Group? A set of.
SoberIT Software Business and Engineering Institute HELSINKI UNIVERSITY OF TECHNOLOGY User Studies Basic principles, methods, and examples Sari.
Team Skill 6: Building the Right System From Use Cases to Implementation (25)
S556 SYSTEMS ANALYSIS & DESIGN Week 11. Creating a Vision (Solution) SLIS S556 2  Visioning:  Encourages you to think more systemically about your redesign.
Chapter 9: User-centered approaches to interaction design From “Interaction design: Beyond human-computer interaction” By J. Preece, Y. Rogers, H. Sharp.
Interaction Design Process COMPSCI 345 S1 C and SoftEng 350 S1 C Lecture 5 Chapter 3 (Heim)
Project design & Planning The Logical Framework Approach An Over View Icelandic International Development Agency (ICEIDA) Iceland United Nations University.
5/20/ Conducting and Analyzing a Contextual Interview ICS 205 Spring 2002 Tom Herring Ratiya Komalarachun.
Requirements Engineering Requirements Elicitation Process Lecture-8.
Chapter 4 Finding out about tasks and work. Terminology GOAL: End result or objective TASK: An activity that a person has to do to accomplish a goal ACTION:
Ethnography. Anthropological tradition: Research that focuses on culture. Focus on cultural themes of community roles and behavior Patterns of behavior,
©2001 Southern Illinois University, Edwardsville All rights reserved. Today System Design & Putting it Together Reading: ABF: Ch. 9 CD Ch.s 14, 15, 16,
CS2003 Usability Engineering Human-Centred Design Dr Steve Love.
Task Analysis Methods IST 331. March 16 th
Requirements Elicitation. Structured Interview: Purpose is to ask and answer questions concerning the problem being modeled Observation: Observe activities.
Writing Software Documentation A Task-Oriented Approach Thomas T. Barker Chapter 5: Analyzing Your Users Summary Cornelius Farrell Emily Werschay February.
Ch. 9 User-centered approaches to interaction design Kevin Clark Matt Bergstein Carol Lawson Angelo Mitsopoulos Phil Townsend.
Identifying needs and establishing requirements Data gathering for requirements.
Today Next time  Interaction Reading: ID – Ch 2 Interaction  Introduction to HCI & Interaction Design Reading: ID – Ch. 1 CS 321 Human-Computer Interaction.
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
Barbara white : interactive mobile system design Who are our Users?
©2011 1www.id-book.com The process of interaction design Chapter 9.
1A FAST EXCELLENCE THROUGH FACILITATION Gary Rush The FAST Process MGR Consulting
Task Analysis Lecture # 8 Gabriel Spitz 1. Key Points  Task Analysis is a critical element of UI Design  It describes what is a user doing or will.
Understanding User's Work Ethnography The systematic study and documentation of human activity without imposing a prior interpretation on it via immersion.
Task Analysis Lecture # 8 Gabriel Spitz 1. Key Points  Task Analysis is a critical element of UI Design  It specifies what functions the user will need.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Putting it in Practice: CD Ch. 20 Monday Fun with Icons CS 321 Human-Computer.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today System Design: Reading: CD Ch.s 14, 15, &16 Monday Midterm CS 321 Human-Computer.
Requirements Elicitation Hans Van Vliet, Software Engineering: Principles and Practices, 3rd edition, Wiley (Chapter 3) 1.
Describing What You See.  Differs from Interviews in that in qualitative research it: 1) Most often takes place in a natural setting. 2) The researcher.
Foster positive relationships with customers to enhance company image.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Thursday Consolidation Reading: CD Ch.s 8, 9, & 10 In-class modeling exercise.
1 Design and evaluation methods: Objectives n Design life cycle: HF input and neglect n Levels of system design: Going beyond the interface n Sources of.
User Studies Basic principles, methods, and examples
User-centered approaches to interaction design
Chapter 9: User-centered approaches to interaction design
Presentation transcript:

User-centered approaches to interaction design By Haiying Deng Yan Zhu

Contents of this talk Advantages of involving users in development Principles of a user-centered approach Ethnographic-based methods Participative design techniques

Why is it important to involve users? Better understanding of users’ needs and goals, thus more appropriate and more useable product. Expectation management  making sure that the users’ views and expectations of the new product are realistic.  exceed users’ expectations  Adequate and timely training Ownership: involvement makes users more respective to the product.

Degrees of involvement Users join the design team  Full-time basis or Part-time basis  For the duration of the project or for a limited time only Users are not team members but kept informed through newsletters or other channels of communication Compromise situation

Degrees of involvement (cont) Users join the design team Full-time basis  Advantage Consistent input Users are familiar with the system and it’s rationale.  Disadvantage Lose touch with other users if the project takes many years. Input is less valuable.

Degrees of involvement (cont) Users join the design team (cont) Part-time basis  User is co-opted for whole project Advantage:  input consistent  Remain in touch with other users Disadvantage: too stressful to the user  Need to learn new jargon and handle unfamiliar material  Fulfill original job concurrently  User is co-opted for limited period Advantage: less stressful Disadvantage: input is not consistent

Degrees of involvement (cont) How actively users should be involved? more successful projects have direct links to users and customers user studies produce benefits outweigh the costs of conducting them. high user involvement has negative effect

Principles of user-centered approach Early focus on users and tasks Empirical measurement Iterative design

Principles of user-centered approach (cont) Early focus on users and tasks User’s tasks and goals are the driving force behind the development Users’ behavior and context of use are studied and the system is designed to support them. Users’ characteristics are captured and designed for Users are consulted throughout development from earliest phases to the latest and their input is seriously taken into account All design decisions are taken within the context of the users, their work and environment

Understanding users ’ work: applying ethnography in design

What is ethnography? literally means “ writing the culture ” a broad-based approach in which the users are observed under their normal activities Documented and rationalized experience Make the implicit explicit

What can ethnography do? Studying the context of work and watching work being done can reveal information that might be missed by other methods that concentrated on asking about work away from its natural setting

Typical ethnography example Background Method Brief characterization of user community Community practices and procedures

Principles to do the ethnography? Being reasonable, courteous, unthreatening, and interested in what ’ s happening.

Design & Ethnography Design: concerned with abstraction and rationalization Ethnography: interested in details.

The problem? Representing the information gleaned from an ethnographic study so that it can be used in design is hard.

A framework The distributed co-ordination: the distributed nature of the tasks and the activities The plans and procedures: the organizational support for the work. The awareness of work: how people keep themselves aware of others ’ work.

Two supporting methods: Coherence: presents the data from an ethnography study based around a set of “ view points ” and “ concerns ”. Contextual design: provides a structured approach to gathering and representing info from fieldwork with the purpose of design.

Coherence 3 viewpoints and a set of focus questions associated with each of them 4 concerns and a set of focus questions associated with each of them

Viewpoints: dimensions Focus questions: Distributed coordination: how clear are the boundaries.. Plans and procedures : how do they function? How do they fail ….. Awareness of work : how does the spatial organization support the interaction? How do workers organize the space around

Concerns: ---- paperwork and computer work ---- skill and the use of local knowledge ---- spatial and temporal organization ---- organizational memory

Contextual design Contextual inquiry Work modeling Consolidation Work redesign User environment design Mockup and test with customers Putting it into practice

Contextual inquiry An ethnographic study approach used for design Follows an apprenticeship model 4 main principles: context partnership interpretation focus

Context inquiry & ethnography interview Duration Intensity Participation intention

Work modeling Work flow model: the people involved and the communication and coordination that takes place. Sequence model: the detailed work steps to achieve a goal. Artifact model: the physical things created to do the work. Cultural model: constraints on the system caused by organizational culture. Physical model: the physical structure of the work.

Interpretation session Interpreter roles: ---- interviewer ---- work modelers ---- recorder ---- participants ---- moderator

Consolidating the models Why : to get a more general model of the work, one that is valid across individuals How : use affinity diagram, which organize the individual notes captured in the interpretation sessions into a hierarchy showing common structures and themes

Affinity diagram

The aim of consolidation on different models: Work flow Models : identify the key role. Sequence Models : identify what really needs to happen to accomplish the work Artifacts Models : show the common approaches to organize and structure the work Physical Models : show the commonality of physical structures Cultural Models : show the set of common influencers within the organization.

Design room A physical environment with all the work models available. An important element of Contextual Design.

Participatory design Involve users in design actively PICTIVE(Muller 1991) and CARD (Tudor 1993)

PICTIVE ( Plastic Interface for collaborative Technology Initiatives ) To let users fully participate in the design To improve knowledge acquisition Concentrates on detailed aspects of the system

PICTIVE (cont.) Stakeholders introduce themselves Brief tutorials are represented Brainstorm designs Walkthrough of the design and the decisions

CARD ( Collaborative Analysis of requirements and Design) A form of storyboarding Concentrates on a macroscopic view of the task flow

Summary Involving users in the design process helps with expectation management and feelings of ownership, but how and when to involve users is a matter of dispute. Putting a user-centered approach into practice requires much information about the users to be gathered and interpreted. Ethnography is a good method for studying users in their natural surroundings Representing the information gleaned from an ethnographic study so that it can be used in design has been problematic.

Summary (cont.) The goals of ethnography are to study the details, while the goals of system design are to produce abstractions; hence they are not immediately compatible. Coherence is a method that provides focus questions to help guide the ethnographer towards issues that have proved to be important in systems development. Contextual design is a method that provides models and techniques for gathering contextual data and representing it in a form suitable for practical design. PICTIVE and CARD are both participatory design techniques that empower users to take an active part in design decisions.