Jesper Kjeldskov Mikael B. Skov Jan Stage HCI-Lab Department of Computer Science Aalborg University Denmark Does Time Heal? A Longitudinal Study of Usability.

Slides:



Advertisements
Similar presentations
Goals of INFO3315 Learn about the range of techniques to: Understand users Establish requirements Brainstorm alternatives creatively Prototyping alternative.
Advertisements

IT Issues and Support Structures Simulation Education and Complex Technology Based Practice.
Health Sciences and Practice & Medicine Dentistry and Veterinary Medicine Higher Education Academy Subject Centres Wendy Hardyman, Mark Stacey, Alison.
Jesper Kjeldskov, Mikael B. Skov, Benedikte S. Als, and Rune T. Høegh Mikael B. Skov Department of Computer Science Aalborg University, Denmark Is it Worth.
PROGRAM AND PROJECT MANAGEMENT
Steve Howard 12, Jesper Kjeldskov 2, Mikael B Skov 2, Kasper Garnoes 2, Olga Gruberger 2 1 Interaction Design Group, 2 HCI Group Department of Information.
MoHealthWINs MoHealthWINs Open Learning Initiative Co-Development Project October 31, 2013.
The USE Project: Usability Evaluation and Software Design: Bridging the Gap University of Copenhagen Aalborg University Use Case Evaluation (UCE): A Method.
Evaluation of A PDA Based Clinical Handover System Dr Marilyn R McGee-Lennon University of Glasgow SIHI, Portsmouth, Sept 2007 HECTOR.
Part 4: Evaluation Days 25, 27, 29, 31 Chapter 20: Why evaluate? Chapter 21: Deciding on what to evaluate: the strategy Chapter 22: Planning who, what,
Instant Data Analysis (IDA): Evaluating Usability in a Day Jesper Kjeldskov Mikael B. Skov Jan Stage.
Computer Science Department Program Improvement Plan December 3, 2004.
Jesper Kjeldskov & Jan Stage Department of Computer Science Aalborg University Denmark New Techniques for Usability Evaluation of Mobile Systems.
Feedback from Usability Evaluation to User Interface Design: Are Usability Reports Any Good? Christian M. Nielsen 1 Michael Overgaard 2 Michael B. Pedersen.
HFSD User Involvement Whilst the need to involve users in the SAD process is accepted to a greater or less extent in all design methods - the decision.
Frequently asked questions about software engineering
Lecture 1.
VENDORS, CONSULTANTS AND USERS
IMPLEMENTING AN EMERGENCY DEPARTMENT SCRIBE PROGRAM AT ALASKA REGIONAL HOSPITAL A Feasibility Study.
1. Learning Outcomes At the end of this lecture, you should be able to: –Define the term “Usability Engineering” –Describe the various steps involved.
Chapter 1- Introduction
1. Human – the end-user of a program – the others in the organization Computer – the machine the program runs on – often split between clients & servers.
Year Seven Netbook Project. Aims of the Project To evaluate the impact on learning and teaching of using portable technologies both within and outside.
Use of OCAN in Crisis Intervention Webinar October, 2014.
New Advanced Higher Subject Implementation Events Design and Manufacture: Advanced Higher Course Assessment.
1 Usability evaluation and testing User interfaces Jaana Holvikivi Metropolia.
Margaret J. Cox King’s College London
Usability Testing Teppo Räisänen
1 SWE 513: Software Engineering Usability II. 2 Usability and Cost Good usability may be expensive in hardware or special software development User interface.
1 Usability of Digital Libraries Sanda Erdelez & Borchuluun Yadamsuren Information Experience Laboratory University of Missouri – Columbia USA Libraries.
Presentation: Techniques for user involvement ITAPC1.
Gruppearbejde Mikael B. Skov Jan Stage. 2 Gruppearbejde Hvad er jeres produkter, og hvad gør I vedr. evaluering? Hvordan kan specifikt evaluere disse?
Human Computer Interaction
Multimedia Specification Design and Production 2012 / Semester 1 / week 5 Lecturer: Dr. Nikos Gazepidis
What is Usability? Usability Is a measure of how easy it is to use something: –How easy will the use of the software be for a typical user to understand,
Problem-Based Learning. Process of PBL Students confront a problem. In groups, students organize prior knowledge and attempt to identify the nature of.
Children: Can they inspect it? Yes they can! Gavin Sim.
Pune circle Dr.Kanchan Jagtap, DDHS,PUNE 23 / 24 May 14 Skill development Plan.
Extended Cognitive Walkthrough Judy Kay CHAI: Computer human adapted interaction research group School of Information Technologies.
Big6 Overview Big6™ Trainers Program McDowell County Schools.
Usability Testing Chapter 6. Reliability Can you repeat the test?
Chapter 13. Reviewing, Evaluating, and Testing © 2010 by Bedford/St. Martin's1 Usability relates to five factors of use: ease of learning efficiency of.
Midterm Stats Min: 16/38 (42%) Max: 36.5/38 (96%) Average: 29.5/36 (78%)
Scientific Investigations and Problem Solving District Learning Day TBD August 5, 2015.
1 Technical & Business Writing (ENG-315) Muhammad Bilal Bashir UIIT, Rawalpindi.
Inquiry Based Learning District Learning Day 1:45-2:45 August 5, 2015.
Program Evaluation.
Train The Trainer. Ice breaker What is your background? What are your expectations from the course? What has been your greatest achievement up till now?
Writing Software Documentation A Task-Oriented Approach Thomas T. Barker Chapter 5: Analyzing Your Users Summary Cornelius Farrell Emily Werschay February.
(1) Cam Moore Collaborative Software Development Laboratory Communication & Information Sciences University of Hawaii, Manoa
CS818 SOFTWARE SYSTEM ENGINEERING Team 3 Steve Grimes, Craig Mitchell, Mark Oden, Mark Ramos, Brian Rater, Kat Reagan.
Unit (7) Why businesses make decisions? The decision that they make might include. - what to produces, where to locate the premises, what method of production.
Managing Challenging Projects Presented to the class of: Dr. Jane Mackay M.J. Neely School of Business.
A Simulation Model for Bioterrorism Preparedness in An Emergency Room Lisa Patvivatsiri Department of Industrial Engineering Texas Tech University Presented.
1 Usability evaluation and testing User interfaces Jaana Holvikivi Metropolia.
Oct 211 The next two weeks Oct 21 & 23: Lectures on user interface evaluation Oct 28: Lecture by Dr. Maurice Masliah No office hours (out of town) Oct.
The Value of USAP in Software Architecture Design Presentation by: David Grizzanti.
Usability Engineering Dr. Dania Bilal IS 587 Fall 2007.
The Process of Developing a Mobile Device for Communication in a Safety-Critical Domain Jesper Kjeldskov and Jan Stage Mobile HCI Research Group Department.
School of Engineering and Information and Communication Technology KIT305/607 Mobile Application Development Week 7: Usability (think-alouds) Dr. Rainer.
SIE 515 Design Evaluation Lecture 7.
Human Computer Interaction Lecture 15 Usability Evaluation
Healing our Health System Models of Care
Frequently asked questions about software engineering
Chapter 16 Nursing Informatics: Improving Workflow and Meaningful Use
Unit 6: Application Development
CLINICAL INFORMATION SYSTEM
HCI Evaluation Techniques
Does Time Heal? A Longitudinal Study of Usability
Kasper Hornbæk Department of Computer Science University of Copenhagen
Presentation transcript:

Jesper Kjeldskov Mikael B. Skov Jan Stage HCI-Lab Department of Computer Science Aalborg University Denmark Does Time Heal? A Longitudinal Study of Usability

2 Jesper Kjeldskov, Mikael B. Skov, Jan Stage, Does Time Heal? OzCHI 2005 Background Making local software industry do usability Providing lightweight methods and techniques The USE project: bridging usability and design Several years of comparative usability studies Where to conduct evaluations: lab/field discussion How to analyze data: instant data analysis (IDA) How to study use: snapshots versus longitudinal studies “Usability does not matter - the user just has to learn the system” Do usability problems disappear? Does time heal poor design?

3 Jesper Kjeldskov, Mikael B. Skov, Jan Stage, Does Time Heal? OzCHI 2005 Project context By 2006 all Danish hospitals must have implemented Electronic Patient Records (EPR) (this political demand will not be met) EPRs contain information about patient’s medical history used by nurses and doctors Designing useable EPR systems is a huge challenge… Dynamic and stressful use context User’s focus is not on the system Errors can be fatal We participated in a large scale pilot project studying the use of EPR at a large regional hospital prior to national implementation

4 Jesper Kjeldskov, Mikael B. Skov, Jan Stage, Does Time Heal? OzCHI 2005 The EPR system evaluated Commercially available system: IBM IPJ 2.3 Running on desktop and laptop PC’s A complex system for expert users primarily engaged elsewhere (deciding if this system is useful is not trivial)

6 Jesper Kjeldskov, Mikael B. Skov, Jan Stage, Does Time Heal? OzCHI 2005 Research questions To what extent is the effectiveness and efficiency of using the system different over time? Which usability problems are experienced by the users over time? Is there a difference in the severity over time?

7 Jesper Kjeldskov, Mikael B. Skov, Jan Stage, Does Time Heal? OzCHI 2005 The longitudinal study May 2002 August st evaluation 7 experienced nurses Novice computer users Had completed EPR course Facing system implementation the following week 2nd evaluation 7 experienced nurses Higher general computer users Had used EPR system 15 months times/2 hours per day

8 Jesper Kjeldskov, Mikael B. Skov, Jan Stage, Does Time Heal? OzCHI 2005 The two evaluations Experimental settings and approach State-of-the-art usability lab 3 tasks developed with hospital staff Thinking aloud Post-evaluation interviews and TLX tests Test subjects 7 professional nurses years of age 2-31 years of work experience hours of EPR training Evaluations identical in 2002 and 2003

9 Jesper Kjeldskov, Mikael B. Skov, Jan Stage, Does Time Heal? OzCHI 2005 Experimental setup

10 Jesper Kjeldskov, Mikael B. Skov, Jan Stage, Does Time Heal? OzCHI 2005 Themes of usability problems Complexity of information The information in the EPR system was found to be too complex and fragmented. Nurses found it difficult to get an overview of each patient and to find the necessary information Relation to work activities Nurses found that the structure of information in the system poorly reflected their real work tasks, making it difficult to find and store the right information Mobility of work Nurses stressed concerns about being mobile while having to use the system. Carrying a laptop computer was found unfeasible

11 Jesper Kjeldskov, Mikael B. Skov, Jan Stage, Does Time Heal? OzCHI 2005 Problem severity Delay Irritation/ irrationality Expectation vs. actual Critical Total (user stops) StrongCritical diff. Serious Several minutes Medium Significant diff. Cosmetic< 1 minuteLowSmall diff. Based on Molich and Nielsen

12 Jesper Kjeldskov, Mikael B. Skov, Jan Stage, Does Time Heal? OzCHI 2005 Total numbers of usability problems (1) 1st evaluation (2002) (N=7) Critical25 Serious45 Cosmetic13 Total83 The nurses experienced 25 critical usability problems Information about the patients is fragmented It is difficult to get an overview of the different pending tasks It is difficult to understand relation between different parts of the systems

13 Jesper Kjeldskov, Mikael B. Skov, Jan Stage, Does Time Heal? OzCHI 2005 Total numbers of usability problems (2) 1st evaluation (2002) (N=7) 2nd evaluation (2003) (N=7) Total (N=14) Critical Serious Cosmetic Total The nurses experienced less usability problems after one year of use 19 critical usability problems Some problems had disappeared and new ones had emerged Some had changed severity (critical  serious) (serious  cosmetic)

14 Jesper Kjeldskov, Mikael B. Skov, Jan Stage, Does Time Heal? OzCHI 2005 Distribution of problems across time Numbers in parentheses show totals of non-unique problems 1st evaluation nd evaluation 2003

15 Jesper Kjeldskov, Mikael B. Skov, Jan Stage, Does Time Heal? OzCHI 2005 Distribution of problems across severity Each column represents a usability problem. A black square indicates that the respective user group identified a usability problem. A white square indicates that a problem was not identified by that user group

16 Jesper Kjeldskov, Mikael B. Skov, Jan Stage, Does Time Heal? OzCHI 2005 Distribution of problems across severity (1) Critical Problems of the critical problems experienced in the 1st evaluation was still experienced after one year of use 4 of the critical problems found in 2002 were not experienced after one year of use 2 of these 4 problems were still experienced after one year but had changed severity to “serious”

17 Jesper Kjeldskov, Mikael B. Skov, Jan Stage, Does Time Heal? OzCHI 2005 Distribution of problems across severity (2) Serious Problems of the serious problems experienced in the 1st evaluation was still experienced after one year of use 9 of the serious problems experienced in the 1st evaluation had disappeared after one year of use 2 of the 3 “new” serious problems were problems experienced as critical one year before (changed severity)

18 Jesper Kjeldskov, Mikael B. Skov, Jan Stage, Does Time Heal? OzCHI 2005 Distribution of problems across severity (3) Cosmetic Problems of the cosmetic problems experienced in the 1st evaluation was still experienced after one year of use 3 of the cosmetic problems experienced in the 1st evaluation had disappeared after one year of use After one year of use, the nurses experienced 2 new cosmetic problems

19 Jesper Kjeldskov, Mikael B. Skov, Jan Stage, Does Time Heal? OzCHI 2005 Where did the problems disappear to? 2 critical problems disappeared after one year of use because.. The users developed workarounds outside the system to avoid them (workarounds now need to be communicated to new staff) 9 serious problems disappeared after one year of use because... They were closely related to the 2 disappearing critical problems The users got more familiar with the system Most of the cosmetic problems disappeared because... The users got more familiar with the system The users had acquired higher general computer skills

20 Jesper Kjeldskov, Mikael B. Skov, Jan Stage, Does Time Heal? OzCHI 2005 Which problems did not disappear? After one year of use, the basic design of the EPR system was still experienced as problematic in the nurses’ everyday work at the hospital Information structure Information still experienced as complex and too fragmented Still difficult to get an overview of individual patients Still difficult to get an overview of pending tasks (despite of workarounds) Mobility and relation to work activities Still poor relation between information structure and work activities Mobility did become a big issue; carrying a laptop computer was found unfeasible Basic interaction design (not learned) Lack of consistency (e.g. single and double click) still a problem Lack of affordances (e.g. Seeing which elements are active) still a problem

21 Jesper Kjeldskov, Mikael B. Skov, Jan Stage, Does Time Heal? OzCHI 2005 What did we learn? Time does not heal usability problems Critical usability problems do not “just disappear” with user experience Workarounds should not be seen as an acceptable solution! Problem severity may change Some cosmetic problems may disappear Poor design remains poor! (and we should be able to do better) Longitudinal evaluations rather than “the usual” snapshots of use? Stretching the design process into real use situations Allowing for user appropriation of design Providing a noise filter on cosmetic usability problems

22 Jesper Kjeldskov, Mikael B. Skov, Jan Stage, Does Time Heal? OzCHI 2005 Questions...