Information & Interaction Design Fall 2005 Bill Hart-Davidson Session 6: analyzing work practices – rationale and challenges; the 5 Contextual Design work.

Slides:



Advertisements
Similar presentations
Structured Design The Structured Design Approach (also called Layered Approach) focuses on the conceptual and physical level. As discussed earlier: Conceptual.
Advertisements

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.
Experiential Learning Cycle
Interaktionsdesign Session 4 Analysemetoder. Work Models Describe work from the point of view of the one person interviewed The Flow model The Sequence.
INF Lecture 30th of December Ethnographic and interpretive studies Example papers: We will discuss them in terms of –Approach and methods.
ACTIVELY ENGAGING THE STAKEHOLDER IN DEFINING REQUIREMENTS FOR THE BUSINESS, THE STAKEHOLDER, SOLUTION OR TRANSITION Requirements Elicitation.
Systems Analysis and Design 9th Edition
Analytical methods for Information Systems Professionals
CAP 252 Lecture Topic: Requirement Analysis Class Exercise: Use Cases.
Information & Interaction Design Fall 2005 Bill Hart-Davidson Session 7: teams present research plan + a sequence diagram from phase 2 homework; Affinity.
Studio Design in HCI Spring 2004 Bill Hart-Davidson Session 8: object-oriented modeling, basic concepts; artifact and physical work models; guidelines.
Administrivia  Review Deliverable 2 –Overview (audience) –Excellent additions  User Goals  Usability Goals  User Group (who are you designing for?)
Information & Interaction Design Fall 2005 Bill Hart-Davidson Session 3: Team & Project intros; Activity Analysis; Phase 1 presentation and Memo guidelines;
Reproduced with permission from BESTEAMS 2004
Studio Design in HCI Fall 2005 Bill Hart-Davidson Session 10: class diagrams; prototype examples; review guidelines for phase 2 presentation & forecast.
Project Sharing  Team discussions –Share results of heuristic evaluations –Discuss your choice of methods and results  Class-level discussion –Each spokesperson.
The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #10 BOO! BOO!
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #3.
Understanding and Representing Users A.J. Brush cse490ra January 22, 2003.
Introduction to Communication Research
1 Contextual Interview Shahnewaz A. Jolly CPSC 681: Research Methods in Human Computer Interaction Instructor: Dr. Saul Greenberg Date: November 4, 2009.
Case Study Research By Kenneth Medley.
Professional Facilitation
Science Inquiry Minds-on Hands-on.
RESEARCH DESIGN.
Academy of management - August 15, 2011 Symposium: Learning to Coordinate: The Dynamic Interplay between Relationships and Structures Who’s actually relating?
Z556 Systems Analysis & Design Session 9 ILS Z556 1.
CSCI 4163/6904, summer Quiz  Multiple choice  Answer individually - pass in  Then class discussion.
© 2011 Brooks/Cole, A Division of Cengage Learning Chapter 16 Consultation and Collaboration You must be the change you wish to see in the world. Mahatma.
5/20/ Conducting and Analyzing a Contextual Interview ICS 205 Spring 2002 Tom Herring Ratiya Komalarachun.
Copyright©2007 Education Service Center Region XIII Mineral Wells ISD 5E CSCOPE Overview.
9.1 WELCOME TO COMMON CORE HIGH SCHOOL MATHEMATICS LEADERSHIP SCHOOL YEAR SESSION 1 17 SEPT 2014 TAKING CHANCES (IN CONTENT AND PEDAGOGY)
Process Walk & SIPOC Define Kaizen Facilitation. Objectives Understand the process as a “system” Describe the concept of an entity and how it relates.
1 Technical & Business Writing (ENG-315) Muhammad Bilal Bashir UIIT, Rawalpindi.
1 Introduction to Software Engineering Lecture 1.
CCT 333: Imagining the Audience in a Wired World Class 6: Qualitative Research Methods.
Gathering SoTL Evidence: Methods for Systematic Inquiry into Student Learning Renee A. Meyers Coordinator, UWS SoTL Leadership Site Faculty College, May.
CIS 112 Exam Review. Exam Content 100 questions valued at 1 point each 100 questions valued at 1 point each 100 points total 100 points total 10 each.
Writing Software Documentation A Task-Oriented Approach Thomas T. Barker Chapter 5: Analyzing Your Users Summary Cornelius Farrell Emily Werschay February.
SBD: Analyzing Requirements Chris North CS 3724: HCI.
Design Process … and some design inspiration. Course ReCap To make you notice interfaces, good and bad – You’ll never look at doors the same way again.
1 L545 Systems Analysis & Design Week 3: September 16, 2008.
S556 SYSTEMS ANALYSIS & DESIGN Week 6. Using Language to Focus Thought (cf., Wood, 1997) SLIS S556 2  The language gives you a way to see:  a framework.
Developing Effective Study Groups Working Collaboratively.
Today Next time  Interaction Reading: ID – Ch 2 Interaction  Introduction to HCI & Interaction Design Reading: ID – Ch. 1 CS 321 Human-Computer Interaction.
CS160 Discussion Section 6 Task Analysis Postmortem David Sun March 06, 2007.
September 2010 Arlene W. Williams Marshall School of Business PLEASE SIT IN TEAMS.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Putting it in Practice: CD Ch. 20 Monday Fun with Icons CS 321 Human-Computer.
Today Discussion Follow-Up Interview Techniques Next time Interview Techniques: Examples Work Modeling CD Ch.s 5, 6, & 7 CS 321 Human-Computer Interaction.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Tuesday Contextual Inquiry & Intro to Ethnography Introduction to HCI & Contextual.
TECHNICAL WRITING 2013 UNIT 3: DESIGNING FOR CHANGE PART 2.
Week 2: Interviews. Definition and Types  What is an interview? Conversation with a purpose  Types of interviews 1. Unstructured 2. Structured 3. Focus.
CDIO: Overview, Standards, and Processes (Part 2) Doris R. Brodeur, November 2005.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Thursday Consolidation Reading: CD Ch.s 8, 9, & 10 In-class modeling exercise.
User-centered approaches to interaction design By Haiying Deng Yan Zhu.
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.
Stages of Research and Development
Conceptual Change Theory
From: A. Cooper et al.: About Face Andreas Rudin
CHAPTER OVERVIEW The Case Study Ethnographic Research
Chapter 4: Business Process and Functional Modeling, continued
Week 10: Object Modeling (1)Use Case Model
SBD: Analyzing Requirements
Design Research Jon Kolko Director & Founder, Austin Center for Design.
A thinking skills approach to learning maths (CAME)
CHAPTER OVERVIEW The Case Study Ethnographic Research
Presentation transcript:

Information & Interaction Design Fall 2005 Bill Hart-Davidson Session 6: analyzing work practices – rationale and challenges; the 5 Contextual Design work models; Exercise 2: CD interviews, flow & sequence models

Today in Class… Introduction to Contextual Design Overview of your work in phase 2 Challenges in analyzing & designing work (Bill H-D talks about the most obvious ones for each project team) CD’s 5 work models explained Exercise 2: Conducting CD interviews to build flow and sequence models

Contextual Design, what is it? An approach to system design that 1.uses qualitative research techniques to directly observe actual, ongoing work 2.ties design decisions to the results of research, using work models in 5 visual formats in order to facilitate shared understanding

What does CD do? 1.It reveals “hidden” patterns of work 2.It makes work structures visible and intelligible so that they can become the basis for system design 3.It meshes nicely with Activity Theory and Embodied Interaction, allowing designers to focus on implementation without ignoring user centered goals while still

CD: Philosophy Design processes work when they build on natural behavior go to where the work is, and watch it happen learn by paying attention to what matters to the people who do the work see the details!

CD: Methodology Seeing the work reveals structure people learn to do work and become expert by observing others…you can do the same commit to watching multiple instances and multiple users current activity recalls past instances…ask about them!

CD 4 Principles: Context Context Lessons– gather evidence of ongoing vs. summary experience; concrete vs. abstract data avoid surveys, general interview questions such as “what do you think of the current system”…this is summary data gather actual artifacts, observe and talk about real events, explore ongoing work

CD 4 Principles: Partnership Partnership Lessons – build a reciprocal relationship with participants to ensure good data avoid relationships that position you as the expert, the “guest” or the typical interviewer help users to explain work by reflecting back what you think you see, verifying, asking them to show you, etc.

CD 4 Principles: Interpretation Interpretation Lessons– build your interpretation over time, with the help of the whole team and users gather facts and make interpretations of those that you can share with your team and with users for verification consider design decisions the end of a chain of reasoning that begins with interpretation of your data

CD 4 Principles: Focus Focus Lessons– commit to challenging your assumptions about the activity, not confirming them your “focus” is a powerful tool that can help you to see detail, but also to miss important aspects of the big picture take time, as a team, to talk about the focus for each data gathering session so you can understand what you may see and what you may miss

Doing Contextual Design In phase 2, You’ll observe and interview people in the various user roles you identified in Phase 1, gathering data to build interpretations of the work that your system must support. You’ll share your interpretations using the 5 work models, and then build prototypes of the user environment for the system that allow you to test the design ideas that come from your interpretations.

3 Priorities of the Conceptual Design Phase Gather & interpret concrete data about ongoing experiences for each user role Understand the work Use visual models to achieve shared understanding and see possibilities Represent the context Design the functionality of the system with few or no specific implementation choices Model the system

How it breaks down in class… Session 6 – intro to CD, work models; teams plan CD activities and begin building flow and sequence models Session 7 – the big picture: cultural models; teams share their CD research plans Session 8 – consolidating the data w/ affinity diagrams; teams present examples of work models (flow, sequence, cultural) in class

How it breaks down in class, cont. Session 9 – modeling the user environment; OO modeling concepts (objects, views, relationships); Exercise 3: artifact and physical models Session 12 – prototyping: testing design concepts, not system features; Session 13 – conceptual design presentation guidelines

Phase 2 homework: CD Interviews Your homework for phase 2 is to conduct 1-3 contextual design interviews as described on pp You’ll use the data to create and share two sequence models (see ch. 6). Post these for sharing in class session 7.

Challenges of Work Analysis & Design 1.“Normal” 2. Intermittent 3.Uninterruptable 4.Extremely long 5.Extremely focused 6.Internal Seeing work that is:

Where do your challenges lie? 1.“Normal” 2. Intermittent 3.Uninterruptable 4.Extremely long 5.Extremely focused 6.Internal Seeing work that is: For each user role, let’s consider which of these complicating factors come into play…and how they can be dealt with

Team Student Body Politic: participants 1.“Normal” 2. Intermittent 3.Uninterruptable 4.Extremely long 5.Extremely focused 6.Internal Seeing work that is: You may need to ask participants to keep a record of activity over some period of time that can be the basis for a retrospective interview

Team mmFood: menu planners 1.“Normal” 2. Intermittent 3.Uninterruptable 4.Extremely long 5.Extremely focused 6.Internal Seeing work that is: “Normal” actions planning meals may not be enough…you may need to ask about “critical incidents;” probe to discover complicating issues

Team +9SoV: Schedulers 1.“Normal” 2. Intermittent 3.Uninterruptable 4.Extremely long 5.Extremely focused 6.Internal Seeing work that is: The scheduling portion of meeting planning is a heavily mediated activty, involving the coordination of information from potentially many sources

Team Fitting Room: Frequent Clothing Shoppers 1.“Normal” 2. Intermittent 3.Uninterruptable 4.Extremely long 5.Extremely focused 6.Internal Seeing work that is: Frequent shoppers may, in some sense, always be shopping: reconciling what they have with what’s available to buy, etc.

5 work models Flow – what patterns of communication/ coordination exist? Sequence – what are the detailed steps necessary to perform actions? Cultural – what are the influences on the work that come from organizational & social sources? Artifact – what do the resources used to perform work look like? How are they employed in real work situations? Physical – what does the workspace look like? How does it influence the work? What patterns of activity shape it?

Building a flow model Gather data about: Roles Responsibilities Groups Flow patterns Artifacts Topics Actions Places Breakdowns See coordination by noting when people interact, what they use, why and where they do it.

Simple flow model: scheduling a consultation Instructor StudentsTA schedule Request to coordinate schedule Please arrange a time… website calendar

Building a sequence model Gather data about: Goals Triggers Actions - steps Artifacts Outcomes Errors Start with a user role, and trace the work practice from that user’s point of view.

Simple sequence model: Instructor Intent: Delegate Task Trigger: upcoming presentations Request TA coordinate schedule Send to students asking them to coordinate with TA Receive s with schedule requests Post schedule on website Receive revised schedule Re-post schedule on website Forward to TA

For Next Week Be ready to share… –A sequence model based on your already collected data As before, It is best if you can post some representation of it for us to look at as well - the main purpose: to discover what you still need to learn more about Set up and conduct your initial CD interviews/observations; start working on flow and sequence models We’ll talk about the big picture: cultural models

What’s a Research Plan? The research focus - what does your team need to know? The interviews/observations you will do broken down by roles The approach you will take in each of these How you will deal with the challenges your project poses

Something to think about… “Culture is as invisible as water is to fish” “The cultural model speaks the words people think [and believe] but don’t say”