Groups and teams

Most work today is done in groups. Products are designed by cross-functional teams, patients are treated by care teams, construction projects are coordinated by site teams, and software is built by squads that may span several countries. Teams can achieve things no individual could, but they can also waste time, suppress good ideas and frustrate their members. This lesson explains how groups develop, what shapes their behavior, why bigger is not always better and what the evidence says about building effective teams. Running meetings and team communication are covered in BUS-120; here the focus is on how groups and teams work as social systems.

Groups and teams

A group is two or more individuals who interact and depend on each other to achieve particular objectives. Formal groups are defined by the organization's structure, such as a department or project team. Informal groups form naturally in response to social needs, such as colleagues who lunch together; they can strongly shape norms and information flow. A team is a special kind of group whose members work intensely together toward a common goal, with mutual accountability and complementary skills, so that the collective result is greater than the sum of individual inputs. A work group shares information to help each member perform individually; a team produces a joint product.

Organizations use several types of team. Problem-solving teams of employees from the same department meet to improve quality, efficiency or the work environment. Self-managed teams take on many supervisory responsibilities, such as scheduling, assigning tasks and choosing methods. Cross-functional teams bring together people from different areas to complete a task such as launching a product. Virtual teams use technology to connect members in different locations. Multiteam systems are networks of teams, such as the police, fire, paramedic and hospital teams responding to a highway crash, whose goals depend on each other.

How groups develop

Bruce Tuckman's five-stage model, proposed in 1965 and extended in 1977, remains the most widely used description of group development. In forming, members are polite and uncertain, testing what behavior is acceptable and looking to a leader for direction. In storming, conflict emerges over goals, roles and leadership as members assert their views. In norming, the group develops close relationships, shared expectations and a sense of identity. In performing, the structure is accepted and energy goes into the task. In adjourning, temporary groups wrap up and disband, which can bring both satisfaction and a sense of loss.

Real groups do not always follow the stages neatly; they may return to storming when a new member joins or the goal changes. Connie Gersick's research on project teams with deadlines found a different pattern, called punctuated equilibrium. Teams set a direction in their first meeting and stick with it through a first phase of relative inertia. At about the midpoint of their allotted time, they experience a transition, a burst of change in which they drop old patterns and adopt new perspectives, followed by a second phase of execution and a final burst of activity before the deadline. The practical lesson is that the midpoint of a project is a natural moment to step back and reassess.

Roles, norms and status

A role is a set of expected behaviors attributed to someone occupying a given position. Team members play task roles, which move the work forward (initiating, information seeking, summarizing), maintenance roles, which keep relationships healthy (encouraging, harmonizing, gatekeeping so quieter members can speak), and sometimes self-oriented roles that hurt the group (dominating, blocking, seeking recognition). Role ambiguity, uncertainty about what is expected, and role conflict, incompatible expectations, are sources of stress. Tools such as Belbin's team roles are popular for discussion, though like other typologies their predictive evidence is limited.

Norms are acceptable standards of behavior shared by group members. They cover performance (how hard to work, how fast to respond to messages), appearance, social arrangements and resource allocation. The Hawthorne studies at Western Electric in the 1920s and 1930s, though flawed by modern standards, drew attention to how informal group norms regulate output: workers in the bank wiring room kept production at a level the group agreed was fair and pressured "rate-busters" to slow down. Solomon Asch's experiments in the 1950s showed the power of conformity: when a group of confederates unanimously gave an obviously wrong answer about line lengths, about three-quarters of participants conformed at least once. A single dissenter sharply reduced conformity, which shows the value of encouraging even one person to speak up.

Status is a socially defined position or rank given to groups or group members. High-status members often talk more, are interrupted less and have more influence over decisions, whether or not they have the most relevant knowledge. Teams perform better when influence follows expertise rather than status, which leaders can encourage by asking for input from junior members first and explicitly inviting dissent.

Group size and social loafing

Bigger groups bring more resources, skills and perspectives, but they are harder to coordinate. Communication channels grow much faster than group size. In a group of \(n\) members, the number of possible one-to-one channels is:

# Possible one-to-one communication channels as a team grows
for n in [3, 5, 7, 9, 12, 15, 20]:
    channels = n * (n - 1) // 2
    print(f"team of {n:2d}: {channels:3d} channels")

team of  3:   3 channels
team of  5:  10 channels
team of  7:  21 channels
team of  9:  36 channels
team of 12:  66 channels
team of 15: 105 channels
team of 20: 190 channels

A team of 5 has 10 channels; a team of 15 has 105. This is one reason many organizations keep teams small. Amazon popularized the "two-pizza team", a team small enough to be fed by two pizzas, and research on team effectiveness generally suggests that teams of about five to nine people balance resources and coordination well for most tasks.

Social loafing is the tendency for individuals to put in less effort when working collectively than when working alone. In the 1880s, the French agricultural engineer Max Ringelmann found that people pulling on a rope in groups exerted less force per person as group size increased. Later research separated two causes: coordination losses (people do not pull at the same moment) and motivation losses (people reduce effort when their individual contribution cannot be identified). Social loafing is stronger in individualistic cultures, on boring tasks and when people believe others are slacking.

Cohesiveness

Cohesiveness is the degree to which members are attracted to each other and motivated to stay in the group. Cohesive groups communicate more, cooperate more and are more satisfying to belong to. But cohesiveness amplifies norms rather than guaranteeing performance. A cohesive group with high performance norms is very productive; a cohesive group with low performance norms is very good at restricting output. Cohesiveness also increases the risk of groupthink, discussed in lesson 8. Cohesion grows with time together, shared success, smaller size, clear goals and, often, a shared external challenge.

What makes teams effective

Research on team effectiveness points to three clusters of factors. Context includes adequate resources, effective leadership and structure, a climate of trust and a performance evaluation and reward system that recognizes team contributions, not only individual ones. Composition includes members' abilities and personalities, the allocation of roles, diversity, size and members' preference for teamwork. Process includes a common purpose, specific team goals, team efficacy (members' confidence that the team can succeed), a shared mental model of how the work gets done, a manageable level of conflict (lesson 11) and low social loafing.

Psychological safety, a concept developed by Amy Edmondson, is a shared belief that the team is safe for interpersonal risk-taking: that members will not be embarrassed, rejected or punished for speaking up with ideas, questions, concerns or mistakes. Edmondson's early research in hospitals found, surprisingly, that better-led nursing units reported more errors, because people felt safe reporting them, not because they made more. Google's Project Aristotle, reported in 2015, studied about 180 internal teams and concluded that psychological safety was the most important factor distinguishing effective teams, followed by dependability, structure and clarity, meaning and impact. HSE-109 covers psychological safety as part of psychological health and safety; at the team level, leaders build it by framing work as learning, acknowledging their own fallibility and responding to bad news with appreciation rather than blame.

Diversity in teams

Diverse teams can make better decisions because members bring different information, perspectives and networks, but diversity can also increase conflict and reduce cohesion, especially early on. Research distinguishes informational diversity, differences in knowledge and expertise, which tends to help complex, non-routine tasks, from demographic differences that create faultlines, hypothetical dividing lines that split a group into subgroups, such as when all the engineers are young men in one office and all the marketers are older women in another. Strong faultlines can produce us-versus-them dynamics. Leaders reduce these risks by emphasizing a shared goal and identity, mixing subgroups in tasks and creating an inclusive climate where every perspective is sought.

Virtual and hybrid teams

Virtual and hybrid teams face distinctive challenges: fewer informal interactions, slower trust-building, time-zone coordination, misread tone in written messages and the risk that remote members are left out of decisions made by those in the office, sometimes called proximity bias. Effective virtual teams establish clear norms for responsiveness and channels, overlap hours deliberately, document decisions, rotate meeting times fairly across time zones, invest in occasional in-person time for relationship-building and make sure contributions are judged by output rather than visibility. Trust in virtual teams often starts as swift trust, a presumption of reliability that must then be confirmed by early, visible follow-through.