Tuckman's 5 Stages of Team Development
In 1965 psychologist Bruce Tuckman observed that nearly every team moves through the same five phases of team development on its way to high performance: forming, storming, norming and performing — with adjourning added later for when the team disbands. The Tuckman model (forming storming norming performing) matters because the hard part, storming, is normal and unavoidable. Teams that name it and push through reach performing; teams that mistake it for failure stall.
The five stages at a glance
| Stage | What's happening | How you can tell | What the leader does |
|---|---|---|---|
| 1. Forming | Polite and guarded; roles are unclear and the group leans on the leader. | Lots of questions, little real debate; everyone is on best behavior. | Set the goal, the roles and the ground rules. Remove uncertainty. |
| 2. Storming | Friction over priorities, methods and who decides. Most teams stall here. | Tension or silence in meetings, missed deadlines, the same argument on repeat. | Surface conflict safely and re-anchor everyone on the shared goal. |
| 3. Norming | Norms and roles settle, trust grows, and people start covering for each other. | Smoother meetings, easier feedback, a shorthand of the team's own. | Keep healthy debate alive; guard against over-niceness. |
| 4. Performing | The team runs itself — confident, autonomous and aligned. | Problems get solved before they reach the leader. | Shift from directing to enabling: remove obstacles, develop people. |
| 5. Adjourning | The project ends and the team winds down. | Work is wrapping up; energy turns to what's next. | Mark the close, reflect on the lessons, celebrate the work. |
The five stages in depth
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.
How to tell which stage your team is in
Teams rarely announce their stage — you read it from behavior. A few reliable signals:
- Still forming if people route every question through the leader and real opinions only surface one-to-one afterward.
- Storming if meetings are tense or unusually quiet, deadlines slip, and the same disagreement keeps resurfacing in different clothes.
- Norming once the team has a shorthand of its own, gives feedback without bracing for it, and starts covering gaps unprompted.
- Performing when problems get solved before they reach you, and the group protects its own focus.
The trap is reading a storming team as a broken one. The friction is the work of becoming a team — not evidence that it failed.
How leadership should change at each stage
The most useful thing the model tells a manager is that your job description changes as the team matures. Lead a performing team the way you'd lead a forming one and you smother it; lead a forming team like a performing one and it drifts.
- Forming — direct. Be clear and visible. Set the goals, the roles and the first few decisions yourself.
- Storming — coach. Stay close, mediate, and keep re-pointing everyone at the shared goal while conflict does its work.
- Norming — support. Move into a facilitator role. Let the team own more decisions and protect the norms it's building.
- Performing — delegate. Get out of the way. Remove obstacles, develop people, and let the team run.
How long does each stage take?
There's no fixed clock. A team that meets an hour a week can sit in forming for months, while a group thrown together on an intensive project can hit storming by day two. What's consistent is the order, not the pace — and the pace is partly in your control. Teams stall longest in storming, and the fastest way through is to give the group a reason to communicate and disagree somewhere low-stakes before a real deadline forces it.
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.
Where the Tuckman model falls short
No model is the territory. Real teams don't always move in a clean line — a reorganization, a new hire or a lost client can drop a performing team straight back into storming, and some groups loop between norming and storming for years. The stages also describe the team's internal relationships more than its output: a team can be technically productive while still stuck socially in storming. Treat Tuckman as a shared language for what a team is feeling, not a rigid schedule it must obey — that's where its real value lives.
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.
Frequently asked questions
What are Tuckman's stages of team development? +
Forming, storming, norming, performing and adjourning — the five phases a team moves through as it comes together, works out conflict, settles into norms, performs at its best and eventually disbands.
Which stage is hardest? +
Storming. It's where conflict and frustration surface, and many teams stall there. Naming the stage and resetting shared goals is what moves a team into norming.
Can team building speed up the stages? +
Yes. A shared, hands-on challenge compresses forming and storming into a single day by giving people a low-stakes reason to communicate, divide roles and build trust before it matters on a real project.
Who created the stages of team development? +
Psychologist Bruce Tuckman, in a 1965 paper titled “Developmental Sequence in Small Groups.” He proposed four stages — forming, storming, norming and performing — and added a fifth, adjourning, in 1977 with Mary Ann Jensen.
What is the difference between the four and five stages? +
The original 1965 model had four stages, ending at performing. Adjourning — the wind-down when a project team disbands — was added in 1977, giving the five-stage version most people use today.
How long does the storming stage last? +
There's no fixed length; storming lasts as long as the team avoids the conflict underneath it. Naming the stage and re-anchoring on a shared goal is what ends it, which is why a facilitated, low-stakes challenge can compress storming into a single day.
Move your team from storming to performing.
Tell us your group size, city and goals. We’ll send a tailored proposal — and design a shared challenge that builds trust your team carries back to work.

