Learning objectives

After completing this unit, you will be able to:

Explain team development stages and the shifting leadership role across them.
Define psychological safety and describe its impact on team learning and performance.
Analyze the diversity paradox and the role of inclusion in activating diverse teams.
Propose leadership practices for building trust and effectiveness in virtual and distributed teams.

Effective teams

Characteristics

According to Hill (2003), an effective team does not only involve team performance, but is characterized by three criteria:

The team performs: the output meets the standards of those who have to use it
The team members are satisfied and learn (i.e., the team experience contributes to each member’s personal well-being and development)
The team adapts and learns (i.e., the team experience enhances the capability of members to work and learn together in the future)

These criteria remind us that short-term results alone do not define a successful team, but that sustainability and growth matter equally.

Team paradoxes

Just as organizations face paradoxes (Unit 3), so do teams. Committed leaders need to be aware of at least four contradictory forces in team work and deal with these paradoxes (Hill, 2003):

Embrace individual differences ⭤ Embrace collective identity and goals
Foster support ⭤ Foster confrontation
Focus on performance ⭤ Focus on learning and development
Rely on managerial authority ⭤ Rely on team members’ discretion and autonomy

Navigating these paradoxes requires behavioral complexity — the ability to move across the CVF quadrants depending on what the team needs at a given moment.

Remember the competing values framework from Unit 3: effective team leadership requires moving fluidly between collaborate (building trust and belonging), create (encouraging experimentation), compete (driving results), and control (establishing clear processes). No single quadrant suffices for the complex demands of team leadership.

Team development

Tuckman’s stage model

Tuckman (1965) proposed that teams progress through predictable stages:

Forming: Team members come together, get acquainted, and explore boundaries. Characterized by politeness, uncertainty, and dependence on the leader for direction. Members are testing the waters — “Will I be accepted? What are the rules?”
Storming: Conflict emerges as members assert individual perspectives, challenge authority, and compete for influence. This is the most uncomfortable but also the most critical stage — teams that avoid or suppress storming often fail to develop the trust and candor needed for high performance.
Norming: The team develops shared norms, roles, and ways of working. Cohesion increases, and members begin to value the group’s goals over individual agendas. A sense of “we” emerges.
Performing: The team functions at a high level — members are interdependent, flexible, and focused on shared goals. Conflict is managed constructively, and the team can handle complex tasks with minimal supervision.
Adjourning: The team disbands after completing its task. This stage was added by Tuckman & Jensen (1977) and involves reflection, celebration, and sometimes grief over the end of meaningful working relationships.

While intuitively appealing, the model has limitations: it implies a linear progression that many teams do not follow. Teams can regress to earlier stages when facing new challenges, membership changes, or external shocks.

Wheelan’s Integrated Model of Group Development

The Integrated Model of Group Development (IMGD) (Wheelan, 2005) provides an empirically grounded refinement of Tuckman’s stages:

Stage	Focus	Key behaviors
(1) Dependency & inclusion	Will I belong?	Members look to the leader for direction; communication is tentative; conflict is avoided
(2) Counterdependency & fight	Who has influence?	Members challenge the leader and each other; subgroups form; conflict over values and procedures
(3) Trust & structure	How do we work together?	Mature negotiation of roles, norms, and goals; increased trust and open communication
(4) Work & productivity	Let’s get it done.	High task focus; effective collaboration; flexible role allocation; constructive conflict

Table 1: Stages of group development as proposed by the IMGD (Wheelan, 2005)

The model adds several important nuances to Tuckman (1965):

Teams don’t progress linearly: they can regress to earlier stages when facing membership changes, new tasks, or external pressures. A Stage 4 team that loses a key member may temporarily return to Stage 2 dynamics.
Most teams never reach stage 4: Wheelan (2005)’s research suggests that many organizational teams remain stuck in Stages 1 or 2, never developing the trust and structure needed for true high performance.
Time matters: teams need sufficient time together to develop. Short-lived project teams or teams with frequent membership changes face inherent developmental challenges.
The leader’s role shifts across stages: in Stage 1, members need more direction and structure. In Stage 2, the leader must manage conflict without suppressing it. In Stage 3, the leader can increasingly delegate. In Stage 4, the leader serves primarily as a boundary manager and resource provider.

The leader’s role across stages

The leader’s approach must adapt as the team develops:

Team stage	Leadership approach	Key actions
Dependency & inclusion	Directive	Provide clear structure, establish safety, model expected behavior
Counterdependency & fight	Coaching	Normalize conflict, facilitate dialogue, protect minority voices
Trust & structure	Supporting	Encourage self-management, support emerging norms, delegate decisions
Work & productivity	Delegating	Manage boundaries, secure resources, remove obstacles

Table 2: The leader’s role across stages

Notice how this maps onto the situational leadership model from Unit 3 (Hersey & Blanchard, 1977): as the team matures, the leader gradually shifts from high-task/high-relationship behavior to low-task/low-relationship behavior. The leader does not become less important — but the nature of the leadership contribution changes from providing answers to creating conditions.

This is also an example of adaptive leadership in action: in early team stages, many challenges are technical (establishing roles, processes, and norms). As the team matures, challenges become more adaptive (navigating interpersonal tensions, developing shared mental models, balancing competing priorities).

Psychological safety

Definition

Psychological safety is a shared belief held by members of a team that the team is safe for interpersonal risk-taking (A. Edmondson, 1999).

A. Edmondson (1999) showed that psychological safety enables learning behavior in teams — asking questions, admitting mistakes, seeking feedback, experimenting — which in turn drives team performance.

The research by A. Edmondson (1999) began with a puzzling finding: the best-performing hospital nursing teams reported more errors, not fewer. It turned out that these teams had higher psychological safety, which meant members felt safe to report and discuss errors — leading to more learning and ultimately fewer repeated mistakes. Teams with low psychological safety underreported errors, creating an illusion of competence while actually performing worse.

The key insight: psychological safety is not about being nice or avoiding conflict. It is about creating an environment where people feel safe to be candid — to disagree, to point out problems, to ask “stupid” questions, and to admit “I don’t know.” This candor is the foundation of team learning.

The research evidence

Psychological safety leads to Learning behavior leads to team performance

Key findings from research (A. Edmondson, 1999):

Teams with higher psychological safety engage in more learning behaviors (seeking feedback, discussing errors, experimenting)
Learning behavior mediates the relationship between psychological safety and team performance
Psychological safety is a group-level phenomenon. It is a shared perception, not an individual trait
Leader behavior is the strongest predictor of team psychological safety

Project Aristotle

Google’s Project Aristotle¹ confirmed and extended these findings (Google re:Work, 2015):

Psychological safety was the #1 predictor of team effectiveness at Google, more important than team composition, structure, or individual talent.

The five key dynamics of effective teams (in order of importance):

Psychological safety — Can we take risks without feeling insecure or embarrassed?
Dependability — Can we count on each other to do high-quality work on time?
Structure & clarity — Are goals, roles, and plans clear?
Meaning — Is the work personally important to us?
Impact — Do we believe our work matters?

Project Aristotle studied 180+ teams at Google over two years. The researchers initially expected to find that team composition (e.g., having the right mix of skills or personalities) would be the key factor. Instead, they found that how teams worked together mattered far more than who was on the team.

This finding reinforces a key message from our course: leadership is not just about selecting the right people (traits, Unit 2) — it is fundamentally about creating the right conditions for those people to work effectively together.

Creating psychological safety

A. C. Edmondson (2018) proposed three categories of action in her “Leader Tool Kit”:

Setting the Stage creates the rationale for speaking up.
Inviting Participation creates the opportunity to speak up.
Responding Productively creates the orientation for continued speaking up.

According to A. C. Edmondson (2018), psychological safety is not about being “nice” or lowering performance standards; it is about increasing candor to enable learning.

These three steps create a reinforcing loop:

Setting the Stage: Frame failure as learning: define the work as a “learning problem” rather than an “execution problem.” Treat setbacks as data for improvement, asking “What can we learn?” instead of “Who is responsible?”
Inviting Participation: Model vulnerability: acknowledge your own mistakes and uncertainties. When a leader says “I don’t know” or “I was wrong,” it creates “safety in fallibility.”
Invite input actively use proactive inquiry. Don’t just leave the door open; actively solicit perspectives from everyone, especially quieter members, with specific, open-ended questions.
Responding Productively: Replace blame with curiosity: when concerns are raised, respond with appreciation and interest. How you handle the first person who speaks up determines the team’s future silence or transparency.

A single punitive response to a mistake (a “failure of responding productively”) can destroy months of trust-building work.

Note the connection to engaging leadership (Unit 4): facilitating (autonomy), connecting (relatedness), and strengthening (competence) all contribute to psychological safety. A disengaging leader who uses coercive, eroding, or isolating behaviors will systematically destroy it.

Psychological safety ≠ comfort zone

Psychological safety is not about lowering standards or avoiding disagreement.

	Low accountability	High accountability
High psychological safety	Comfort zone — people feel safe but aren’t challenged	Learning zone — people feel safe AND are held to high standards
Low psychological safety	Apathy zone — people don’t care and aren’t pushed	Anxiety zone — people are stressed and afraid to take risks

Table 3: The 2×2 framework of psychological safety (A. Edmondson, 1999)

The goal is the learning zone: high psychological safety combined with high accountability and high performance standards.

This distinction is critical because psychological safety is sometimes misunderstood as “being nice” or “avoiding difficult feedback.” In fact, the most effective teams combine psychological safety with rigorous standards — people feel safe to be candid because the team cares about quality, not despite it.

This connects to the team paradoxes we discussed earlier: foster support ⭤ foster confrontation. Psychological safety is what makes it possible to hold this paradox — to support people as human beings while confronting them about their work.

Diversity & inclusion

Diversity x team performance

Cognitive diversity is a powerful resource for team problem-solving and innovation.

Page (2007) argues that diversity is a collection of tools (heuristics, perspectives, interpretive frameworks). He proves that a group of diverse “average” problem-solvers often outperforms a group of “top-tier” identical experts because the experts get stuck on the same hurdles.

Demographic diversity serves as a vital proxy for cognitive diversity; varied life experiences and social identities provide the unique “raw materials” that expand a team’s collective intelligence.

Consequently, two forms of diversity can be distinguished as they have different mechanisms:

Cognitive diversity directly enriches the team’s information pool and problem-solving capacity. When team members bring different mental models (recall Unit 1), the team can see problems from multiple angles — like the blind men who together can describe the whole elephant.
Demographic diversity does not automatically produce cognitive diversity, but it often correlates with different life experiences, professional networks, and cultural perspectives that expand the team’s collective intelligence.

Diversity is a resource — but it is a resource that requires active management to realize its potential.

Component	Definition	Role in Problem-Solving
Perspectives	Internal representations of the world or “problem space.”	Helps the team identify multiple possible solutions instead of just one.
Heuristics	Rules of thumb or specific techniques for finding solutions.	Provides different shortcuts or “how-to” methods to bypass obstacles.
Interpretations	Mental categories used to group or classify information.	Changes how the team frames the problem (e.g., technical vs. social).
Predictive Models	Causal “if/then” maps used to anticipate outcomes.	Allows the team to forecast consequences from various vantage points.

Table 4: The Diversity Toolbox (Page, 2007)

The diversity paradox

Diverse teams have higher potential
and higher process loss.

Diversity increases the range of perspectives, knowledge, and ideas available to the team, but it also increases the potential for misunderstanding, conflict, and coordination challenges (Stahl et al., 2010).

Diverse teams are better at generating creative solutions and avoiding groupthink
But they can also experience more communication breakdowns, slower decision-making, and stronger in-group/out-group dynamics
Knippenberg et al. (2004) shows that inclusion (i.e., avoiding “social categorization”) is the mechanism that allows teams to elaborate on their differences rather than clashing over them

The diversity paradox means that simply assembling a diverse team is not enough — and can even backfire if the team lacks inclusive practices. Without psychological safety and active inclusion, diverse team members may self-censor, disengage, or experience identity threat. The result: the team bears the coordination costs of diversity without reaping its cognitive benefits.

This is why psychological safety (the previous section) is a prerequisite for diversity to work: only when people feel safe to bring their full perspectives will cognitive diversity translate into better outcomes.

Inclusion

Inclusion is the set of leadership practices that activate the latent potential of a diverse team. Leaders bridge the gap between “having a seat at the table” and “having a voice that carries weight” through:

Voice Equity: mitigating “dominance hierarchies” to ensure participation is distributed, regardless of status or seniority (A. C. Edmondson, 2018).
Perspective-raking: the cognitive process of stepping into another’s shoes, which reduces bias and improves “information elaboration” (Galinsky et al., 2008).
Belonging Cues: high-frequency social signals that create a “safe connection,” signaling that the individual is a vital part of the future of the group (Coyle, 2018).
Constructive Dissent Norms: institutionalizing “task conflict” while minimizing “relationship conflict” to surface unique perspectives (Jehn, 1995).

Inclusion connects directly to the Categorization-Elaboration Model (Knippenberg et al., 2004). This model posits that diversity only works if the team “elaborates” (shares and processes) information. Without Belonging Cues and Voice Equity, “social categorization” occurs—where people see each other as “us vs. them”—which causes members to withhold their unique knowledge to avoid being seen as “different.”

For leaders, this means that building a diverse team is only the first step. The harder, ongoing work is creating the conditions where diverse perspectives are genuinely heard, valued, and integrated into team decisions.

Virtual teams

Challenges of distance

Distance is not just a geographical gap; it is a “functional barrier” that forces a shift from organic interaction to intentional leadership.

Reduced Social Context: the lack of “media richness” (nonverbal cues/tone) increases the risk of misinterpretation and attribution bias (Daft & Lengel, 1986).
Fragility of “Swift Trust”: distance shifts trust from interpersonal (affect-based) to task-based (reliability), making it harder to sustain over time (Jarvenpaa & Leidner, 1999).
Coordination Complexity: distance creates “structural holes” (gaps in the flow of information) that prevent the team from picking up social cues organically. This forces a shift from implicit coordination (natural alignment) to explicit coordination (intentional, documented protocols) to bridge the gap (Hinds & Mortensen, 2005).
Social Loafing & Isolation: physical distance can lead to “psychological distance,” where team members feel less accountable and more disconnected from the collective identity (Golden et al., 2008).

These challenges are not merely inconveniences — they fundamentally affect team development dynamics. Virtual teams often struggle to move through the developmental stages (Wheelan, 2005) because the storming and norming processes that build trust and shared norms are harder to facilitate at a distance. Psychological safety is also more difficult to establish because leaders cannot easily read the room or notice when someone is disengaging.

This is where “digital leadership” (from Unit 1) becomes concrete: leading in the digital age increasingly means leading people you rarely or never see face-to-face.

Swift trust

Meyerson et al. (1996) introduced the concept of swift trust for temporary or virtual teams:

In the absence of time to build traditional trust through repeated interactions, team members make an initial decision to act as if trust exists — based on role expectations, professional reputation, and institutional cues.

Swift trust is fragile: it must be confirmed through early interactions and consistent follow-through. A single violation can shatter it entirely.

Swift trust helps explain why some virtual teams perform well from the start while others struggle. Teams that begin with clear role expectations, professional introductions that establish credibility, and early quick wins tend to develop and maintain swift trust. Teams that begin with ambiguity, missed deadlines, or unanswered messages quickly lose whatever initial trust existed.

For leaders, the implication is clear: the first interactions in a virtual team are disproportionately important. Invest heavily in structured kick-offs, explicit norm-setting, and early deliverables that build confidence.

Leading virtual teams

Practical leadership practices for virtual teams:

Structured communication rhythms — establish regular check-ins, stand-ups, and retrospectives that create predictability and connection
Explicit norms — make implicit expectations explicit (response time expectations, camera-on/off policies, decision-making processes) since unspoken norms cannot be absorbed through osmosis at a distance
Intentional relationship building — create deliberate space for non-task interaction (virtual coffee chats, personal check-ins) that replaces the coffee-machine conversations lost in virtual settings
Technology choices with purpose — match the communication tool to the message type (quick questions in chat; complex discussions per video; documentation in shared documents only) rather than defaulting to the easiest option

Leading virtual teams requires more deliberate, structured leadership than leading co-located teams. What happens naturally in a shared office — relationship building, norm absorption, conflict resolution through informal conversation — must be intentionally designed in virtual settings.

This is also where the latticework of mental models pays off practically. Understanding team development stages helps you diagnose why a virtual team is struggling. Understanding psychological safety helps you design virtual meeting practices that invite voice. Understanding SDT (Unit 4) helps you create autonomy without losing connection. The models compound.

Latticework update

New models added to your latticework:

Stages of group development (team as evolving system)
Psychological safety as team learning enabler
Complex adaptive systems — teams as emergent phenomena

Homework

Reflect on a conflict you have observed in a team or organization:

What were the sources of the conflict (structural, interpersonal, resource-based)?
Was the conflict functional (productive) or dysfunctional (destructive)?
How was it managed — and what would you have done differently?

Literature

Coyle, D. (2018). The culture code: The secrets of highly successful groups. Bantam.

Daft, R. L., & Lengel, R. H. (1986). Organizational information requirements, media richness and structural design. Management Science, 32(5), 554–571.

Edmondson, A. (1999). Psychological safety and learning behavior in work teams. Administrative Science Quarterly, 44(2), 350–383.

Edmondson, A. C. (2018). The fearless organization: Creating psychological safety in the workplace for learning, innovation, and growth. John Wiley & Sons.

Galinsky, A. D., Maddux, W. W., Gilin, D., & White, J. B. (2008). Why it pays to get inside the head of your opponent: The differential effects of perspective taking and empathy in negotiations. Psychological Science, 19(4), 378–384.

Golden, T. D., Veiga, J. F., & Dino, R. N. (2008). The impact of professional isolation on teleworker job performance and turnover intentions: Does time spent teleworking, face-to-face interactions, and social support matter? Journal of Applied Psychology, 93(6), 1412–1421.

Google re:Work. (2015). Guide: Understand team effectiveness. https://rework.withgoogle.com/guides/understanding-team-effectiveness/

Hersey, P., & Blanchard, K. H. (1977). Management of organizational behavior: Utilizing human resources (3rd ed.). Prentice-Hall.

Hill, L. A. (2003). Becoming a manager: How new managers master the challenges of leadership. Harvard Business Press.

Hinds, P. J., & Mortensen, M. (2005). Understanding conflict in geographically distributed teams: The moderating effects of shared identity and shared context. Organization Science, 16(3), 290–307.

Jarvenpaa, S. L., & Leidner, D. E. (1999). Communication and trust in global virtual teams. Organization Science, 10(6), 791–815.

Jehn, K. A. (1995). A multimethod examination of the nature, causes, and effects of task and relationship conflict. Administrative Science Quarterly, 40(2), 256–282.

Knippenberg, D. van, De Dreu, C. K. W., & Homan, A. C. (2004). Work group diversity and group performance: An integrative model and research agenda. Journal of Applied Psychology, 89(6), 1008–1022.

Meyerson, D., Weick, K. E., & Kramer, R. M. (1996). Swift trust and temporary groups. In Trust in organizations: Frontiers of theory and research (pp. 166–195). Sage Publications.

Page, S. E. (2007). The difference: How the power of diversity creates better groups, firms, schools, and societies. Princeton University Press.

Stahl, G. K., Maznevski, M. L., Voigt, A., & Jonsen, K. (2010). Unraveling the effects of cultural diversity in teams: A meta-analysis. Journal of International Business Studies, 41, 690–709.

Tuckman, B. W. (1965). Developmental sequence in small groups. Psychological Bulletin, 63(6), 384–399.

Tuckman, B. W., & Jensen, M. A. C. (1977). Stages of small-group development revisited. Group & Organization Studies, 2(4), 419–427.

Wheelan, S. A. (2005). Group processes: A developmental perspective (2nd ed.). Allyn & Bacon.

Footnotes

Google’s Project Aristotle refers to a large-scale internal study of team effectiveness↩︎