Life Stages & Communities

Team Dynamics

Team dynamics are the patterns of interaction, roles and relationships that shape how a team works. This guide covers the classic models, what research supports, and how teams can work better together.

On this page
  1. Understanding Team Dynamics
  2. Team Formation Stages
  3. Team Roles
  4. Team Effectiveness
  5. Managing Conflict
  6. Building Cohesion
  7. Diversity in Teams
  8. Virtual Team Dynamics
  9. Putting It Together
  10. Frequently asked questions
  11. Sources

Understanding Team Dynamics

Team dynamics are the psychological and behavioral forces that shape how a team works: its roles, norms, communication patterns, relationships, conflicts and decision-making. They are often invisible, yet they explain why teams with similar talent can perform very differently. Understanding team dynamics helps leaders and members build teams that are effective, resilient and satisfying to work in.

Teams can be more than the sum of their parts, but they can also be less. When people work toward shared goals, social processes emerge that can amplify individual abilities, through shared knowledge and mutual support, or diminish them, through miscommunication, conflict and process losses such as coordination problems and reduced effort. The study of team dynamics draws on social psychology, group dynamics and organizational psychology.

What makes a team?

Not every group is a team. Researchers such as Richard Hackman describe real teams as having a shared purpose that requires collective effort, genuine interdependence among members, clear boundaries about who is and is not a member, some authority to manage their own work, and enough stability to learn to work together.

Types of teams

Work teams

Ongoing teams that produce goods or services, such as manufacturing cells, customer service teams or hospital wards.

Project teams

Temporary teams formed for a specific initiative, such as product development or process improvement, which disband when it ends.

Management teams

Leadership groups, such as executive teams or department heads, that coordinate across units.

Parallel teams

Groups that work alongside the regular structure, such as task forces, quality circles and advisory councils.

Why team dynamics matter

Much organisational work is now done in teams, so the quality of team dynamics affects performance, innovation, learning, engagement and retention. Research also shows that dynamics can be improved: they are not simply a product of who happens to be on the team.

Team Formation Stages

Tuckman's model of team development

In 1965, psychologist Bruce Tuckman reviewed studies of small groups and proposed that teams typically pass through four stages. In 1977, with Mary Ann Jensen, he added a fifth.

  1. Forming. Members get to know each other, are polite and tentative, test boundaries and depend on the leader for direction. Leaders help by providing structure, clarifying purpose and making introductions.
  2. Storming. Differences surface as disagreements about goals, approaches, roles and influence. Frustration with progress is common. Leaders help by normalising conflict, facilitating resolution and keeping it safe to disagree.
  3. Norming. The team agrees how it will work. Roles become clearer, trust grows, a team identity emerges and feedback flows more constructively. Leaders reinforce positive patterns and encourage participation.
  4. Performing. The team focuses on goals, adapts roles flexibly, solves problems effectively and supports members. Leaders delegate, remove obstacles and recognise success.
  5. Adjourning. The team completes its task and disbands. Members may feel accomplishment, sadness and uncertainty. Leaders celebrate achievements, capture lessons and support transitions.

Important caveats

Tuckman's model is memorable and useful, but it was based on a review of mostly therapy and training groups rather than workplace teams. Teams do not always move in a straight line; new members, new tasks or crises can send them back to storming. Some teams move quickly, others get stuck. Connie Gersick's 1988 research on project teams found a different pattern, punctuated equilibrium, in which teams worked in one mode until around the midpoint of their deadline, then made a sudden shift in approach. Virtual and short-lived teams may show different patterns again.

Team Roles

Belbin's team roles

British researcher Meredith Belbin studied management teams in simulation exercises and identified nine roles that people tend to play. Each comes with typical strengths and "allowable weaknesses."

Belbin's nine team roles
RoleTypical strengthsAllowable weaknesses
PlantCreative, imaginative, generates ideasIgnores details; may communicate poorly
Resource InvestigatorOutgoing, explores opportunities, networksOver-optimistic; loses interest quickly
CoordinatorConfident, clarifies goals, delegatesCan be seen as manipulative
ShaperChallenging, dynamic, thrives on pressureCan provoke others
Monitor EvaluatorStrategic, discerning, weighs optionsLacks drive; overly critical
TeamworkerCooperative, diplomatic, listens wellIndecisive in crunch situations
ImplementerDisciplined, reliable, efficientInflexible; slow to respond to change
Completer FinisherPainstaking, conscientious, delivers on timeAnxious; reluctant to delegate
SpecialistDedicated, provides deep expertiseNarrow focus

The model offers a helpful language for discussing contributions, and it highlights that strengths and weaknesses come together. However, independent research on the reliability and validity of Belbin's questionnaire has been mixed, so it is best used as a discussion tool rather than a precise assessment. People commonly play several roles.

Formal and informal roles

Formal roles are officially assigned, such as team leader or subject expert, with defined responsibilities and authority. Informal roles emerge through interaction: the person who eases tension with humour, the peacemaker, the challenger, the one others go to for advice. Informal roles can carry considerable influence without formal authority.

Task and maintenance roles

In a classic 1948 paper, Kenneth Benne and Paul Sheats distinguished task roles, which move work forward (initiating ideas, seeking information, clarifying, summarising, evaluating), from maintenance roles, which sustain relationships (encouraging, harmonising, gatekeeping to ensure everyone participates, setting standards). They also described individual roles, such as dominating or blocking, that serve personal needs at the team's expense. Effective teams need both task and maintenance contributions.

Team Effectiveness

Hackman's conditions for team effectiveness

Harvard psychologist J. Richard Hackman spent decades studying teams, from airline cockpit crews to orchestras. He concluded that leaders cannot directly make a team great, but they can create conditions that make effectiveness more likely:

  • A real team: clear boundaries, interdependent work and reasonably stable membership.
  • Compelling direction: a clear, challenging and consequential purpose, with the ends specified and the means left flexible.
  • Enabling structure: a well-designed task, the right size (Hackman warned that teams larger than about ten often struggle) and mix of skills, and clear norms of conduct.
  • Supportive context: rewards that recognise team performance, access to information, and adequate resources.
  • Expert coaching: help with team process, offered at the right moments, such as the start, midpoint and end of work.

Hackman judged effectiveness on three criteria: whether the team's output meets the standards of those who receive it, whether the team's capability to work together grows over time, and whether the experience contributes to members' learning and wellbeing.

Google's Project Aristotle

Google's internal study of around 180 teams identified five dynamics that mattered most: psychological safety, dependability, structure and clarity, meaning, and impact. Psychological safety was reported as the most important, echoing Amy Edmondson's academic research showing that it enables team learning.

Measuring team performance

Teams can be assessed with quantitative measures, such as productivity, quality, customer satisfaction, deadlines and budgets, and qualitative indicators, such as engagement, communication quality, collaboration, learning and how well conflict is handled. Using both avoids rewarding short-term output at the cost of burnout or poor relationships.

Managing Conflict

Types of team conflict

Researchers, notably Karen Jehn, distinguish three types of conflict:

  • Task conflict: disagreements about the content of work, such as ideas, goals and interpretations.
  • Process conflict: disagreements about how work should be done, such as who does what and when.
  • Relationship conflict: interpersonal friction, dislike and tension.

What research shows

Popular advice often says task conflict is good and relationship conflict is bad. The evidence is more nuanced. A 2003 meta-analysis by Carsten De Dreu and Laurie Weingart found that both task and relationship conflict were, on average, negatively related to team performance and satisfaction. Later work, including a 2012 meta-analysis by de Wit, Greer and Jehn, found that task conflict can be beneficial under certain conditions: when relationship conflict is low, when there is trust and psychological safety, and in decision-making teams at senior levels. Relationship conflict consistently harms performance and wellbeing, and process conflict is usually unhelpful.

The practical lesson is that disagreement about ideas is valuable only when a team can keep it focused on the work and prevent it from becoming personal.

Conflict-handling styles

The Thomas-Kilmann model, developed by Kenneth Thomas and Ralph Kilmann, describes five styles based on assertiveness and cooperativeness:

Thomas-Kilmann conflict styles
StyleApproachWhen it can fit
CompetingAssertive, uncooperative: pursuing your own concernsUrgent decisions; unpopular but necessary actions
CollaboratingAssertive, cooperative: seeking a solution that meets both sides' needsWhen both parties' concerns are too important to compromise
CompromisingModerate on both: splitting the differenceModerately important goals; temporary settlements
AvoidingUnassertive, uncooperative: not addressing the conflictTrivial issues; when emotions need to cool
AccommodatingUnassertive, cooperative: yielding to othersWhen you are wrong or the issue matters more to others

Productive conflict management

Healthy team norms include disagreeing with ideas rather than people, listening to understand, relying on data, raising issues promptly and keeping discussions respectful. Leaders help by normalising disagreement, ensuring all voices are heard, separating people from problems and focusing on what to do next rather than who is to blame. A structured resolution process, drawn from interest-based negotiation, involves acknowledging the conflict, understanding each perspective, identifying underlying interests rather than fixed positions, generating options, evaluating them against agreed criteria, agreeing a plan and following up. See conflict resolution.

Building Cohesion

What is team cohesion?

Cohesion is the degree to which members are bonded to the team and motivated to stay part of it. Researchers distinguish task cohesion, a shared commitment to the team's goals, from social cohesion, members' liking for one another and enjoyment of being together.

Cohesion and performance

A 1994 meta-analysis by Brian Mullen and Carolyn Copper found a reliable, modest link between cohesion and performance, driven mainly by commitment to the task rather than interpersonal attraction. They also found that performance influences cohesion: success brings teams together. Cohesion is linked to better communication, satisfaction, effort, resilience and lower turnover.

Potential downsides

Highly cohesive teams can suffer from groupthink, Irving Janis's term for the pressure to agree that suppresses dissent and leads to poor decisions. Strong in-group loyalty can also create "us versus them" tension with other teams (see in-group bias), make it hard for newcomers to join, and breed resistance to change. In addition, groups are vulnerable to social loafing, reduced individual effort when contributions are not identifiable, demonstrated by Bibb Latané and colleagues in 1979.

Building healthy cohesion

Teams build cohesion through shared experiences, such as working through challenges together and marking successes; a clear identity built on shared purpose and norms; genuine interdependence, with shared goals, complementary skills and collective accountability; and a positive climate of respect, recognition and psychological safety. Building in dissent, for example by assigning a devil's advocate, helps prevent cohesion from turning into conformity.

Diversity in Teams

Types of diversity

Surface-level diversity refers to visible or demographic differences, such as age, gender, ethnicity and disability. Deep-level diversity refers to underlying differences in values, personality, knowledge, skills and working styles. Research suggests deep-level differences become more important over time as members get to know each other.

Benefits and challenges

Diverse teams bring a wider range of knowledge and perspectives, which can improve problem-solving, creativity and decisions, and reduce groupthink. However, meta-analyses show that the effects of diversity on performance are mixed on average: diversity can also slow trust-building, create communication barriers and lead to subgroups or "faultlines" when several differences line up. Whether diversity helps depends heavily on team processes, leadership and an inclusive climate.

Leveraging diversity

Teams get more from diversity when they actively seek and value all contributions, ensure equal participation, challenge bias and stereotypes, share working-style preferences, use structured decision-making and facilitate discussion carefully. Psychological safety appears especially important for diverse teams to benefit from their differences. See prejudice and discrimination.

Virtual Team Dynamics

Unique challenges

Remote and hybrid teams face reduced non-verbal cues, technology barriers, time zone differences and fewer spontaneous conversations, which increase the risk of misunderstandings. Trust is harder to build without face-to-face contact, delayed replies can be misread, and members may feel isolated or "out of sight, out of mind." Coordination can suffer from information silos and unclear responsibilities. See remote work and mental health.

Best practices for virtual teams

Effective virtual teams tend to over-communicate context, use video for important or sensitive discussions, document decisions in writing, agree norms for response times, and hold regular check-ins. They deliberately build relationships through informal video chats, personal check-ins at the start of meetings and in-person gatherings when possible. Clear roles, defined workflows and shared tools reduce confusion. Trust grows from consistently delivering on commitments, being responsive and sharing information openly.

Putting It Together

Team dynamics are complex but not mysterious. Teams tend to develop through recognisable phases, though not always in order. They benefit from a mix of task and relationship contributions, from clear direction and structure, and from a climate where people can disagree about ideas without damaging relationships. Cohesion helps when it centres on the shared task and stays open to dissent. Diversity and remote working add both opportunity and challenge, and both depend on inclusive, deliberate processes.

In practice, the most useful steps are to invest time early in clarifying purpose, roles and norms; to create space for healthy debate; to build trust and psychological safety; and to review regularly how the team is working, not just what it is producing.

Frequently asked questions

What are the five stages of team development?

Bruce Tuckman proposed four stages in 1965: forming, when members get oriented; storming, when conflict over roles and approaches emerges; norming, when the team agrees ways of working; and performing, when it works effectively. In 1977 Tuckman and Mary Ann Jensen added adjourning, when the team completes its work and disbands. The stages are a helpful guide, though teams often revisit earlier stages.

What is the difference between a group and a team?

A group is any set of people who interact or share an identity. A team is a particular kind of group whose members share a common goal, depend on each other's work, are clearly bounded and are jointly accountable for results. A committee that meets occasionally may be a group; a surgical team that must coordinate closely to succeed is a team.

Are Belbin team roles scientifically valid?

Belbin's nine roles are widely used in organisations and many people find them a helpful language for discussing team contributions. However, independent research on the questionnaire's reliability and validity has been mixed, and evidence that role-balanced teams consistently outperform others is limited. They are best treated as a conversation tool rather than a precise scientific measure.

What makes a team high-performing?

Research points to several common ingredients: a clear and meaningful shared goal, real interdependence, the right mix of skills, clear roles and norms, psychological safety, dependable members, enough resources and support, and leaders who coach rather than micromanage. Google's Project Aristotle and Hackman's research both emphasise how a team works together over who is on it.

What is social loafing?

Social loafing is the tendency for people to put in less effort when working in a group than when working alone, especially when individual contributions are hard to identify. It was demonstrated by Bibb Latané and colleagues in 1979 using clapping and shouting tasks. Making contributions visible, keeping teams small and giving people meaningful, distinct roles reduce it.

Sources

  1. Tuckman, B. W. (1965). Developmental sequence in small groups. Psychological Bulletin, 63(6), 384–399.
  2. Tuckman, B. W., & Jensen, M. A. C. (1977). Stages of small-group development revisited. Group & Organization Studies, 2(4), 419–427.
  3. Hackman, J. R. (2002). Leading Teams: Setting the Stage for Great Performances. Harvard Business School Press.
  4. De Dreu, C. K. W., & Weingart, L. R. (2003). Task versus relationship conflict, team performance, and team member satisfaction: A meta-analysis. Journal of Applied Psychology, 88(4), 741–749.
  5. Mullen, B., & Copper, C. (1994). The relation between group cohesiveness and performance: An integration. Psychological Bulletin, 115(2), 210–227.
  6. Latané, B., Williams, K., & Harkins, S. (1979). Many hands make light the work: The causes and consequences of social loafing. Journal of Personality and Social Psychology, 37(6), 822–832.
  7. Benne, K. D., & Sheats, P. (1948). Functional roles of group members. Journal of Social Issues, 4(2), 41–49.
  8. Edmondson, A. (1999). Psychological safety and learning behavior in work teams. Administrative Science Quarterly, 44(2), 350–383.

About this page. Written and reviewed by the iPsychology Editorial Team using peer-reviewed research, textbooks and guidance from bodies such as the APA, NIMH, NHS and WHO. Content is educational and is not a substitute for professional advice. Spotted an error? Let us know.