Team Situation Awareness Scale (TSAS)

Questionnaires are faster and less resource-intensive; ideal for rapid feedback loops and training evaluation. Observational methods are more objective but labor-intensive. Best practice: use both. Questionnaire TSAS captures perceived team coordination; observational coding captures actual communication patterns. Divergence between the two (e.g., high self-rated team SA but poor communication in transcripts) signals either social desirability bias or poor observer coding reliability. For pragmatic applications with time constraints, questionnaire suffices; for research requiring objective validation, use observation.

Low team SA may indicate: (1) poor training effectiveness, (2) high task difficulty (even well-trained teams struggle with novel, complex scenarios), (3) social desirability bias (team under-reports to appear humble), or (4) questionnaire insensitivity. Investigate by: collecting objective performance data (errors, response times, patient outcomes), conducting post-scenario interviews ('How confident were you that your team understood the situation?'), and reviewing communication transcripts. Combine TSAS with these measures to diagnose root cause before attributing low scores solely to training failure.

Each 'team' is a unit of analysis. If comparing, say, 5 surgical teams, n=5 teams. Statistical power to detect between-team differences is modest with n=5; aim for n≥10–12 teams if conducting statistical tests. Within-team, if administering TSAS to all team members (e.g., 5-person team, 5 questionnaires), you have n=5 individual respondents per team; average their ratings to yield team-level score. Report both individual- and team-level results; group-level patterns may mask individual-level disagreement.

TSAS is designed for small-to-medium teams (4–12 people) with clearly defined roles. For very large organizations (control center with 50+ operators), the concept of 'shared mental model' breaks down; instead, measure sub-team or shift-level SA. Alternatively, adapt TSAS to assess shared understanding of critical information (e.g., 'All shift members understand the current facility status') rather than roles. Large-scale organizational SA measurement requires different conceptualization; consult specialized frameworks (Organizational Learning, Safety Culture).

No. Team communication (frequency, clarity, responsiveness) is a component of team SA but not equivalent. A team could communicate extensively and still lack shared understanding (e.g., each person sharing information no one synthesizes). Conversely, a quiet, experienced team might have strong shared mental models without much explicit communication (relying on pre-established norms and implicit coordination). Measure both: TSAS assesses mental model alignment; communication analysis (coding, turn-taking, information-sharing patterns) assesses the communication process. Integrate both to understand team coordination fully.