<italic xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink"><b>Background:</b></i> Communication is the backbone of effective collaboration, enabling project success; yet, engineering projects often fail due to poor communication. Specifically, engineering teams may benefit from reflexivity interventions to improve decision making, problem solving, innovation, and performance. In this study, we focus on team reflexivity in direct application to engineering project management to identify reflexivity processes that facilitate effective communication. <italic xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink"><b>Literature review:</b></i> Although research has shown that team reflexivity interventions—elicited through communication—can improve team interaction and performance, little empirical evidence exists into the temporal dimensions across the action and transition phases of team reflexivity processes. <italic xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink"><b>Research questions:</b></i> 1. How is team reflexivity expressed through text-based communication? 2. How and when do team members shift between reflexivity processes over time, especially across and between transition and action phases? <italic xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink"><b>Research methodology:</b></i> We analyzed collaborative activity among 62 four-person teams in a computer-simulated microworld across two scenarios. The reflexivity processes exhibited during interaction were identified and analyzed using statistical and content analysis. <italic xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink"><b>Results and discussion:</b></i> Analyses indicated that team reflection promoted discussions about key issues, facilitated frequent process shifts among transition and action phases, and resulted in overall better performance. <italic xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink"><b>Conclusions:</b></i> Our findings demonstrate the importance of team reflexivity interventions in engineering project teams to strategically guide members to improve planning, responding, and quality of attention devoted to long-term outcomes. Furthermore, our findings demonstrate the importance of deep structured team reflexivity through process shifts to help members understand strategies and goals, and develop shared objectives in complex environments.

Background: Communication is fundamental to the success of engineered systems, enabling interactions between the system's stakeholders. Systems engineering, an integrative discipline on which the contributions of many disciplines are evaluated against each other, may particularly benefit from research in communication methods. Specifically, storytelling may be beneficial to engineers because it enables sense-making. Research into storytelling is conducted to identify storytelling metrics that could be useful in engineering communication, specifically engineering case studies. Literature review: Although storytelling has been identified in past research as possibly useful to Model-Based Systems Engineering (MBSE) and software requirement writing, a rigorous study of the use of storytelling elements in systems engineering communication has not been performed. Research question: How are storytelling elements currently being applied in engineering case studies? Research methodology: Twelve interdisciplinary metrics from storytelling, content analysis, and engineering are identified from the literature and used to characterize a collection of 48 NASA case studies. The values of the metrics for each case study are determined and analyzed using statistical and content analyses. Results and discussion: Analysis of the 12 metrics indicates that the case study design region with a historical backstory structure, climactic plot structure, and early points of attack is most frequently used by designers. Conclusions: The analysis indicates that certain storytelling elements applied in engineering case studies are used more frequently. Further work is needed to leverage the metrics as design variables in engineering case study writing.