Tuckman's 5 Stages of Team Development

The five stages

1. Forming

The team comes together. People are polite, a little guarded, and lean heavily on the leader for direction. Roles are unclear and real opinions stay hidden. Energy is high but trust is shallow. The leader's job here is clarity: spell out the goal, the roles and how the group will work, so uncertainty doesn't harden into anxiety.

2. Storming

Reality sets in and friction surfaces — over priorities, methods, status and who decides what. This is the stage most teams find painful, and the one where many quietly stall, settling into a low-trust truce instead of working through it. Storming isn't a sign the team is broken; it's the sign it's becoming real. The leader's job is to surface conflict safely, re-anchor everyone on the shared goal, and turn disagreement into decisions.

3. Norming

The team works out how it actually operates. Norms emerge, roles settle, trust grows, and people start covering for one another instead of competing. Feedback gets easier. The risk here is over-niceness — avoiding hard conversations to protect the new harmony — so keep healthy debate alive.

4. Performing

The team runs largely on its own. Members are confident, autonomous and aligned, and the group solves problems without the leader brokering every step. Leadership shifts from directing to enabling — removing obstacles, protecting focus and developing people.

5. Adjourning

Tuckman added this stage in 1977 for project and event teams that eventually wind down. The work ends; the relationships shouldn't just evaporate. Mark the close, reflect on what the team learned, and celebrate it — so people carry the lessons (and the goodwill) into the next team.

Why the Tuckman model still matters

Its real value is permission. When a team hits storming and someone can say "this is normal, this is the storming stage," the conflict stops feeling like a crisis and starts feeling like a phase to move through. Naming the stage is half the work.

Later models have refined it, but the Tuckman model endures because it maps to what people actually feel. Managers use the forming, storming, norming, performing sequence as a shared language for team forming stages — a quick way to tell a new group "this friction is expected" and to spot which phase of team development a stalled team is really stuck in. You don't manage a storming team the way you manage a performing one, and the model is what tells you which is which.

How to move a team through the stages faster

You can't skip storming, but you can compress it — and you can run it somewhere low-stakes before it shows up on a deadline. A shared, hands-on challenge forces a brand-new group to communicate, divide roles, disagree, and recover, all in a single day where nothing is on the line. That's why a well-designed team experience accelerates the arc: people do their forming and storming over a build table, then bring the norming and performing back to real work. For intact leadership teams, ongoing team coaching does the same over a longer horizon, and structured programs keep the gains from fading.

The single best activity we've found for seeing the model in action is Let Go My Ego. A group runs through all four stages — forming, storming, norming and performing — in a matter of minutes, and each stage is unmistakable as it happens. It turns Tuckman from an abstract diagram into something a team has actually felt together, which makes the debrief land: everyone can point to the moment they were storming, and the moment they broke through to performing. If you’re starting from scratch, our guide to team building for a newly formed team shows how to move a group through these stages fast.