Oops Preventing Human Error
Contents |
your password? Mission human error computer security EERL's mission is to be the best possible online collection of environmental and energy sustainability resources for community college educators
Examples Of Human Error In Information Technology
and for their students. The resources are also available for practitioners and the public. EERL & ATEEC EERL is a product of a community college-based National Science Foundation Center, the Advanced Technology Environmental and Energy Center (ATEEC), and its partners. Contact ATEEC 563.441.4087 or by email ateec@eicc.edu ©1999–2014 Advanced Technology Environmental and Energy Center (ATEEC) | Leave Feedback
from iTunes or Google Play,or view within your browser. More information here Failure and Recovery PDF December 6, 2004Volume 2, issue 8
Name 5 Ways That A Computer Can Be The Object Of A Crime.
Coping with Human Error Errors Happen. How to Deal. Aaron B. Brown, how to reduce human error in the workplace IBM Research Human operator error is one of the most insidious sources of failure and data loss in human error in information system today's IT environments. In early 2001, Microsoft suffered a nearly 24-hour outage in its Web properties as a result of a human error made while configuring a name resolution system. http://www.eerl.org/index.php?P=FullRecord&ID=1721 Later that year, an hour of trading on the Nasdaq stock exchange was disrupted because of a technician's mistake while testing a development system. More recently, human error has been blamed for outages in instant messaging networks, for security and privacy breaches, and for banking system failures. Although these scenarios are not as spectacularly catastrophic as their analogues in other engineering http://queue.acm.org/detail.cfm?id=1036497 disciplines--the meltdown of the Chernobyl nuclear plant or the grounding of the Exxon Valdez oil tanker, for example--their societal consequences can be nearly as severe, causing financial uncertainty, disruption to communication, and corporate instability. It is therefore critical that the designers, architects, implementers, and operators of today's IT infrastructures be aware of the human error problem and build in mechanisms for tolerating and coping with the errors that will inevitably occur. This article discusses some of the options available for embedding "coping skills" into an IT system. THE INEVITABILITY OF HUMAN ERROR Human error happens for many reasons, but in the end it almost always comes down to a mismatch between a human operator's mental model of the IT environment and the environment's actual state. Sometimes this confusion arises from poorly designed status feedback mechanisms, such as the perplexing error messages that Paul Maglio and Eser Kandogan discuss elsewhere in this issue (see "Error Messages: What's the Problem?" on page 50), but other times the mismatch simply arises from a lack of experience on the operator's part, or worse, to
and event prevention for individuals and for high reliability organizations. Opinions and training content will be shared and offered for use in your programs. Click here for brand new http://www.humanperformancetools.com/human-performance-tools-spotlight-oops-process-parameter-procedure/ Human Performance Training Courses Human Performance Fundamentals Observation and Coaching Class Team Building to Improve Leadership and Communication Skills Dynamic Learning Activities Workshop Managing Distractions Corrective Action Review Board Basic Human Performance Causal Analysis Integrating Human Performance into existing training programs Human Performance Steering Committee Services HPT Provides Human Performance human error Training Human Performance Program Assessment Human Performance Program Development Speeches, Keynotes, and Presentations Human Performance Film Festival Podcast Updates Interviews Mission Smart Phone About Human Performance Tool Spotlight: OOPS - Outside Of Procedure, Parameters, or Process - STOP 4 April, 2016 James D. Newman OOPS, Questioning Attitude, Stop When Unsure, Time human error in Out, Tools 2 comments Holy cow, a Human Performance tool called, "OOPS?" Well, not really. It's only an addition (or interpretation) to Stop When Unsure and Questioning Attitude. Using a Questioning Attitude (holding off on my argument that SWU and QA are not even tools at all, because these should be used all the time, and tools only when they matter the most) while performing work and you find a reading or situation off normal, STOP. This seems pretty simple and to the point. Staying engaged and thinking about the work. So, let's evaluate OOPS and why it's possibly more effective than Stop When Unsure. The keyword being "Unsure" - it sounds like the worker doesn't know what they're doing - lacking training or knowledge to perform the task. This sounds accusatory and perhaps even with a little blame. What I've come to learn about people and Human Performance Program
be down. Please try the request again. Your cache administrator is webmaster. Generated Sun, 23 Oct 2016 13:56:58 GMT by s_wx1196 (squid/3.5.20)