Tuckman's Stages of Group Development: Forming, Storming, Norming, Performing

Tuckman's stages of group development is a model that has been on every team-leadership syllabus for over fifty years. It earns its place there because it names the thing most teams feel but can't articulate: the awkward, frustrating middle where conflict erupts before cohesion arrives. Understanding that middle changes how you lead through it.

What are Tuckman's stages of group development?

Tuckman's stages of group development is a five-stage model that describes how teams form, struggle, stabilize, and eventually reach peak performance. Psychologist Bruce W. Tuckman first published the framework in 1965 in his paper "Developmental Sequence in Small Groups" in the Psychological Bulletin. That paper synthesized findings from 50-plus studies on small-group behavior and proposed four stages: Forming, Storming, Norming, and Performing.

In 1977, Tuckman and Mary Ann Jensen revisited the model in Group and Organization Studies and added a fifth stage: Adjourning, which captures what happens when a team's work is done and the group disbands. The model is sometimes called the Tuckman-Jensen model in recognition of that revision.

The enduring appeal of the framework isn't just its simplicity. It's the honesty embedded in Stage 2. Storming isn't a sign of failure. It's a developmental requirement.

Key Facts

Key Facts

• Tuckman, B.W. (1965), Psychological Bulletin — the original four-stage model synthesized findings from a review of 50-plus small-group studies, including therapy groups, T-groups, and natural groups.
• Tuckman, B.W. and Jensen, M.A.C. (1977), Group and Organization Studies — added the fifth stage 'Adjourning' after reviewing 22 additional studies published post-1965.
• Gallup's State of the Global Workplace 2024 report found that only 23% of employees worldwide are actively engaged at work, with new and misaligned teams identified as a primary driver of disengagement, costing the global economy an estimated $8.9 trillion.

The 5 stages explained

Tuckman's stages don't describe what a team does. They describe what a team experiences. The difference matters. A leader who reads behavior through this lens stops reacting to Storming as a personal problem and starts responding to it as a developmental phase.

Stage 1: Forming

Forming is the orientation phase. Members meet, scope the work, and figure out who's who. Politeness dominates because no one has taken a real position yet. Conflict avoidance is high, and dependency on the leader is highest at this stage. People look to whoever is in charge to define purpose, structure, and expectations.

The trap here is mistaking the calm for cohesion. It isn't. It's caution.

Typical signs of Forming:

• High reliance on the leader for direction
• Overly polite or cautious conversations
• Questions about roles, scope, and goals
• Low productivity (people are still orienting)
• Excitement mixed with anxiety about what comes next

Leader behavior: Directive. Clarify the mission, set expectations, establish roles. This is not the moment to be hands-off. Teams that don't get clear structure in Forming spend extra time in Storming.

Stage 2: Storming

Storming is where the model earns its reputation. Once the initial politeness fades, real differences emerge: work styles, values, authority, how decisions get made. Conflict spikes. Cliques form. Individuals push back against the leader or each other.

This is healthy. Teams that skip Storming or suppress it tend to plateau at false harmony. Unresolved tension doesn't disappear. It goes underground and poisons later stages.

Typical signs of Storming:

• Open or passive disagreement about approach or priorities
• Competition for influence or recognition
• Resistance to leader decisions or group norms
• Emotional conversations that spill outside formal meetings
• Subgroups forming along lines of affinity or interest

Leader behavior: Coaching. Name the conflict without amplifying it. Help the team surface the real disagreement rather than the surface-level argument. This is where emotional intelligence matters more than authority.

Stage 3: Norming

Norming is the resolution phase. The team establishes how it actually works: how decisions get made, what communication looks like, which behaviors are acceptable. Trust grows because people have survived a conflict together. Collaboration increases and individuals start putting the group's goals ahead of their own preferences.

The risk at Norming is tipping into false consensus. A team that has learned to avoid conflict may stop challenging weak ideas in the name of harmony.

Typical signs of Norming:

• Agreed-upon ways of working that everyone follows
• Increased willingness to give and receive feedback
• More open communication, including lateral (peer-to-peer) rather than only vertical
• Rising productivity as process friction decreases
• Growing sense of group identity and belonging

Leader behavior: Supporting. Step back from directing. Reinforce norms, facilitate peer collaboration, and let the team's own structures do more of the work. Over-leading at this stage delays the team's ability to self-manage.

Stage 4: Performing

Performing is the target state. The team functions as a cohesive unit. Roles are clear, trust is high, conflict is constructive and resolved quickly. Members are interdependent in the best sense: they rely on each other's strengths without losing individual accountability. Productivity peaks because energy goes into the work, not internal friction.

Not every team reaches Performing. Many organizations cycle through Forming and Storming repeatedly as team composition changes. The ones that reach and sustain Performing typically have a leader who accelerated each earlier stage rather than skipping it.

Typical signs of Performing:

• High autonomy with minimal supervision needed
• Fast, constructive conflict resolution
• Creative problem-solving and mutual accountability
• Members proactively covering for each other's gaps
• Consistent output quality and delivery pace

Leader behavior: Delegating. Trust the team to manage itself. The leader shifts from in-the-weeds involvement to strategic input, removing blockers, and recognizing wins.

Stage 5: Adjourning

Adjourning (added by Tuckman and Jensen in 1977) captures the end of a team's lifecycle. This might be a project wrapping up, a department restructuring, or a temporary task force disbanding. Members process the end of their shared identity and transition back to individual roles or other teams.

Adjourning often gets skipped in practice, especially in organizations that treat closure as soft or optional. That's a mistake. Teams that end without a proper close often carry unresolved feelings into the next formation.

Typical signs of Adjourning:

• Decreasing focus on the work as end date approaches
• Reflective conversations about what the team accomplished
• Emotional responses (pride, grief, anxiety about what's next)
• Disengagement from group norms now that they're no longer needed

Leader behavior: Closing. Celebrate the work, acknowledge individuals, and create space for the team to process the ending with intention.

Quick comparison: behavior, conflict, productivity by stage

How leaders should lead at each stage (behavior matrix)

The biggest leadership mistake with Tuckman is applying the same style across all stages. A leader who delegates at Forming leaves the team floundering. One who directs at Performing kills initiative. The model pairs naturally with situational leadership theory, which argues that effective leaders match their style to the team's developmental readiness.

Here's how the behaviors align:

Forming: Directing. High task behavior, low relationship behavior. Define goals, assign roles, set norms. The team needs clarity more than autonomy at this point.

Storming: Coaching. High task behavior, high relationship behavior. Keep the work moving while actively managing the emotional dynamics. One-on-ones matter here. So does naming the real disagreement rather than letting it fester.

Norming: Supporting. Low task behavior, high relationship behavior. The team has its footing. The leader's job is to reinforce good patterns, not to take over. This is where trust-building compounds.

Performing: Delegating. Low task behavior, low relationship behavior. Get out of the way. The team is self-managing. The leader's value now comes from strategy, resource access, and protection from organizational noise.

Adjourning: Celebrating. The leader shifts from performance management to recognition and closure. Acknowledging contribution matters for every member's experience of the organization after the team dissolves.

These situational leadership styles don't imply permanent categorization of any person or team. They describe what the situation requires at a specific moment.

Tuckman in real teams: 3 examples

A new product squad after a reorg

A mid-market SaaS company restructured its product teams after an acquisition and created a cross-functional squad of five people who had never worked together. The first three weeks looked calm. But by week four, the engineering lead and the product manager were in open conflict about sprint priorities. The team had hit Storming. The VP of Product made the mistake of trying to resolve it by adding more structure and oversight. What the team actually needed was a facilitated session where both parties named their underlying concerns: the engineer felt technical debt wasn't visible in the roadmap; the PM felt deadline pressure wasn't being factored into architecture decisions. One conversation moved the team from Storming to early Norming faster than two months of top-down process changes.

A cross-functional task force

A regional healthcare network assembled a task force of department heads to redesign the patient intake process. The group came with strong individual opinions and institutional allegiances. Storming started before the second meeting. The chair learned to use the Tuckman model explicitly: she named the stage the group was in during a kickoff retrospective and used that framing to depersonalize the conflict. When a department head pushed back aggressively in session three, she referenced Storming by name. The group laughed in recognition. That one moment of named reality moved the energy from defensive to productive within twenty minutes.

A remote engineering team

A fully distributed team of eight engineers joined a Series B startup during rapid scaling. Because the team was remote, the normal Forming cues were harder to read: nobody had a "vibe" from physical presence. The manager extended the Forming phase intentionally with structured onboarding rituals: paired code reviews in week one, a shared working agreement document in week two, explicit norms for async communication in week three. Storming still arrived, in the form of disagreements about code standards. But having a working agreement already in place gave the team a document to argue against rather than each other. They reached Norming two months faster than the previous remote team had.

When teams get stuck (and how to unstick them)

Most team dysfunction isn't random. It's a team stuck in a stage they should have moved through. Here are the warning signs and how to respond.

Stuck in Forming:

• Symptoms: Persistent questions about basics, refusal to act without explicit permission, no emerging peer dynamics
• Cause: Insufficient clarity from the leader, or a team that has been burned by unclear expectations before
• Unstick: Publish a working agreement. Hold a structured kickoff with roles, goals, and decision rights explicitly documented.

Stuck in Storming:

• Symptoms: Chronic conflict, unresolved personal tensions, gossip as a proxy for direct conversation, leader spending most of their time mediating
• Cause: Conflict is real but no one is naming it cleanly; or leader is avoiding the mediation role
• Unstick: Name the conflict explicitly. Run a structured retrospective. Surface the underlying disagreement (usually about priorities, ownership, or values) and resolve it with a concrete decision rather than vague compromise.

Stuck in Norming:

• Symptoms: Polite agreement that never converts to honest challenge, good vibes but weak output, nobody willing to push back on flawed ideas
• Cause: The team has overcorrected from Storming and now prioritizes harmony over truth
• Unstick: Introduce constructive friction on purpose. Assign devil's advocate roles in planning sessions. Reward dissent when it's substantive. Make it safe to be the person who says "this plan won't work."

Stuck pre-Performing:

• Symptoms: Team is functional but never reaches high output, lacks ownership, waits for direction even on familiar problems
• Cause: Leader hasn't delegated enough, or team doesn't have the skill level the role requires
• Unstick: Audit where the leader is still holding decisions the team should own. Push those decisions down. If skill gaps are the barrier, close them explicitly.

A useful check: if you're spending most of your leadership energy on the same type of problem week after week, the team is likely stuck in a specific stage rather than facing one-off issues.

Common misunderstandings about Tuckman's model

• The stages are always linear. They're not. Teams regress. A major personnel change, a pivotal project failure, or a leadership transition can push a Performing team back to Storming. The model describes a developmental arc, not a one-way escalator.
• Each stage has a fixed duration. Timing varies wildly by team size, complexity, history, and leadership quality. A well-led team can move from Forming to Norming in weeks. A team with unresolved legacy conflict can stay in Storming for quarters.
• Adding a new member doesn't restart the whole cycle. It restarts aspects of it. The team has to re-form around the new member's role, which often triggers a mini-Storming before restabilizing. This is why onboarding is a team leadership challenge, not just an HR administrative task.
• Storming equals failure. This is probably the most damaging misreading. Storming is evidence that people care enough to disagree. A team that never Storms has either been given work that doesn't require real collaboration, or it's suppressing conflict that will surface later at higher cost.

These misunderstandings matter practically. A leader who expects linear progress will overreact to regression. One who expects a fixed timeline will push teams through stages before they're ready, which almost always produces fake Norming and stunted Performing.

How to apply Tuckman's stages today (5 practical steps)

Use this sequence when you join a new team or inherit a team mid-flight.

1. Diagnose the stage before acting. Before doing anything else, observe for one to two weeks. What is the conflict pattern? Where does the energy go? Are people dependent on you for small decisions (Forming) or are they quietly competing with each other (Storming)? Your behavior prescription depends on accurate diagnosis. This connects to the broader skill set in leadership vs management: managers optimize current performance; leaders develop the team's capacity over time.

2. Name the model explicitly with the team. Tuckman is one of the few frameworks that helps people depersonalize group dynamics. Saying "we're in Storming, which is normal and required" changes the team's relationship to the conflict. You don't have to run a training session. A five-minute reference in a team meeting is often enough to shift the framing.

3. Match your leadership style to the stage, not your preference. Most leaders have a default style: some prefer directing, some prefer coaching, some prefer delegating. The Tuckman model is a forcing function to override that default when the situation demands something different. Use classic leadership styles as a reference for the behavioral toolkit across styles.

4. Create stage-specific rituals. Forming benefits from structured onboarding. Storming benefits from regular retrospectives with explicit psychological safety signals. Norming benefits from team-authored working agreements. Performing benefits from autonomy and strategic challenges. Adjourning benefits from intentional closure events. The ritual itself matters less than the deliberate investment in the developmental stage.

5. Audit yourself for blocking behaviors. Leaders often stall their teams inadvertently. A leader who centralizes decisions keeps the team in Forming. One who avoids conflict keeps the team in Storming. One who micro-manages keeps the team from Performing. A regular self-check against Tuckman's stage requirements and expected leader behaviors is a simple but effective leadership habit.

Understanding what is leadership at its core means recognizing that your role changes as the team matures. The 5 levels of leadership framework captures a similar progression: authority matters early; legacy comes from developing others. Tuckman shows you the developmental timeline you're working with. For a grounding in the full landscape of team and leadership frameworks, what is leadership theories provides useful context.

Frequently asked questions

Are Tuckman's stages always linear?

No. The stages describe a developmental arc, not a guaranteed sequence. Teams can and do regress. A major membership change, a high-stakes failure, or a significant shift in goals can push a team backward to an earlier stage. The most common regression is from Norming back to Storming when a new senior hire joins and shifts the group's power dynamics. The practical implication: don't assume a team that has reached Performing will stay there without ongoing attention.

How long does each stage take?

There's no fixed answer. Stage duration depends on team size, the complexity of the work, how much unresolved conflict the team carries from past experiences, and the quality of leadership through each phase. Well-led teams with experienced members can move from Forming to Norming in four to eight weeks. Teams with legacy conflict, unclear goals, or high turnover can remain in Storming for six months or longer. The model is descriptive, not prescriptive about timing.

What happens when a new member joins?

The team partially resets. At minimum, it re-enters a version of Forming as it incorporates the new person into its roles, norms, and communication patterns. Whether a mini-Storming follows depends on how disruptive the new member's presence is to existing dynamics, particularly if they arrive with authority, a different working style, or responsibility for a function previously owned by someone else. Smart leaders treat new member onboarding as a deliberate team-level transition, not just individual HR administration.

Is storming a sign of a bad team?

Quite the opposite. A team that never Storms is either not doing work that requires real interdependence, or it's suppressing conflict that will eventually appear in more destructive forms. Storming is evidence that people are invested enough to disagree. The teams that skip visible Storming and go straight to apparent harmony often have underlying tensions that surface during high-pressure moments, at exactly the wrong time. The goal isn't to eliminate Storming. It's to move through it productively, with the conflict surfaced, addressed, and resolved rather than buried.

Every team you lead is somewhere in this model. The question is whether you know where, and whether you're leading with that in mind. The leaders who can read stage dynamics and adapt accordingly aren't better people. They're better informed. That's a gap worth closing.