The Tuckman model is a framework that describes five predictable stages every team moves through as it develops: forming, storming, norming, performing, and adjourning. Psychologist Bruce Tuckman introduced the first four stages in 1965 after reviewing dozens of studies on small-group behavior. He and Mary Ann Jensen added the fifth stage, adjourning, in 1977. The model remains one of the most widely taught concepts in team development and organizational training, giving managers and team members a shared vocabulary for understanding why collaboration feels easy some weeks and impossible others.
Forming: The Polite Start
Forming is the initial phase where everything feels tentative. Team members are typically excited to be part of something new and eager about the work ahead, but they’re also uncertain about their roles, the group’s rules, and what’s expected of them. People ask a lot of questions during this stage, partly out of genuine curiosity and partly because they’re trying to figure out where they fit and whether their performance will measure up.
Actual task accomplishment tends to be low during forming because so much of the group’s energy goes toward defining itself. The real work of this stage is structural: establishing clear goals, assigning roles, setting direction, and beginning to build trust. Think of it as the orientation period. People are on their best behavior, avoiding conflict, and looking to a leader or organizer for guidance. That politeness is a feature, not a flaw. It creates enough psychological safety for the group to take its next, messier step.
Storming: When Friction Surfaces
Storming begins once the group moves past introductions and starts dividing up real work. The process of organizing tasks and responsibilities brings interpersonal conflicts to the surface. Leadership, power, and structural issues dominate this stage. You’ll see arguing among members, people vying for influence, and clashes driven by differences in working style, opinion, or personality. Role clarity is often still lacking, which fuels the tension.
This stage feels uncomfortable, and it’s the one most likely to stall a team’s progress. Some members may become frustrated or disillusioned, wondering whether the group can function at all. But storming serves a purpose: it forces the team to negotiate how decisions get made, who holds authority on what, and how disagreements will be handled going forward. Teams that suppress conflict during this phase don’t skip it. They just delay it.
Norming: Establishing How Things Work
Once a team works through its power struggles and style clashes, it enters norming. This is where the group settles into agreed-upon ways of working together. Members develop shared expectations for communication, decision-making, and accountability. The friction from storming doesn’t vanish entirely, but it becomes productive rather than personal. People start giving and receiving feedback more openly, and the sense of “us” begins to replace the earlier emphasis on “me.”
Trust deepens during norming because team members have now seen each other handle disagreement and come out the other side. Collaboration feels more natural, roles are clearer, and the group starts producing consistent work. The risk at this stage is complacency: teams can become so comfortable with their norms that they avoid challenging ideas or pushing for higher performance.
Performing: Peak Productivity
Performing is the stage every team is aiming for. The group operates with a high degree of autonomy, competence, and mutual trust. Members understand their roles well enough to adapt flexibly when circumstances change. Problem-solving happens efficiently because the groundwork of norms and relationships is already in place. Energy that used to go toward navigating interpersonal dynamics now goes directly into the work itself.
Not every team reaches this stage. Some get stuck in storming or settle into a comfortable but mediocre version of norming. Teams that do reach performing aren’t conflict-free. They’ve simply built the capacity to handle disagreements quickly and constructively without reverting to earlier power struggles.
Adjourning: The Wrap-Up
Tuckman and Jensen added this fifth stage in 1977 after reviewing additional research on how groups dissolve. Adjourning covers the period when a team’s work is complete and members prepare to move on. For project-based teams, this might mean a final review, a handoff of deliverables, and a retrospective. For longer-standing teams, it could follow a reorganization or the departure of key members.
The emotional texture of adjourning varies. Some members feel satisfaction and relief. Others experience something closer to loss, especially if the team reached a high-performing state and built strong relationships. Acknowledging this stage matters because it gives people permission to reflect on what worked and carry those lessons into future teams.
How the Model Applies to Virtual Teams
Research on virtual learning teams has found that Tuckman’s stages describe how remote groups develop better than competing theoretical models. Virtual teams move through forming, norming, and performing in recognizable ways, and their development tends to cluster tightly around project timelines. One notable difference: virtual teams in studies showed rapid movement between stages, with almost no evidence of a distinct storming phase. The compressed timelines and text-based communication of remote work seem to reduce (or at least obscure) the open conflict that characterizes storming in face-to-face groups.
Another difference is leadership. In co-located teams, a single person often emerges as the leader during forming and storming. In virtual teams, leadership tends to be shared among members, rotating based on who has the most relevant expertise for a given task. If you’re managing a remote or hybrid team, you may notice your group cycling through stages faster and less visibly than the model suggests, which makes it worth checking in explicitly about roles and expectations rather than waiting for conflict to signal that something needs attention.
Where the Model Falls Short
The Tuckman model’s biggest limitation is its implied linearity. The original framework suggests teams move neatly from one stage to the next, but real groups rarely work that way. Stages can merge into each other, repeat, or get skipped entirely. A strong, cohesive team might bypass storming altogether because its members are skilled enough at debate to disagree without devolving into interpersonal conflict. A team that reached performing can slide back to storming when a new member joins, someone leaves, or a major external disruption hits.
Tuckman himself acknowledged some of these limitations. Much of his original observation came from therapy-group settings, and as researcher Denise Bonebright noted in a 2010 historical review, the model was “generalised well beyond its original framework.” The model also doesn’t account for external factors like organizational culture, resource constraints, or shifting priorities, all of which influence how (and whether) a team develops. It says little about motivation, individual personality differences, or the specific leadership behaviors that help a team progress.
None of this makes the model useless. It gives teams a simple, shared language for recognizing what’s happening in their group dynamics. The value isn’t in treating the five stages as a rigid checklist. It’s in using them as a diagnostic lens: if your team is stuck, the model helps you name the stage you’re in and think about what needs to happen next. Just don’t expect the path to be a straight line.