Systems ambiguity: A framework to assess risks and predict potential systems failures

Ayse P. Lrurses, Yan Xiao, Kristin Seidl, Vinay Vaidya, Grant Bochicchio

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

4 Scopus citations

Abstract

To be a high-reliability organization, organizations need to continually assess risks and predict potential failures before even they actually occur. In this paper, we present a new method to uncover and assess risks and failures embedded in a work system: systems ambiguity framework. We define systems ambiguity as uncertainty or vagueness that may prevent a work system from achieving its purpose. We identified five main types of ambiguity in a work system: task ambiguity, responsibility ambiguity, expectation ambiguity, method ambiguity, and exception ambiguity. Examples for each type of ambiguity are provided from a qualitative study aimed at identifying the underlying causes of non-compliance to evidence based guidelines in intensive care units. We argue that systems ambiguity framework can be used alone or in conjunction with well-known risk assessment methods (e.g., root cause analysis, failure modes and effects analysis) to uncover systems failures both reactively and proactively.

Original languageEnglish
Title of host publication51st Annual Meeting of the Human Factors and Ergonomics Society, HFES 2007
Pages626-630
Number of pages5
StatePublished - 2007
Event51st Annual Meeting of the Human Factors and Ergonomics Society, HFES 2007 - Baltimore, MD, United States
Duration: Oct 1 2007Oct 5 2007

Publication series

NameProceedings of the Human Factors and Ergonomics Society
Volume2
ISSN (Print)1071-1813

Conference

Conference51st Annual Meeting of the Human Factors and Ergonomics Society, HFES 2007
Country/TerritoryUnited States
CityBaltimore, MD
Period10/1/0710/5/07

Fingerprint

Dive into the research topics of 'Systems ambiguity: A framework to assess risks and predict potential systems failures'. Together they form a unique fingerprint.

Cite this