Modeling Work and the Interpretation Session ITM 734 Fall 2006 Corritore.

Slides:



Advertisements
Similar presentations
Chapter 9 User-centered approaches to interaction design By: Sarah Obenhaus Ray Evans Nate Lynch.
Advertisements

MIS (Management Information System)
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.
MIS 2000 Class 2: Basic Concepts Updated January 2014.
Personal Reading Procedures Reading for High School and Beyond By; Holden Stengel.
Everything you need to know in order to set up your Reader’s Notebook
Interaktionsdesign Session 4 Analysemetoder. Work Models Describe work from the point of view of the one person interviewed The Flow model The Sequence.
Building Models Part 1: Models good for defining system and user requirements –Affinity diagrams –Flow model –Cultural model –Sequence model –Physical.
INF Lecture 30th of December Ethnographic and interpretive studies Example papers: We will discuss them in terms of –Approach and methods.
8 September Announcements  GIT Class: Friday 3-5 SN 115 (Peter Parente)  Information for Project Links PageProject Links Page  Hot Topics Teams.
Information & Interaction Design Fall 2005 Bill Hart-Davidson Session 7: teams present research plan + a sequence diagram from phase 2 homework; Affinity.
Information & Interaction Design Fall 2005 Bill Hart-Davidson Session 6: analyzing work practices – rationale and challenges; the 5 Contextual Design work.
Focus Groups for the Health Workforce Retention Study.
Gathering Information and Use Case Scenarios
Contextual Inquiry Katayoon Etemad November 2007.
Systems Analysis I Data Flow Diagrams
1 Contextual Interview Shahnewaz A. Jolly CPSC 681: Research Methods in Human Computer Interaction Instructor: Dr. Saul Greenberg Date: November 4, 2009.
Microsoft ® Office Word 2007 Training Mail Merge II: Use the Ribbon and perform a complex mail merge [Your company name] presents:
Test Taking Tips How to help yourself with multiple choice and short answer questions for reading selections A. Caldwell.
The Project AH Computing. Functional Requirements  What the product must do!  Examples attractive welcome screen all options available as clickable.
L545 Systems Analysis & Design Week 7: October 14, 2008.
S556 SYSTEMS ANALYSIS & DESIGN Week 7. Artifacts SLIS S556 2  Artifacts are tangible things people create or use to help them get their work done  An.
Z556 Systems Analysis & Design Session 7 ILS Z556 1.
Effective Note Taking Instructor(s) Date (s).
Communication Skills Anyone can hear. It is virtually automatic. Listening is another matter. It takes skill, patience, practice and conscious effort.
Maestro Hands-on Approach to Whole Publications By Beth L. Fitts Mississippi Scholastic Press Association
Z556 Systems Analysis & Design Session 9 ILS Z556 1.
ACTIVITY. THE BRIEF You need to provide solid proof to your stakeholders that your mobile website meets the needs of your audience. You have two websites.
Focus groups ScWk 242 – Session 4 Slides.
Visioning ITM 734 Fall 2006 Corritore. 2 Visioning Goal – to create a vision of how your system will support your users’ work. * says what the new work.
Z556 Systems Analysis & Design Session 5 ILS Z556 1.
Protocols for Mathematics Performance Tasks PD Protocol: Preparing for the Performance Task Classroom Protocol: Scaffolding Performance Tasks PD Protocol:
INFO3315 Week 4 Personas, Tasks Guidelines, Heuristic Evaluation.
10/12/ Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 1. Interviews & questionnaires.
Calhoun ISD Facilitated School Improvement Planning October 1, 2012 Beth Brophy and Mitch Fowler DO Implement Plan Monitor Plan Evaluate Plan.
Requirements Artifacts Precursor to A & D. Objectives: Requirements Overview  Understand the basic Requirements concepts and how they affect Analysis.
Affinity Diagrams ITM 734 Fall 2006 Corritore. 2 Affinity diagrams Brings issues and insights about customers/users together  Fastest and best way Affinity.
Process Walk & SIPOC Define Kaizen Facilitation. Objectives Understand the process as a “system” Describe the concept of an entity and how it relates.
Contextual Design – The Basics and the Contextual Interview based on: Rapid Contextual Design by Holtzblatt, Wendell, & Wood Contextual Design by Beyer.
Scientific Communication
CCT 333: Imagining the Audience in a Wired World Class 6: Qualitative Research Methods.
1 What to do before class starts??? Download the sample database from the k: drive to the u: drive or to your flash drive. The database is named “FormBelmont.accdb”
Good students DO write in textbooks Three reasons you should mark, highlight & write in your textbooks 1.To find and select the author’s key ideas and.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Tuesday Running A Paper Prototyping Session CS 321 Human-Computer Interaction.
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.
©2001 Southern Illinois University, Edwardsville All rights reserved. CS 321 Human-Computer Interaction Today Consolidation Reading: CD Ch.s 8, 9, & 10.
Science Fair Research Paper General Paper Guidelines MUST be Typed 12 pt. Font Black Ink 1.5 or double spaced At least 4 pages (not including bibliography.
Customer Focus Module Preview This PowerPoint provides a sample of the Strategic Planning Module PowerPoint. The actual Strategic Planning PowerPoint is.
The Level 2 Exam What do each of the underlined words mean? Apply knowledge of and make judgements about drama processes and performance in a new.
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.
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. CS 321 Human-Computer Interaction Today Design from Data Reading: CD Ch. 11, 12,
Annotations by Katherine Schuster.
CCT 333: Imagining the Audience in a Wired World Class 6: Intro to Research Methods – Qualitative Methods.
Week 2: Interviews. Definition and Types  What is an interview? Conversation with a purpose  Types of interviews 1. Unstructured 2. Structured 3. Focus.
Reform Groups and Analyze Preliminary Designs. Schedule Week 6 Lab Small Group Presentations Form into three large teams Agree on problem statement and.
Cooper Goal-Directed Design: Practice Session Dr. Cindy Corritore Creighton University ITM 734 Fall 2005.
Taking Lecture Notes How to Record and Remember Classroom Discussions or Lectures.
User-centered approaches to interaction design By Haiying Deng Yan Zhu.
Literature Circles Ideas for sharing tools. Sharing Tools A tool should usually take 20 minutes or less to create It needs to actively involve all group.
Food Product Development
Z556 Systems Analysis & Design
Z556 Systems Analysis & Design
COMPREHENSION Tool Kit K-3 1 1
Introducing the Ideas One of Six Traits:
Conducting Design Research
SUCCESSFUL TEXTBOOK READING AND NOTE TAKING
CS 321 Human-Computer Interaction
Presentation transcript:

Modeling Work and the Interpretation Session ITM 734 Fall 2006 Corritore

2 Work Models: Sequence model basic info about how the work is really done, structured, and the intent New sequence for each new task or instance of a task  Trigger – what causes the sequence of actions, prompts Need way to tell user that there is something to be done  Steps – action or thought preceding an action Not taking running notes – capturing key steps Include thought steps  Order – may include loops and branches  Breakdowns/problems – lightening bolt Hesitations or errors – ask them to explain  Intents – why the work matters to the user – the reason they did it Primary (applies to entire sequence) and secondary (drive particular way work is carried out) Look over steps and write this Examples pg , 131  User code and number (in sequence)

3 Our project Important for us – why? Kinds of sequences …

4 Work Models: Artifact model The things people create, use or modify in the course of doing work - tangible  How they are arranged into parts and relationship between parts – show conceptual distinctions in the work grouping corresponds to conceptual distinctions Information content and how it is used Informal annotations Presentation – how artifact presented - layout, fonts, formatting, etc.  Make a drawing or picture on flipchart and add handwritten notes  Example pg. 135 (user code and sequence no. )

5 Our project Artifacts important  Provides clues how to structure our system  Natural pattern of interaction with artifacts should be maintained

6 Work models: Physical model Where work happens  Constrains what people can do  People structure their workplace to be convenient, mirrors how they conceptualize their work  Things like Organization of space, division of space, grouping of people, organization of workplaces, movement through the space  Example pg 138

7 Our project Physical model important how?

8 Other work models Flow – shows people’s responsibilities and communication/coordination flow between then for given job Cultural – reveals influences on a person and feelings about their work.

9 Equipment for work models Sharpies  Blue – regular text  Red – breakdowns (lightening bolts)  Green – holes, questions, hi-level summary data, uncertainties Flip chart and paper  Label with user ID

10 Interpretation session Way to build a shared understanding of customers work  Can involve stakeholders and lots of other folks  Multiple perspectives

11 Interpretation session Roles 1. Interviewer – one who interviewed the customer - TRUTH Team can back them up if skipped over something Not passive – can engage in discussion 2. Work modelers – draw work models on flip chart as they hear them Do sequence Tape up artifacts and analyze/annotate as they come up Just draw – if someone sees something they think is wrong, stop and point it out

12 Interpretation session Roles 3. Recorder Keeps notes on overhead projector Word doc  Every key observation, insights and interpretations (I), question (Q), design idea (D), good user quotes (QU)  These used to build an affinity diagram later  Capture key ideas emerging from discussion  Each should stand by itself  Each should only express one idea/activity  Facts OK – more important – why the fact matters  Like a record of the session Will also capture some elements of Sequence Model –  Breakdowns, intents, observed work strategies, triggers that are particularly important for design, etc –  NOT individual steps Will also capture some elements of Artifact Model  Breakdowns, intents, usages, concepts implied, types of info collected and source, aspects that don’t work Will also capture elements of Physical Model

13 Interpretation session Examples of interpretation session notes (pg 117): U4 1 Copies of sample cards kept in shoeboxes; has to keep them two years (regulation) U4 2 Home office lost sample cards she had sent in; she had to make photocopies of her copies and send them again U4 3 Keeps last 6 months of sample cards in her home office; then puts them in shoebox and moves them to garage U4 4 Q: Is there any defined procedure for storing and disposing of sample cards? U4 5 D: give sales reps a budget they can use to buy the things they need. U4 6 I: home office thinks they know the equipment the sales reps need, but don’t supply storage for information Where U4 is type and no. of user, other number is sequence

14 Interpretation session Roles 4. Participants – rest of team  Listen, ask questions to understand, develop insights into the work, propose interpretations for team, make observations, suggest design ideas (don’t discuss these – just capture in their context)  Capture that!  Make sure recorder additions are accurate 5. Moderator  Stage manager for meeting “what happened on this interview and what do we need to capture from it?”  Keep the pace brisk, keep everyone involved  Give post-it notes to talkers to record ideas – then at end see if they have been brought up

15 Interpretation session Roles 6. Rat hole watcher – rat hole is anything that pulls the conversation off-track  Examples:  Is this technically feasible?  Evaluation of any idea.  Sharing your own personal experience with a product  Introducing data from another user (my guy did that too!)  Everyone really does this

16 Interpretation session process Label everything with user ID and sequence number Demographic profile – put in Word doc  Job function, job title, department, age, time at job, no. of students, no. of courses this semester, on avg. a semester, online vs. onsite, browser type, etc?  Don’t put in affinity note – put in section before notes. Draw a physical model of workplace and annotate (flipchart) Walk through interview step by step  Bit chaotic – trying to tell story, people asking questions, people drawing models, recorder typing, moderator advising  Everyone thinking outloud – NO EVALUATION at this point  Recorder writing affinity notes one per line When done, look back and list top insights from this interview (pg. 119) – on flipchart  reflection

17 Sharing sessions When teams do interpretation in small groups – have to inform the whole at some point  Speaker – presents the models for a given user Sequence model – tell story of the sequence model - summarize key strategies or breakdowns that model reveals  Helper updates model as speaks  Teams listen, question, add interpretations, etc.  Recorder – adds any new points to online notes At bottom (find duplication later)  Moderator – keep meeting moving

18 Example Interpretation Session Read customer data U1 – 9 Roles  Recorder – Word on screen  Moderator  Interviewer  Rat hole watcher  Work Modeler – flipchart (sequence, artifact)  Rest of team -

19 Interpretation session process Label everything with user ID and sequence number Demographic profile – put in Word doc  Job function, job title, department, age, time at job, no. of students, no. of courses this semester, on avg. a semester, online vs. onsite, browser type, etc?  Don’t put in affinity note – put in section before notes. Draw a physical model of workplace and annotate (flipchart) Walk through interview step by step  Bit chaotic – trying to tell story, people asking questions, people drawing models, recorder typing, moderator advising  Everyone thinking outloud – NO EVALUATION at this point  Recorder writing affinity notes one per line When done, look back and list top insights from this interview (pg. 119) – on flipchart  reflection

20 Take a look ….. Incontextdesign.com – hop/index.htm - physical model - artifact model - sequence model (consolidated)

21 Next time Sharing sessions Consolidation and affinity diagrams  Ch 7 and 8 in Holtzblatt, et. al.

22