Interruption science

From AviationSafetyX Wiki
Jump to navigation Jump to search

Interruption science is the interdisciplinary scientific study concerned with how interruptions affect human performance, and the development of interventions to ameliorate the disruption caused by interruptions.[1] Interruption science is a branch of human factors psychology and emerged from human–computer interaction and cognitive psychology.

Being ubiquitous in life and an intuitive concept, there are few formal definitions of interruption. A commonly agreed upon definition proposed by Boehm-Davis and Remington specifies an interruption is "the suspension of one stream of work prior to completion, with the intent of returning to and completing the original stream of work".[2] Interruptions are considered to be on the spectrum of multitasking and in this context referred to as sequential multitasking.[3] The distinguishing feature of an interruption (see Task switching (psychology), concurrent multitasking) is the presence of primary task which must be returned to upon completing a secondary interrupting task.[3] For instance, talking on the phone while driving is generally considered an instance of concurrent multitasking; stopping a data entry task to check emails is generally considered an instance of an interruption.

Interruptions, in almost all instances, are disruptive to performance and induce errors.[4] Therefore, interruption science typically examines the effects of interruptions in high-risk workplace environments such as aviation,[5] medicine,[6] and vehicle operation[7] in which human error can have serious, potentially disastrous consequences. Interruptions are also explored in less safety-critical workplaces, such as offices, where interruptions can induce stress,[8] anxiety,[9] and poorer performance.[10]

History

<templatestyles src="Module:Message box/ambox.css"></templatestyles>

The first formal investigation into interruptions was conducted by Zeigarnik and Ovsiankina as part of the Vygotsky Circle in the 1920s. Their seminary research demonstrated the Zeigarnik effect: people remember uncompleted or interrupted tasks better than completed tasks. In the 1940s, Fitts and Jones reported that interruptions were a cause of pilot errors and flying accidents, and made recommendations on reducing these disruptive effects.[11]

Theoretical models

Template:Empty section

Knowledge workers

Office workers face a number of interruptions due to information technologies such as e-mail, text messages, and phone calls. One line of research in interruption science examines the disruptive effects of these technologies and how to improve the usability and design of such devices. According to Gloria Mark, "the average knowledge worker switches tasks every three minutes, and, once distracted, a worker can take nearly a half-hour to resume the original task".[12] Mark conducted a study on office workers, which revealed that "each employee spent only 11 minutes on any given project before being interrupted".[13] Kelemen et al. showed that a team of programmers is interrupted through a technical Skype support chat up to 150 times a day, but these interruptions can be reduced by introducing a dispatcher role and a knowledge base.[14]

Notifications

One of the major challenges associated with increased reliance on information technologies is they will send users notifications, without considering current task demands. Answering notifications impedes task performance and the ability to resume to the original task at hand.[15] In addition, even just knowing that one has received a notification can negatively impact sustained attention.[16]

Several solutions have been proposed to this problem. One study suggested entirely disable email notifications. The down side was it may induce a pressure to constant need to check their email accounts.[15]: 27  In fact, entirely removing notifications may lead people to spend more time checking their email.[15]: 29  The absence of e-mail notifications is often seen as counterproductive because of the required "catch-up" time periods after a long time between email checking.[15]: 30  Alternatively, there are several attempts to design software applications that deliver notifications when there is an identified break from work,[17] or categorize notifications based on their relative importance (e.g. Oasis).

Research has also investigated the effects of relevant interruptions, and found notifications relevant to the current task are less disruptive than if it were unrelated.[18]: 99  Overall task performance is most impacted when an instant message is received during fast and stimulus-driven tasks such as typing, pressing buttons, or examining search results.[19]: 263, 265, 268 

Bounded deferral is a restricted notification method that entails users waiting a prescribed amount of time before they access a notification to reduce the amount of interruption and decline in productivity. This technique was used in the aim to provide calmer and less disruptive work spaces.[20]: 1  If users are busy, alerts and notifications are put aside and delivered only when users are in a position to receive notifications without harming their work. The bounded deferral method has proven to be useful and has the potential to become even more effective on a wider scale, as it has showed how an effective notification system can operate.

Medicine

For a surgeon, interruption during an operation could have serious consequences. Yet in some cases, a surgeon may need to be interrupted to make him or her aware of new issues arising with the patient.

In nursing, a study has been conducted of the impact of interruptions on nurses in a trauma center.[21] Another study has been done on the interruption rates of nurses and doctors.[22]

Interruption caused by smartphone use in health-care settings can be deadly. Hence, it may be worthwhile for health care organizations to craft effective cellphone usage policies to maximize technological benefits and minimize unnecessary distraction associated with smartphone use.[23]

See also

References


Further reading

  • Adamczyk P. D. & Bailey B. P. (2004) If not now, when?: The effects of interruption at different moments within task execution, in: Human Factors in Computing Systems: Proceedings of CHI'04, New York: ACM Press, 271-278
  • Lua error: bad argument #1 to "get" (not a valid title).
  • Lua error: bad argument #1 to "get" (not a valid title).
  • Bailey, B. P., Konstan, J. A., & Carlis, J. V. (2001). The Effects of Interruptions on Task Performance, Annoyance, and Anxiety in the User Interface. Proceedings of INTERACT '01, IOS Press, 593–601.
  • Cades, D. M., Davis, D. A. B., Trafton, J. G., & Monk, C. A. (2007). Does the difficulty of an interruption affect our ability to resume? In Proceedings of the Human Factors and Ergonomics Society Annual Meeting (Vol. 51, pp. 234–238). SAGE Publications.
  • Lua error: bad argument #1 to "get" (not a valid title).
  • Lua error: bad argument #1 to "get" (not a valid title).
  • Lua error: bad argument #1 to "get" (not a valid title).
  • Lua error: bad argument #1 to "get" (not a valid title).
  • Hodgetts H. M., Jones D. M. (2006) Interruption of the Tower of London task: Support for a goal-activation approach, Journal of Experimental Psychology: General. 135 (1): 103-115. https://doi.org/10.1037/0096-3445.135.1.103
  • Lua error: bad argument #1 to "get" (not a valid title).
  • Latorella, K. A. (1999). Investigating interruptions: Implications for flight deck performance (Technical Memorandum NASA/TM-1999-209707), (October).
  • Lua error: bad argument #1 to "get" (not a valid title).
  • Lua error: bad argument #1 to "get" (not a valid title).
  • Remington, R. W., & Loft, S. (2015). Attention and multitasking. APA Handbook of Human Systems Integration., (1918), 261–276. doi 10.1037/14528-017
  • Salvucci, D. D., & Taatgen, N. A. (2011). The multitasking mind. Oxford series on cognitive models and architectures. Retrieved from http://lib.myilibrary.com/detail.asp?ID=279322\nhttp://firstsearch.oclc.org/WebZ/DECRead?standardNoType=1&standardNo=0199733562&sessionid=0&srcdbname=worldcat&key=455a3d5fd3b04b30b7e62eefaccb0a6c37c006d081c99153ebf63d6646df2b41&ectype=MOREINFO\nhttp://fir
  • Lua error: bad argument #1 to "get" (not a valid title).
  • Lua error: bad argument #1 to "get" (not a valid title).
  • Lua error: bad argument #1 to "get" (not a valid title).
  1. ↑ Lua error: bad argument #1 to "get" (not a valid title).
  2. ↑ Lua error: bad argument #1 to "get" (not a valid title).
  3. ↑ 3.0 3.1 Lua error: bad argument #1 to "get" (not a valid title).
  4. ↑ Lua error: bad argument #1 to "get" (not a valid title).
  5. ↑ Lua error: bad argument #1 to "get" (not a valid title).
  6. ↑ Lua error: bad argument #1 to "get" (not a valid title).
  7. ↑ Lua error: bad argument #1 to "get" (not a valid title).
  8. ↑ Lua error: bad argument #1 to "get" (not a valid title).
  9. ↑ Lua error: bad argument #1 to "get" (not a valid title).
  10. ↑ Lua error: bad argument #1 to "get" (not a valid title).
  11. ↑ Lua error: bad argument #1 to "get" (not a valid title).
  12. ↑ Lua error: bad argument #1 to "get" (not a valid title).
  13. ↑ Lua error: bad argument #1 to "get" (not a valid title).
  14. ↑ Lua error: bad argument #1 to "get" (not a valid title).
  15. ↑ 15.0 15.1 15.2 15.3 Lua error: bad argument #1 to "get" (not a valid title).
  16. ↑ Lua error: bad argument #1 to "get" (not a valid title).
  17. ↑ Notification, Disruption, and Memory: Effects of Messaging Interruptions on Memory and Performance.  Edward Cutrell.  Microsoft Research.  Retrieved 15 October 2012 from link
  18. ↑ Lua error: bad argument #1 to "get" (not a valid title).
  19. ↑ Lua error: bad argument #1 to "get" (not a valid title).
  20. ↑ Balancing Awareness and Interruption: Investigation of Notification Deferral Policies.  Eric Horvitz.  Microsoft Research.  Retrieved 17 October 2012 from link
  21. ↑ Brixey J. J., Robinson D. J., Tang Z., Johnson T. R., Zhang J. & Turley J. P. (2005) "Interruptions in Workflow for RNs in a Level-One Trauma Center", in: AMIA 2005 Annual Symposium Proceedings, Bethesda, MD: American Medical Informatics Association, 86-90
  22. ↑ Lua error: bad argument #1 to "get" (not a valid title).
  23. ↑ Lua error: bad argument #1 to "get" (not a valid title).
Retrieved from "https://wiki.alsresume.com/index.php?title=Interruption_science&oldid=348"