Salas Big Five of Teamwork

1. What Is Salas Big Five of Teamwork?

The Salas Big Five of Teamwork is a research-based team effectiveness framework that identifies the core behaviors teams need in order to perform well, especially when work is interdependent, time-sensitive, and subject to change. It is not a personality model. It is a model of how teams coordinate, support one another, and adapt while doing real work.

The framework is especially useful for diagnosing why a team that is full of capable individuals still underperforms as a group. Consultants often use it when a leadership team says it has a “culture” problem but the real issue is coordination, candor, or load-sharing. That is why the model frequently appears in broader organization consulting work rather than in standalone team-building sessions.

In practice, the framework gives executives and team leaders a disciplined way to look beyond vague labels such as trust, alignment, or collaboration and ask a sharper question: which specific team behaviors are missing, inconsistent, or breaking down under pressure?

2. Origin and Background

The framework was articulated by Eduardo Salas, Dana E. Sims, and C. Shawn Burke in their 2005 article, “Is There a ‘Big Five’ in Teamwork?,” published in Small Group Research. Salas became the name most commonly associated with the model because of his extensive body of work in team performance, human factors, and training.

The authors developed the model by synthesizing prior research on team performance. Their aim was to identify the core components required for teams to adapt and perform effectively in complex environments. The original article proposed five core teamwork components and three distinct coordinating mechanisms that enable them.

The model became influential in organizational psychology, military research, aviation, healthcare, and other safety-critical settings. Over time, it moved into practical use in leadership development and team diagnostics. Some later summaries blur the line between the five core behaviors and the three enabling mechanisms, but in the original formulation they are related, not identical.

3. How Salas Big Five of Teamwork Works

The core logic is straightforward: effective teamwork is not a matter of chemistry alone. Teams perform better when a small set of observable behaviors is present, reinforced, and sustained. The framework helps teams examine those behaviors directly instead of relying on generic impressions such as “we communicate well” or “we need more trust.”

The original model identifies five core components of teamwork. These are supported by three coordinating mechanisms that make the behaviors more likely to occur consistently. In practical use, most teams turn the model into an observation checklist, a discussion guide, or a heat map of strengths and weaknesses.

The five core behaviors

The three coordinating mechanisms

• Shared mental models: a common understanding of goals, roles, priorities, status, and how the work should unfold.
• Closed-loop communication: messages are sent clearly, acknowledged, and confirmed so that assumptions do not linger.
• Mutual trust: confidence that other members are competent, reliable, and acting in the team’s interest.

The power of the framework lies in the way these elements reinforce one another. Without trust, monitoring feels intrusive. Without shared mental models, backup behavior is clumsy because people do not know what help is needed. Without communication, adaptability turns into confusion. The framework therefore works best as a system, not as a set of isolated traits.

4. When to Use Salas Big Five of Teamwork

The framework is most helpful when performance depends on real coordination across people or functions. That includes executive teams, product launch teams, transformation teams, clinical teams, plant leadership teams, deal teams, and professional-services teams. It is particularly useful when the work is dynamic, deadlines matter, and no single person can succeed independently.

It is especially powerful when leaders want to improve day-to-day ways of working—meeting quality, handoffs, escalation, cross-functional problem solving, and team responses under pressure. It is also useful after repeated missed deadlines, rework, avoidable errors, or a pattern of “we thought someone else had it.”

To use it meaningfully, teams need qualitative and behavioral evidence: interviews, meeting observations, handoff examples, post-mortems, and sometimes survey data. A quick workshop can introduce the model in a day, but a credible diagnosis usually takes one to three weeks for a single team.

The framework is not a good fit when the work is mostly independent, when the main issue is technical capability rather than coordination, or when senior leaders want a simple score without doing the harder work of observation and feedback. It can also mislead if used to explain away structural problems such as impossible spans, unclear roles, broken incentives, or chronic understaffing. For the model to work well, there must be genuine task interdependence, observable team behavior, and enough leadership willingness to act on what the diagnosis reveals.

The model remains relevant today, but practitioners now adapt it for hybrid work, agile teams, and cross-functional networks by looking at digital handoffs and asynchronous communication as well as live interaction.

5. How to Apply Salas Big Five of Teamwork: Step-by-Step

1. Clarify the decision and scope. Start by defining why the team is being assessed. Is the goal to improve executive decision making, reduce project failure, speed product launches, or strengthen cross-functional collaboration? Set the time horizon and decide whether you are examining one team, a leadership layer, or multiple comparable teams.
2. Gather the required inputs and data. Combine interviews, meeting observations, workflow examples, performance data, and recent critical incidents. Look for evidence of missed handoffs, duplicated work, silent disagreement, overload, slow escalation, and breakdowns during change.
3. Define the unit of analysis. Be precise about what counts as “the team.” Is it the top team, a product squad, a functional leadership team, or a recurring cross-functional forum? Many flawed diagnoses come from mixing a formal org chart with the actual working team that carries the task.
4. Construct the framework artifact. Build a simple diagnostic scorecard or heat map with the five behaviors and three coordinating mechanisms as rows. For each row, define observable indicators, such as whether members speak up about risks, confirm decisions, rebalance work, or adapt plans when assumptions change.
5. Analyze and interpret the results. Do not stop at average scores. Look for patterns: strong trust but weak monitoring; strong leadership but weak backup behavior; good intentions but poor shared mental models between functions. Distinguish one-off anecdotes from repeated behavioral patterns.
6. Translate insights into actions. Convert the diagnosis into targeted interventions: meeting redesign, role clarification, escalation rules, coaching, after-action reviews, workload rebalancing, or explicit communication protocols. At this stage, many companies move from diagnosis into a formal team effectiveness program that combines behavioral commitments, leader coaching, and progress reviews.
7. Test sensitivities and alternative assumptions. Recheck the conclusions under different conditions. Are the observed issues specific to one leader, one project phase, remote work, or a recent reorganization? If the answer changes materially when the context changes, the intervention should be more tailored.
8. Align stakeholders and iterate. Socialize the findings with the team, not just the sponsor. Encourage challenge, compare perceptions with observed behavior, and refine the diagnosis. The model is most useful when teams revisit it after several weeks and assess whether the targeted behaviors have actually changed.

6. Example: Salas Big Five of Teamwork in Action

The situation

A $700 million B2B software company had a recurring problem: major product launches were late, sales enablement materials arrived at the last minute, and customer-success teams learned about feature limitations only after client commitments had been made. The executive team initially described the issue as poor alignment between functions.

Why this framework was selected

The issue was not a lack of strategy. The company already knew which products it wanted to launch and which customers it wanted to target. The real question was why a capable cross-functional launch team kept failing at coordinated execution. The Salas model was chosen because it focuses directly on the behaviors that make interdependent teams work.

How the framework was applied

Over two weeks, the team interviewed Product, Engineering, Marketing, Sales, and Customer Success leaders; observed launch meetings; reviewed post-mortems from the previous three releases; and mapped the launch process from code freeze to customer rollout. The team then rated the launch team against the five behaviors and three coordinating mechanisms using concrete examples rather than opinions alone.

The insights

The diagnosis found that trust was reasonably strong and the launch leader was respected, but mutual performance monitoring and backup behavior were weak. Functions reported status, but they did not actively track one another’s downstream risks. Shared mental models were also inconsistent: Engineering defined “ready” as code complete, while Sales defined it as field-ready training and approved messaging. Under pressure, the team adapted reactively rather than deliberately.

The decisions and actions

The company responded by defining launch-readiness criteria, creating a weekly risk review, and clarifying launch decision rights across Product, Engineering, Sales, and Customer Success. It also introduced explicit closed-loop communication in launch meetings and short after-action reviews. Within two quarters, launch delays fell and surprise escalations became less common.

7. Strengths and Limitations

Strengths

• Behaviorally specific: it turns a fuzzy conversation about teamwork into observable behaviors that can be discussed, coached, and improved.
• Research grounded: the model comes from a synthesis of team-performance research rather than from anecdote alone.
• Useful across settings: it applies in executive, project, operational, and safety-critical teams.
• Strong for dynamic work: it is especially good at diagnosing performance under changing conditions, not just in stable routines.
• Actionable: the output naturally points to interventions such as meeting redesign, leader coaching, role clarification, and communication protocols.

Limitations

• It is not a turnkey instrument: despite the name, the original model is a taxonomy, not a universal scored assessment with fixed benchmarks.
• It can underweight structure: team behavior may look weak when the deeper problem is poor organization design, misaligned incentives, or lack of capacity.
• Measurement can be subjective: if teams rely only on self-ratings, the diagnosis can become a reflection of politics or mood.
• It is a snapshot: the model does not by itself explain how a team developed over time or how power dynamics shape behavior.
• Less useful for low-interdependence work: if people mostly work independently, the framework adds limited value.

8. Common Pitfalls and How to Avoid Them

• Treating it as a morale exercise. What goes wrong: the discussion becomes about whether people “feel good” rather than how the team performs. Why it matters: teams may leave with better sentiment but no operational change. How to avoid it: anchor the conversation in real work episodes, decisions, and handoffs.
• Confusing the five with the three enablers. What goes wrong: teams mix behaviors and conditions together and lose diagnostic precision. Why it matters: interventions become vague. How to avoid it: assess the five behaviors directly, then ask whether trust, communication, or shared mental models are enabling or blocking them.
• Using self-ratings alone. What goes wrong: politically skilled teams overrate themselves, while demanding teams underrate themselves. Why it matters: the assessment reflects perception more than performance. How to avoid it: combine survey input with observation and concrete operating evidence.
• Ignoring context and structure. What goes wrong: leaders conclude the team needs better collaboration when the real issue is unclear roles, overloaded managers, or incompatible incentives. Why it matters: the team gets coaching instead of a fix. How to avoid it: test whether the behavior gap persists after you examine role clarity, decision ownership, and workload.
• Equating monitoring with micromanagement. What goes wrong: teams avoid visibility into one another’s work in the name of empowerment. Why it matters: risks surface too late. How to avoid it: define mutual performance monitoring as shared situational awareness and early warning, not intrusive control.
• Stopping at diagnosis. What goes wrong: the framework produces an interesting workshop and then disappears. Why it matters: nothing changes in daily behavior. How to avoid it: translate each finding into routines, owners, and review dates.

9. How Salas Big Five of Teamwork Relates to Other Frameworks

Compared with Tuckman’s stages of team development

Tuckman explains how teams tend to evolve over time—forming, storming, norming, and performing. Salas Big Five explains what effective teamwork looks like behaviorally at any point in that journey. If a team is struggling, Tuckman can help explain where it is developmentally, while Salas helps specify what behaviors need to change now.

Compared with Lencioni’s Five Dysfunctions of a Team

Lencioni is executive-friendly and focuses on common failure modes such as absence of trust and avoidance of accountability. Salas is more behaviorally granular and more directly tied to team-performance research. In practice, Lencioni is often useful for framing the leadership conversation, while Salas is stronger for observation, diagnosis, and intervention design.

Combined with role and decision frameworks

Salas is often strongest when paired with tools that clarify structure. If the diagnosis reveals weak handoffs or slow escalation, role-clarity and decision-rights frameworks help convert behavioral insight into operating changes. A good sequence is to use a basic role framework when the charter is murky, then use Salas to improve how the team actually works together under live conditions.

10. Key Takeaways

• The Salas Big Five of Teamwork is a research-based model for diagnosing how teams coordinate and perform under interdependent work.
• It identifies five core behaviors—leadership, monitoring, backup behavior, adaptability, and team orientation—plus three enabling mechanisms.
• It is most useful for executive, cross-functional, project, and operational teams where coordination failures drive performance problems.
• Its biggest practical value is turning vague concerns about culture or alignment into specific, observable behaviors.
• It works best when supported by real evidence such as meeting observation, handoff examples, and post-mortem data.
• Its biggest caveat is that behavior alone is not the whole story; structure, roles, incentives, and capacity still matter.

11. FAQs About Salas Big Five of Teamwork

Is the Salas Big Five of Teamwork still relevant today?

Yes. The model remains relevant because interdependent work has not disappeared, and hybrid work often makes coordination harder. What has changed is the application: practitioners now look at digital handoffs, asynchronous communication, and distributed decision making as well as live meetings.

Is it the same as the Big Five personality model?

No. The Big Five personality model describes individual personality traits, while the Salas Big Five of Teamwork describes team behaviors and enabling conditions. One helps explain how individuals may differ; the other helps explain how a team performs together.

What is the difference between Salas Big Five and Lencioni’s Five Dysfunctions?

Lencioni focuses on common dysfunctions in leadership teams and is often used as a leadership discussion tool. Salas focuses on observable teamwork behaviors and is more useful when you want a structured diagnosis tied to real operating episodes, handoffs, and adaptation under pressure.

Can small or early-stage companies use it?

Absolutely. A startup or small company does not need a formal survey or large consulting study to use the framework. Founders can apply it in a simple retrospective by asking where leadership, monitoring, backup behavior, adaptability, and team orientation are helping or hurting execution.

How long does it typically take to apply in a real project?

A light-touch team workshop can be done in half a day, but a useful real-world diagnosis usually takes one to three weeks for a single team. The timeline depends on how much observation is needed, how many stakeholders must be interviewed, and whether the work includes intervention design and follow-through.