Stephen L. Dorton;Glenn J. Lematta;Kelly J. Neville
{"title":"The Tough Sell of Resilience Engineering","authors":"Stephen L. Dorton;Glenn J. Lematta;Kelly J. Neville","doi":"10.1109/TTS.2024.3484176","DOIUrl":null,"url":null,"abstract":"We provide an argument for why current Resilience Engineering (RE) tools are unlikely to see widespread adoption, and recommendations for making more adoptable RE tools. Resilience engineering continuously grows in popularity, and various RE tools have existed for years; however, we have found that convincing technology development teams to use RE tools is a “tough sell” for a variety of reasons. We synthesized insights and lessons learned from interacting with numerous technology development teams and the scholarly literature on RE. We then analyzed a set of RE tools through the lens of these insights, and we developed a cohesive and analysis-driven argument for why RE tools are a tough sell, and, more importantly, we developed recommendations to improve future tools. We found that challenges for adoption of current RE tools by technology development teams include RE tools that 1) require too great a level of effort, 2) have unobvious value, 3) require the technology to already exist, 4) have a scope that exceeds agency of technology developers, and 5) do not readily generate relevant systems engineering artifacts. Different underlying factors shape or constrain the solution space; however, there are several recommendations for developing RE tools that are more likely to achieve widespread adoption by technology developers. This research is directly applicable to RE practitioners seeking to have greater engagement with technology development teams. Further, this work is likely generalizable to develop any kind of participatory tools for human-centered design.","PeriodicalId":73324,"journal":{"name":"IEEE transactions on technology and society","volume":"6 1","pages":"47-53"},"PeriodicalIF":0.0000,"publicationDate":"2024-11-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"IEEE transactions on technology and society","FirstCategoryId":"1085","ListUrlMain":"https://ieeexplore.ieee.org/document/10741953/","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
We provide an argument for why current Resilience Engineering (RE) tools are unlikely to see widespread adoption, and recommendations for making more adoptable RE tools. Resilience engineering continuously grows in popularity, and various RE tools have existed for years; however, we have found that convincing technology development teams to use RE tools is a “tough sell” for a variety of reasons. We synthesized insights and lessons learned from interacting with numerous technology development teams and the scholarly literature on RE. We then analyzed a set of RE tools through the lens of these insights, and we developed a cohesive and analysis-driven argument for why RE tools are a tough sell, and, more importantly, we developed recommendations to improve future tools. We found that challenges for adoption of current RE tools by technology development teams include RE tools that 1) require too great a level of effort, 2) have unobvious value, 3) require the technology to already exist, 4) have a scope that exceeds agency of technology developers, and 5) do not readily generate relevant systems engineering artifacts. Different underlying factors shape or constrain the solution space; however, there are several recommendations for developing RE tools that are more likely to achieve widespread adoption by technology developers. This research is directly applicable to RE practitioners seeking to have greater engagement with technology development teams. Further, this work is likely generalizable to develop any kind of participatory tools for human-centered design.