| Literature DB >> 35360608 |
Lauren N P Campbell1, Elisa M Torres1, Stephen J Zaccaro1, Steven Zhou1, Katelyn N Hedrick2, David M Wallace3, Celeste Raver Luning3, Joanna E Zakzewski1.
Abstract
Multiteam systems (MTSs) are complex organizational forms comprising interdependent teams that work towards their own proximal goals within and across teams to also accomplish a shared superordinate goal. MTSs operate within high-stakes, dangerous contexts with high consequences for suboptimal performance. We answer calls for nuanced exploration and cross-context comparison of MTSs "in the wild" by leveraging the MTS action sub-phase behavioral taxonomy to determine where and how MTS failures occur. To our knowledge, this is the first study to also examine how key MTS attributes (boundary status, goal type) influence MTS processes and performance. We conducted historiometric analysis on 40 cases of failed MTS performance across various contexts (e.g., emergency response, commercial transportation, military, and business) to uncover patterns of within- and between-team behaviors of failing MTSs, resulting in four themes. First, component teams of failing MTSs over-engaged in within-team alignment behaviors (vs. between-team behaviors) by enacting acting, monitoring, and recalibrating behaviors more often within than between teams. Second, failing MTSs over-focused on acting behaviors (vs. monitoring or recalibrating) and tended to not fully enact the action sub-phase cycle. Third and fourth, boundary status and goal type exacerbated these behavioral patterns, as external and physical MTSs were less likely to enact sufficient between-team behaviors or fully enact the action sub-phase cycle compared to internal and intellectual MTSs. We propose entrainment as a mechanism for facilitating MTS performance wherein specific, cyclical behavioral patterns enacted by teams align to facilitate goal achievement via three multilevel behavioral cycles (i.e., acting-focused, alignment-focused, and adjustment-focused). We argue that the degree to which these cycles are aligned both between teams and with the overarching MTS goal determines whether and how an MTS fails. Our findings add nuance beyond single-context MTS studies by showing that the identified behavioral patterns hold both across contexts and almost all types of MTS action-phase behaviors. We show that these patterns vary by MTS boundary status and goal type. Our findings inform MTS training best practices, which should be structured to integrate all component teams and tailored to both MTS attributes (i.e., boundary status, goal type) and situation type (e.g., contingency planning).Entities:
Keywords: entrainment; historiometric method; multiteam systems; performance; teams and groups
Year: 2022 PMID: 35360608 PMCID: PMC8960246 DOI: 10.3389/fpsyg.2022.813624
Source DB: PubMed Journal: Front Psychol ISSN: 1664-1078
MTS Action Subphase Behavioral Inventory.
| Within-Team MTS Action Subphases and Behaviors | |
|---|---|
| Acting | Within-team behaviors associated with goal striving and MTS goal accomplishment, including implementing adaptation plans identified in recalibrating phase |
| 1 | Execute protocols that coordinate team members’ activities around MTS goal accomplishment |
| 2 | Enact appropriate alignment of team members’ activities to facilitate appropriate pacing of MTS actions |
| 3 | Implement modifications to member resources to align with MTS task requirements |
| 4 | Implement modifications to team member response sequence to maintain appropriate pacing of MTS task requirements |
| 5 | Implement modifications to team member tasks and actions to align with the actions of other focal teams in the MTS |
| Monitoring | Continuous within-team observation and communication used to track goal progress and quality of MTS performance over time |
| 6 | Track team members tasks and progress toward MTS goal accomplishment |
| 7 | Track use and availability of team resources that support MTS goal accomplishment |
| 8 | Track information about an event/incident/threat impacting MTS goal accomplishment |
| 9 | Exchange information with focal team members regarding progress toward accomplishing team and MTS goals |
| 10 | Exchange information with team members regarding changes in MTS environmental characteristics and constraints that signal the need for adjustment or adaptation |
| 11 | Acknowledge cues and triggers in the MTS environment (e.g., elements of a developing event/incident/threat) that indicates component team member adjustments or adaptation is required for MTS goal accomplishment |
| 12 | Alert team members about incidents requiring MTS adjustment or adaptation and the impact on between-team interactions |
| Recalibrating | Identification of the need for within-team action adjustments and adaptation; development of such plans for subsequent actions; and dissemination of these plans to team members |
| 13 | Exchange information with team members to develop a shared understanding of incident triggers and adjustments or adaptation cue stream to appropriately align team members actions with modified MTS actions |
| 14 | Develop a course of action for adjusting or adapting team member actions to align with MTS actions |
| 15 | Communicate updated team member action and/or between-team action plan(s) with focal team members |
|
| |
| Acting | Between-team behaviors associated with goal striving and MTS goal accomplishment, including implementing adaptation plans identified in recalibrating phase |
| 16 | Execute interdependence between-team actions according to MTS sequence and timing |
| 17 | Engage in between-team back-up behavior, assisting component team task accomplishment |
| 18 | Share material and personnel resources between teams |
| 19 | Implement modifications to between-team actions and tasks |
| 20 | Implement modifications to between-team response sequence to maintain appropriate pacing of MTS tasks |
| Monitoring | Continuous between-team observation and communication used to track goal progress and quality of MTS performance over time |
| 21 | Track component teams’ activities and process toward MTS goal accomplishment |
| 22 | Exchange information between teams regarding MTS environmental characteristics and constraints that signal the need for between-team action adjustment or adaptation |
| 23 | Exchange information between teams regarding team goal progress |
| 24 | Exchange information between teams regarding team resources and constraints |
| 25 | Acknowledge cues and triggers in the MTS environment (e.g., elements of a developing event/incident/threat) that indicates between-team action adjustment or adaptation is required for MTS goal accomplishment |
| 26 | Alert other teams about incidents requiring between-team adjustment or adaptation |
| Recalibrating | Identification of the need for between-team action adjustments and/or adaptation; development of such plans for subsequent actions; and dissemination of these plans between component teams |
| 27 | Exchange information between teams to develop a shared understanding of incident triggers and adjustment or adaptation cue stream |
| 28 | Develop a course of action for adjusting or adapting between-team coordinated action |
| 29 | Communicate updated action plan between component teams |
Adapted from Torres et al. (2021).
Aligning-type acting subphase behaviors;
Adjusting-type acting subphase behaviors.
Tracking-type monitoring subphase behaviors;
Communicating-type monitoring subphase behaviors.
Figure 1Percent Within vs. Between Behaviors across All Cases by Subphase and Acting and Monitoring Behavior Types. The y-axis represents the percentage of within-team (orange) vs. between-team (yellow) behaviors represented in each behavior type as indicated in the x-axis. The x-axis includes a column for all of the coded behaviors, as well as each subphase behavior type (i.e., acting, monitoring and recalibrating) and each subtype for acting (i.e., aligning and adjusting) and monitoring (i.e., tracking and communicating). For example, the furthest right column indicates that, of all of the coded recalibrating behaviors, 58% occurred at the within-team level and 42% occurred at the between-team level.
Included Cases of Failed MTS Performance.
| Industry | Case summary | Data Source(s) | Bound. status | Goal type |
|---|---|---|---|---|
| Business/Religion | 2018 Willow Creek Church dissolution following sexual harassment scandal response effort | 2 industry investigative reports, 3 news articles | E | I |
| Business/Product Dev. | 2015 Zano startup development abandonment | 1 investigative journaling report, 1 org document, 1 news article | E | I |
| Business/Construction | 1990s Denver airport automated baggage system implementation abandonment | 1 industry investigative report, 1 news article | E | I |
| Business | 2010 Deepwater Horizon explosion and oil spill | 6 gov’t/industry investigative reports, 2 gov’t articles, 3 academic articles, 2 news articles, 1 org manual | E | P |
| Business/Government | 1987–1992 DMV records digitization abandonment | 1 academic article, 1 legal document, 1 news article | E | I |
| Business/Government | 2013 Affordable Care Act website launch delay | 2 gov’t investigative reports, 1 academic commentary article, 7 news articles | E | I |
| Science/Government | 2003 NASA Columbia shuttle landing crash | 3 gov’t investigative reports | I | P |
| Emergency Response | 2013 Washington, DC Navy Yard active shooter response effort | 2 gov’t investigative reports, 4 news articles | E | P |
| Emergency Response | 2016 Orlando, FL Pulse nightclub active shooter response effort | 2 gov’t/industry investigative reports, 1 news article | E | P |
| Emergency Response | 2007 Blacksburg, VA Virginia Tech active shooter response effort | 1 gov’t investigative report, 3 news articles | E | P |
| Emergency Response | 2016 Parkland, FL high school active shooter response effort | 1 news article, 1 gov’t meeting presentation and synopsis | E | P |
| Emergency Response | 2016 MD firefighter fatality during civilian welfare check | 1 gov’t investigative report | E | P |
| Emergency Response | 2013 TX fertilizer plant explosion and response effort | 4 gov’t investigative reports, 1 gov’t article, 7 news articles, 5 academic articles | E | P |
| Emergency Response | 2018 PA firefighter fatality during building collapse | 1 gov’t investigative report | E | P |
| Emergency Response | 1998 NY firefighter fatality during floor collapse | 1 gov’t investigative report | I | P |
| Emergency Response | 2016 DE firefighter fatality during arson response effort | 1 gov’t investigative report | I | P |
| Emergency Response | 2017 TX firefighter fatality during arson response effort | 1 gov’t investigative report | I | P |
| Emergency Response | 2018 TX firefighter fatality during grass fire response effort | 1 gov’t investigative report | I | P |
| Military | 2001 USS Greeneville—Ehime Maru collision | 2 gov’t investigative reports, 1 legal document, 3 news articles | I | P |
| Military | 2012 USS Essex—USNS Yukon collision | 1 gov’t investigative report, 5 news articles | I | P |
| Military | 1969 USS Evans—HMAS Melbourne collision | 1 gov’t investigative report | E | P |
| Military | 2017 USS Antietam grounding | 1 gov’t investigative report | I | P |
| Military | 2013 USS Guardian grounding | 1 gov’t investigative report, 1 gov’t article, 4 news articles | I | P |
| Military | 2012 USS San Jacinto—USS Montpelier collision | 1 gov’t investigative report, 1 gov’t article, 4 news articles | I | P |
| Military | 1975 USS Belknap—USS Kennedy collision | 1 gov’t investigative report, 1 gov’t article, 3 news articles | I | P |
| Transport | 2015 Clipper Quito—Lurongyu collision | 1 gov’t investigative report | E | P |
| Transport | 2017 Eric Haney grounding | 1 gov’t investigative report | E | P |
| Transport | 2013 Amarillo, TX three-train collision | 1 gov’t investigative report, 6 legal documents, 1 org manual | E | P |
| Transport | 2016 Granger, WY two-train collision | 1 gov’t investigative report, 6 legal documents, 1 org manual | E | P |
| Transport | 2009 Atlantic Ocean, Air France flight 447, in-air crash | 1 gov’t investigative report | E | P |
| Transport | 2016 Chicago, IL, American Airlines flight 383, take off abandonment | 1 gov’t investigative report, 1 org manual, 1 gov’t article, 1 gov’t meeting presentation and synopsis | E | P |
| Transport | 1996 Quincy, IL two-airplane runway collision | 1 gov’t investigative report, 3 gov’t articles, 2 org manuals | E | P |
| Transport | 2005 Teterboro, NJ, Platinum Jet Mgmt., departure crash | 1 gov’t investigative report, 4 gov’t articles | E | P |
| Transport | 2015 Taipei, Taiwan, TransAsia flight 235, departure crash | 1 gov’t investigative report | E | P |
| Transport | 2016 Dubai, UAE, Emirates flight 521 airplane landing crash | 2 gov’t/industry investigative reports | E | P |
| Transport | 2014 Java Sea, AirAsia flight 8,501, in-air crash | 1 gov’t investigative report | E | P |
| Transport | 2014 Magong, Penghu Island, TransAsia flight 222 landing crash | 1 gov’t investigative report | E | P |
| Transport | 2016 Lagos, Nigeria DANACO flight 992 in-air crash | 2 gov’t/industry investigative reports | E | P |
| Transport | 2009 Lubbock, TX Empire Airlines flight 8,284 landing crash | 2 gov’t/industry investigative reports | E | P |
| Transport | 2015 Islamabad, Pakistan, Bhoja flight 213 landing crash | 1 gov’t investigative report | E | P |
Boundary status: E = external, I = internal. Goal type: I = intellectual, P = physical.
Frequencies of Occurred Codes across the Cases.
| Level | Subphase | Behavior | Freq | Percent (%) | Avg | Med | Min | Max |
|---|---|---|---|---|---|---|---|---|
| Within | Acting | 1 | 517 | 16.14 | 12.83 | 8 | 0 | 54 |
| Within | Acting | 2 | 217 | 6.77 | 5.30 | 3 | 0 | 35 |
| Within | Acting | 3 | 14 | 0.44 | 0.36 | 0 | 0 | 6 |
| Within | Acting | 4 | 178 | 5.56 | 4.48 | 2 | 0 | 55 |
| Within | Acting | 5 | 101 | 3.15 | 2.53 | 1 | 0 | 37 |
| Within | Monitoring | 6 | 54 | 1.69 | 1.35 | 0 | 0 | 19 |
| Within | Monitoring | 7 | 34 | 1.06 | 0.91 | 0 | 0 | 10 |
| Within | Monitoring | 8 | 142 | 4.43 | 3.56 | 1 | 0 | 34 |
| Within | Monitoring | 9 | 94 | 2.93 | 2.33 | 0 | 0 | 52 |
| Within | Monitoring | 10 | 53 | 1.65 | 1.33 | 0 | 0 | 21 |
| Within | Monitoring | 11 | 205 | 6.40 | 5.13 | 3 | 0 | 26 |
| Within | Monitoring | 12 | 51 | 1.59 | 1.28 | 0 | 0 | 13 |
| Within | Recalibrating | 13 | 90 | 2.81 | 2.31 | 0 | 0 | 64 |
| Within | Recalibrating | 14 | 113 | 3.53 | 2.81 | 0 | 0 | 34 |
| Within | Recalibrating | 15 | 146 | 4.56 | 3.63 | 1 | 0 | 29 |
| Between | Acting | 16 | 298 | 9.30 | 7.33 | 5 | 0 | 26 |
| Between | Acting | 17 | 21 | 0.66 | 0.58 | 0 | 0 | 6 |
| Between | Acting | 18 | 9 | 0.28 | 0.23 | 0 | 0 | 4 |
| Between | Acting | 19 | 38 | 1.19 | 0.91 | 0 | 0 | 11 |
| Between | Acting | 20 | 35 | 1.09 | 0.90 | 0 | 0 | 13 |
| Between | Monitoring | 21 | 142 | 4.43 | 4.03 | 2 | 0 | 33 |
| Between | Monitoring | 22 | 75 | 2.34 | 1.80 | 1 | 0 | 12 |
| Between | Monitoring | 23 | 110 | 3.43 | 2.75 | 2 | 0 | 19 |
| Between | Monitoring | 24 | 37 | 1.16 | 0.93 | 0 | 0 | 15 |
| Between | Monitoring | 25 | 61 | 1.90 | 1.48 | 1 | 0 | 14 |
| Between | Monitoring | 26 | 114 | 3.56 | 2.81 | 2 | 0 | 18 |
| Between | Recalibrating | 27 | 50 | 1.56 | 1.23 | 0 | 0 | 17 |
| Between | Recalibrating | 28 | 71 | 2.22 | 1.73 | 0 | 0 | 14 |
| Between | Recalibrating | 29 | 133 | 4.15 | 3.31 | 1 | 0 | 25 |
Freq represents the total frequency of the coded behaviors across all cases. Percent represents the percentage of the given behavior of all coded behaviors across all cases. Avg, Med, Min, and Max represent the average, median, minimum, and maximum number of times the given behavior was coded per case. The gradient green shading in the Frq and Percent columns represents the proportion of a given cell across the column from lowest (white background) to highest (darkest green background).
Aligning-type acting subphase behaviors;
Adjusting-type acting subphase behaviors.
Tracking-type monitoring subphase behaviors;
Communicating-type monitoring subphase behaviors.
Figure 2Percent Behaviors in Each Subphase Overall and over the Action Phase of the Performance Episode. The y-axis represents the percentage of each behavior that was coded within each subphase of action performance. The x-axis includes a column for the coded behaviors that occurred both overall and within each section of the performance episode. For example, the furthest right column indicates that, of all of the behaviors coded in the last third of the performance episode, 42% were acting, 34% were monitoring, and 24% were recalibrating.
Figure 3Change in Within vs. Between Behaviors over the Action Phase of the Performance Episode by MTS Boundary Status. The y-axis represents the percentage of within-team behaviors, relative to the percentage of between-team behaviors. The x-axis indicates the coded behaviors that occurred within each section of the performance episode. For example, the furthest right data point on the lower line indicates that, for all coded behaviors in the last third of the performance episode, for cases of performance for MTSs with internal boundary status, the behaviors were 58% within-team.
Figure 4Change in Within vs. Between Behaviors over the Action Phase of the Performance Episode by MTS Goal Type. This descriptive evidence presented in this figure and throughout this theme is based upon only cases of external physical MTSs (n = 25), as the data set only includes cases of external intellectual MTSs (n = 5) due to limited availability and accessibility of cases of internal MTSs; this is discussed further in the Limitations section. By removing the cases of internal physical MTSs (n = 10) from this comparison, we aimed to mitigate confounding the effects of boundary status with those of goal type. The y-axis represents the percentage of within-team behaviors, relative to the percentage of between-team behaviors. The x-axis indicates the coded behaviors that occurred within each section of the performance episode. For example, the furthest right data point on the lower line indicates that, for all coded behaviors in the last third of the performance episode, for cases of performance for MTSs with intellectual goal types, the behaviors were 53% within-team.
Figure 5Expanded MTS Action Subphase Model for Successful and Misaligned MTS Responses to Within- and Between-Team Triggers. All figures are adapted from the original MTS Action Subphase model presented in Torres et al. (2021). Solid black rectangle represents the MTS boundary. Outlined circles represent component team boundaries. Straight arrows represent between-team interdependence. Trigger is indicated by blast shape. Curved arrows represent subphase relationships. Green curved arrow represents an appropriate response to the trigger. Red curved arrow represents an inappropriate response to the trigger. (A) Successful Adaptive MTS Response to Within-Team Trigger. The purpose of this figure is to visually depict a successful, subphase level response cycle to a within-team level trigger for adaptation. That is, this is what might occur if an MTS is operating under normal conditions, entraining the baseline behavioral cycle of acting (aligning-type behaviors) and monitoring (tracking-type behaviors) at the within- and between-team levels, when a team-level trigger occurs for Component B. In this instance, Component B shifts to a cycle that includes monitoring-communicating type behaviors, recalibrating behaviors, and acting-adjusting type behaviors. This cycle will continue until the trigger is resolved. The team may concurrently enact monitoring-tracking and acting-aligning type behaviors as well. As such, the figure above is depicted at the subphase level. (B) Misaligned Adaptive MTS Response to Within-Team Trigger via Acting-Focused Cycle. The purpose of this figure is to visually depict an unsuccessful, subphase level response cycle to a within-team level trigger for adaptation. That is, this is what might occur if an MTS is operating under normal conditions, entraining the baseline behavioral cycle of acting (aligning-type behaviors) and monitoring (tracking-type behaviors) at the within- and between-team levels, when a team-level trigger occurs for Component B. In this instance, Component B shifts to a cycle that includes only acting behaviors and, as such, is unlikely to resolve the trigger without the necessary monitoring and recalibration behaviors that are depicted in (A). These acting behaviors may include alignment and/or adjustment types; therefore, the figure above is depicted at the subphase level. (C) Misaligned Adaptive MTS Response to Within-Team Trigger via Alignment-Focused Cycle. The purpose of this figure is to visually depict an unsuccessful, subphase level response cycle to a within-team level trigger for adaptation. That is, this is what might occur if an MTS is operating under normal conditions, entraining the baseline behavioral cycle of acting (aligning-type behaviors) and monitoring (tracking-type behaviors) at the within- and between-team levels, when a team-level trigger occurs for Component B. In this instance, Component B shifts to a cycle that includes only acting and monitoring behaviors and, as such, is unlikely to resolve the trigger without the necessary recalibration behaviors that are depicted in (A). These acting and monitoring behaviors may include any combination of their behavioral types (i.e., acting-alignment and/or adjustment, monitoring-tracking, and/or -communicating); therefore, the figure above is depicted at the subphase level. (D) Successful Adaptive MTS Response to Between-Team Trigger. The purpose of this figure is to visually depict a successful, subphase level response cycle to a between-team level trigger for adaptation. That is, this is what might occur if an MTS is operating under normal conditions, entraining the baseline behavioral cycle of acting (aligning-type behaviors) and monitoring (tracking-type behaviors) at the within-team level, when a between-level trigger occurs. In this instance, the between-team behavioral cycle shifts to include monitoring–communicating type behaviors, recalibrating behaviors, and acting-adjusting type behaviors. This cycle will continue until the trigger is resolved. The teams may concurrently enact between-team level monitoring-tracking and acting-aligning type behaviors as well. As such, the figure above is depicted at the subphase level. (E) Misaligned Adaptive MTS Response to Between-Team Trigger via Acting-Focused Cycle. The purpose of this figure is to visually depict a successful, subphase level response cycle to a between-team level trigger for adaptation. That is, this is what might occur if an MTS is operating under normal conditions, entraining the baseline behavioral cycle of acting (aligning-type behaviors) and monitoring (tracking-type behaviors) at the within-team level, when a between-level trigger occurs. In this instance, the between-team behavioral cycle shifts to include only acting behaviors and, as such, is unlikely to resolve the trigger without the necessary monitoring and recalibration behaviors that are depicted in (D). These acting behaviors may include alignment and/or adjustment types; therefore, the figure above is depicted at the subphase level. (F) Misaligned Adaptive MTS Response to Between-Team Trigger via Alignment-Focused Cycle. The purpose of this figure is to visually depict a successful, subphase level response cycle to a between-team level trigger for adaptation. That is, this is what might occur if an MTS is operating under normal conditions, entraining the baseline behavioral cycle of acting (aligning-type behaviors) and monitoring (tracking-type behaviors) at the within-team level, when a between-level trigger occurs. In this instance, the between-team behavioral cycle shifts to include only acting and monitoring behaviors and, as such, is unlikely to resolve the trigger without the necessary recalibration behaviors that are depicted in (D). These acting and monitoring behaviors may include any combination of their behavioral types (i.e., acting-alignment and/or adjustment, monitoring-tracking, and/or -communicating); therefore, the figure above is depicted at the subphase level.