The Field Guide to Human Error Investigations Chapters 7 – 13 “The New View of Human Error” AST 425.

Slides:



Advertisements
Similar presentations
Accident and Incident Investigation
Advertisements

Time Management By Zahira Gonzalez.
1 Myers-Briggs Type Indicator Carl G. Jung’s theory of psychological types Differences between normal healthy people Source of misunderstanding and miscommunication.
The CRM Textbook: customer relationship training Terry James © 2006 Chapter 11: Management.
Entrepreneurial Mind-Set
Human Performance and Patient Safety
Human Performance Todd Conklin PhD Royce Railey Sr. Safety Advisor
Brownfields 2013 Ron Snyder, HMTRI/CCCHST Adapted from: Todd Conklin PhD Los Alamos National Laboratory.
1 Procedural Analysis or structured approach. 2 Sometimes known as Analytic Induction Used more commonly in evaluation and policy studies. Uses a set.
Perception and Individual Decision Making
Writing the 'Personal' Statement Robert Harper-Mangels, Ph.D. Assistant Dean, Yale University Graduate School.
What Is Perception, and Why Is It Important?
ORP Incorporating Human Performance Improvement Tools into DOE Processes Shirley J. Olinger, Deputy Manager, ORP Brian Harkins, ORP Facility Representative.
Communication Effective Listening.
Introduction to Root Cause Analysis Understanding the Causes of Events
Assignment 2 Case Study. Criteria Weightage - 60 % Due Date – 11 th October 2012 Length of Analysis – 2500 words Leverage % including appendices,
Using Situational awareness and decision making
Writing User-Oriented Instructions and Manuals Debopriyo Roy.
 Students will be able to:  List items in a AI plan  List items to include in an AI kit  Explain why human error could be a cause or a symptom of.
LEADERSHIP COACHING OBJECTIVES
Tutoring and Learning: Keeping in Step David Wood Learning Sciences Research Institute: University of Nottingham.
Assessing the Curriculum Gary L. Cates, Ph.D., N.C.S.P.
A Manager’s Guide to Performance Management Tyler Wade
The Scientific Method And the watermelon lab.
University of Palestine software engineering department Testing of Software Systems Fundamentals of testing instructor: Tasneem Darwish.
The Field Guide to Human Error Investigations- The Old View (Chapters 1 – 6) By Dekker AST 425.
Topic 5 Understanding and learning from error. LEARNING OBJECTIVE Understand the nature of error and how health care can learn from error to improve patient.
How Would You Know You’re Not As Good As You Think You Are? Learning To Learn Bill Rigot1.
| House of Leaves [day3] Schedule: 1.Attendance & Questions? 2.Twilight 3.Discussion groups 4.Large Group 5.Discussion groups, revisited 6.HW.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 7: Focusing on Users and Their Tasks.
Journal Write a paragraph about a decision you recently made. Describe the decision and circumstances surrounding it. How did it turn out? Looking back,
©2010 John Wiley and Sons Chapter 6 Research Methods in Human-Computer Interaction Chapter 6- Diaries.
The Scientific Method And the watermelon lab. What is the scientific method? It is a step by step procedure of scientific problem solving. Similar to.
APPENDIX M1- Tripod Student and Teacher Surveys: The Seven C’s 1.Care pertains to teacher behaviors that help students to feel emotionally safe and to.
Problem Solving Session 1 Introduction. In this session we will be Reviewing the topics that will be covered in this module Discussing expectations Filling.
Chapter 16 Problem Solving and Decision Making. Objectives After reading the chapter and reviewing the materials presented the students will be able to:
User Support Chapter 8. Overview Assumption/IDEALLY: If a system is properly design, it should be completely of ease to use, thus user will require little.
Requirements Validation CSCI 5801: Software Engineering.
Gile Sampling1 Sampling. Fundamental principles. Daniel Gile
Software Testing and Maintenance 1 Code Review  Introduction  How to Conduct Code Review  Practical Tips  Tool Support  Summary.
Evolving Approaches to Documentation and the Student Interview Melanie Thornton Adam Meyer.
Introduction and the Diagnostic Approach 07/02/2013.
Hazard Identification
HEALTHY CHOICES: Accepting Responsibility Lawndale High School Ms. Mai.
A guide to... Safe Systems of Work.
Michael A. Hitt C. Chet Miller Adrienne Colella Slides by R. Dennis Middlemist Michael A. Hitt C. Chet Miller Adrienne Colella Chapter 4 Learning and Perception.
February 15, 2004 Software Risk Management Copyright © , Dennis J. Frailey, All Rights Reserved Simple Steps for Effective Software Risk Management.
Introduction Teaching without any reflection can lead to on the job. One way of identifying routine and of counteracting burnout is to engage in reflective.
Copyright 2010, The World Bank Group. All Rights Reserved. Testing and Documentation Part II.
Assessment. Levels of Learning Bloom Argue Anderson and Krathwohl (2001)
The Risk Management Process
I DENTIFYING C AUSES OF A CCIDENTS Surface vs. Root Causes Surface causes are: the hazardous conditions or unsafe work practices that directly or indirectly.
Case Studies and Review Week 4 NJ Kang. 5) Studying Cases Case study is a strategy for doing research which involves an empirical investigation of a particular.
MODULE 9 MANAGERS AS DECISION MAKERS “Decide first, then act” How do managers use information to make decisions and solve problems? What are the steps.
Monitoring, review and audit.
2.7 Risk Management Otama Adventure 3 Credits. 3 Aims for the unit 1. Life Long Learners: Informed decision makers To be aware of risks in outdoor settings.
Chapter 14 - Analyzing a Case and Writing a Case Report 1 Understanding the Case Method of Learning What is the case method?  Applies the ancient Socratic.
1 Kevin O’Connor Airworthiness Surveyor Civil and Military Design, Production & Continuing Airworthiness Root Cause Analysis Project…
RISK MANAGEMENT FOR COMMUNITY EVENTS. Today’s Session Risk Management – why is it important? Risk Management and Risk Assessment concepts Steps in the.
Section. Communication – the process of exchanging information, ideas. and feelings Senders and receivers –Every message Needs to be sent Received Understood.
Human & Organizational Performance – H.O.P.
ON “SOFTWARE ENGINEERING” SUBJECT TOPIC “RISK ANALYSIS AND MANAGEMENT” MASTER OF COMPUTER APPLICATION (5th Semester) Presented by: ANOOP GANGWAR SRMSCET,
Human Performance Improvement/ HRO
University of Bahrain College of Business Administration Management & Marketing Department Chapter Five: Decision Making, Learning, Creativity and Entrepreneurship.
Assessment.
Assessment.
SY DE 542 User Testing March 7, 2005 R. Chow
Narrative Writing (Imaginative)
Unit 6: Application Development
Costa’s Levels of Questioning
Presentation transcript:

The Field Guide to Human Error Investigations Chapters 7 – 13 “The New View of Human Error” AST 425

The New View Human Error is a symptom of trouble deeper inside a system To explain failure, do not try to explain where people went wrong Instead, investigate how people’s assessments and actions would have made sense at the time, given the circumstances that surrounded them

Chapter 7- New View Human error is not the cause, it is the effect or symptom of deeper trouble Human error is not random, it is systematically connected to features of people’s tools, tasks and operating environment Human error is not the conclusion of an investigation, it is the beginning

New View Safety is never the only goal in systems that people operate. Goals are multiple (schedules, economic, competition, etc.) Trade-offs between safety and other goals often must be made under uncertainty and ambiguity. People decide to “borrow” from the safety goal to accomplish these other goals Systems are not basically safe, people create safety by adapting under pressure and acting under uncertainty

New View- People People are vital to “negotiating” safety under these circumstances Under these conditions, human error should be expected

New View of Error Errors/Failures should be treated as: –A window on a problem which might happen again –A red flag in the everyday operation of a system and an opportunity to learn about the conditions which caused the failure potential

New View Recommendations Seldom focus on individuals- everyone is potentially vulnerable Do not focus on tightening procedures- individuals need discretion to deal with complex operations Do not get trapped in the promise of new technology (which will present new opportunities for error) Speak in systemic terms- organizational conditions, operational conditions, or technological features

Chapter 8- Human Data, fault finding Traditional investigations have gathered Human Factors data by: –Interviewing peers or others who give their opinion about the people under scrutiny –Scrutinize training or other relevant records –Document what people did leading up to the accident –Fuels the Bad Apple Theory

Human Data The problem of the previous method lies in human memory: –Memory is not like a tape which can be rewound –Often it is impossible to separate actual events and cues which were observed from later inputs –Human memory tends to order and structure events more than they actually were- we add plausibility to fill in gaps

Human Data Participants should be allowed to tell their story with questions from the investigator such as: –What were you seeing? –What were you focusing on? –What were you expecting to happen? –What pressures were you experiencing? –Were you making any operational trade-offs? –Were you trained to deal with this situation? –Were you reminded of any previous experience?

Chapter 9, Reconstructing the Unfolding Mindset Lay out the sequence of events in time Divide the sequence of events into episodes Find the data you now know to have been available to people during the episode- was the right data available? Was it complete? Identify what was observed during the event and why it made sense (particularly harsh or salient cues will attract attention even if they are little understood at the time)- the hard part

Chapter 10- Patterns of Failure Technology- new technology doesn’t eliminate human error, it changes it- attention slips from managing the process to managing the automation interface Automation relies on monitoring- something humans aren’t good at for infrequent events Many automated systems provide users with little feedback allowing operators to detect discrepencies.

Ch. 10 Pilots often interpret their automation based on what they believe they have told it to do and not on the (often weaker more ambiguous) cues as to what is actually happening It takes a very compelling cue to get pilots to change this mindset.

Ch. 10- drift Accidents don’t just occur, they are the result of an erosion of margins that went unnoticed- less defended systems are more vulnerable (ie. A J-3 cub in someone’s barn vs. a 747) Often the absence of adverse consequences of violations lead people down the wrong path- “the normalization of deviance”- to understand why we need to understand the complexity behind the violation Recognize that Safety is not a constant- what causes an accident today may not tommorrow

Ch. 10 Real progress in safety lies in seeing the similarities between events which may highlight particular patterns toward breakdown (ie. The airbus being in Vertical speed mode rather than a descent angle mode)

Chapter 11- Writing Recommendations Can be “high end” (recommending the reallocation of resources) or “low end” (changing a procedure) The easier a recommendation can be sold, the less effective it will be- true solutions are seldom simple and are usually costly Recommendations should focus on change not “diagnosis”

Chapter 12- Learning from Failure Use Outside “objective” auditors Avoid accepting errors as “just human” Avoid “setting an example” of individual failures- this just makes people avoid reporting errors Avoid Compartmentalization- seek to find commonalities in failure Avoid passing the buck- safety is everyone’s problem

Ch. 12 Those making safety decisions should never divorce themselves totally from the day-to-day operations becoming immersed in an idealized world

Chapter 13- In Summary You cannot use the outcome of a sequence of events to assess the quality of the decisions and actions that led up to it Don’t mix elements from your own reality now into the reality that surrounded people at the time. Resituate performance in the circumstances that brought it fourth

Summary Don’t present the people you investigate with a shopping bag full of epiphanies (“it should have been so clear!”) as this is seldom the way the evidence presented itself Recognize that consistencies, certainties and clarities are products of your hindsight- not data available to those in the situation

Summary To understand human performance, you must understand how the situation unfolded around people at the time- try to understand how people’s actions made sense at the time Remember the point of a human error investigation is to understand “why” not to judge them for what they did not do.

Finally Remember the fundamental difference between “explaining” and “excusing” human performance- Some people always need to bear the brunt of a system’s failure; usually it’s those on the blunt end of a system (manager’s, supervisors, etc.)