Implementation and evaluation of team science training for interdisciplinary teams in an engineering design program

Abstract Introduction: Interdisciplinary academic teams perform better when competent in teamwork; however, there is a lack of best practices of how to introduce and facilitate the development of effective learning and functioning within these teams in academic environments. Methods: To close this gap, we tailored, implemented, and evaluated team science training in the year-long Engineering Innovation in Health (EIH) program at the University of Washington (UW), a project-based course in which engineering students across several disciplines partner with health professionals to develop technical solutions to clinical and translational health challenges. EIH faculty from the UW College of Engineering and the Institute of Translational Health Sciences’ (ITHS) Team Science Core codeveloped and delivered team science training sessions and evaluated their impact with biannual surveys. A student cohort was surveyed prior to the implementation of the team science trainings, which served as a baseline. Results: Survey responses were compared within and between both cohorts (approximately 55 students each Fall Quarter and 30 students each Spring Quarter). Statistically significant improvements in measures of self-efficacy and interpersonal team climate (i.e., psychological safety) were observed within and between teams. Conclusions: Tailored team science training provided to student-professional teams resulted in measurable improvements in self-efficacy and interpersonal climate both of which are crucial for teamwork and intellectual risk taking. Future research is needed to determine long-term impacts of course participation on individual and team outcomes (e.g., patents, start-ups). Additionally, adaptability of this model to clinical and translational research teams in alternate formats and settings should be tested.

Abstract licence: CC BY-NC-SA

A person counts once a day per paper. We keep no cookie and no address: a reader is a hash that changes every day. Any month under five reads shows no number.