The 5 stages of team development (and what to run at each)

The stages of team development are the phases a group tends to move through as it comes together: forming, storming, norming, performing, and adjourning. Bruce Tuckman named the first four in a 1965 review of small-group research; the fifth was added in 1977. Each stage has a distinct feeling, an honest signal to read past it, and a specific thing worth running.

The model is famous because it is easy to remember, not because it was ever proven. Read it as a way to take the temperature of a team, not as a timetable the team will keep. The question that matters is not which stage you are in. It is what to do about it.

Where the model comes from (and what it is not)

Tuckman’s 1965 paper, Developmental Sequence in Small Groups, was a literature review of roughly fifty studies of therapy and training groups, not an experiment (Tuckman 1965, summarized by MindTools). He described a pattern he noticed in other people’s data. In 1977, with Mary Ann Jensen, he reviewed a further set of studies and added a fifth stage, adjourning, for the ending of a team (Tuckman and Jensen, 1977). So the model is a synthesis of observation, and that origin sets a sensible ceiling on how literally to take it.

The stages, and what to run at each

Here is the useful version. For each stage: what it feels like, the signal most explanations skip, and the intervention worth running. The table is the map; the detail is below it.

Stage	What it feels like	What to run
Forming	Polite and cautious; people defer to whoever leads	Icebreakers, a check-in ritual, a first charter
Storming	Friction over who owns what and how work gets done	Working agreements, a safe space, regular retros
Norming	The team finds its rhythm and roles get clearer	Lock in the charter, run a health check
Performing	The team runs itself with little drama	Protect the cadence, keep measuring
Adjourning	Work wraps up and energy dips	A closing retro to capture what you learned

Forming: polite, and waiting to be told

What it feels like. New teams are careful. People defer to whoever seems in charge, and keep their real opinions soft. There is often energy, but it sits on the surface.

The honest signal. Silence is not agreement at this stage. It is people who do not yet feel safe enough to disagree. A forming team that looks harmonious is usually just guarded, and the harmony breaks the moment real work creates friction.

What to run. This is the thaw. Lower the cost of disagreement before you need it. Run a round of icebreakers that surface something real rather than trivia, open every meeting with a short check-in, and start writing down how the team will work together. The full method for warming a cold or new team is in how to defrost a team. To do it live, Two Truths and a Lie or Common Ground get a new group talking within a few minutes.

Storming: friction surfaces

What it feels like. Once people are comfortable enough to be honest, the differences appear. There are arguments about who owns what and how the work should be done, and it can feel as though the team is sliding backward.

The honest signal. Storming out loud is a good sign. The failure mode is storming underground, where disagreement gets swallowed to keep the peace and then leaks out as quiet resistance. Suppressing conflict to protect harmony is the real problem, not the conflict itself. And if your team never visibly storms, do not force it: in Tuckman’s own review, only about half the groups showed a distinct conflict stage (per the criticism summarized on Wikipedia).

What to run. Make disagreement safe and give it structure. Agree a set of team norms and working agreements that spell out how you make decisions and handle conflict. Build the trust and psychological safety that lets hard things get said in the room rather than in the corridor; Amy Edmondson’s study of 51 work teams found psychological safety associated with more learning behavior and better performance (Edmondson, 1999). A regular retrospective then gives friction a scheduled, low-stakes outlet.

Norming: the agreements settle

What it feels like. The team finds its rhythm. Roles get clearer, people start to rely on each other instead of routing everything through the manager, and trust begins to compound.

The honest signal. Watch for false harmony. Norming can quietly slide into avoiding the very disagreements that made storming useful, which is the leading edge of groupthink. A team that has stopped arguing altogether may have stopped thinking critically together.

What to run. Lock in what works. This is the refreeze: turn the habits you want to keep into an explicit team charter and put a date in the calendar to revisit it. Then start measuring the team’s state with a health check, so trust and clarity become something you can see and track rather than guess at.

Performing: the team delivers

What it feels like. The team runs itself. People self-organize and handle disagreement without it turning into drama. This is the stage everyone wants, and the one that is hardest to hold.

The honest signal. Performing is fragile, and it rewards maintenance over neglect. The measure that counts is not how good a discussion feels but whether decisions turn into finished work. A team that follows through is performing; a team that only meets well is not.

What to run. Protect the cadence. Keep the check-ins and retrospectives even when the work is going well, because that rhythm is what holds the stage in place. Re-run the same health check on a regular beat to catch drift early, while it is still cheap to fix.

Adjourning: the team ends

What it feels like. The work wraps up and the team disbands or reforms. Energy usually dips, and there is a sense of loss even when the project went well.

The honest signal. The temptation is to skip the ending and roll straight into the next thing. That wastes the most reflective moment a team ever gets.

What to run. Close on purpose. Run a final retrospective to capture what the team learned and to name what each person brought to it. If part of the group carries forward into new work, remember that it starts at forming again, whatever it achieved together before.

The honest limitation: it describes, it does not predict

This is where most explanations of Tuckman go quiet, so three things are worth saying plainly.

First, the evidence is thinner than the model’s fame suggests. It came from reviewing other people’s studies, and in the 1965 review only about half of them showed a clear storming stage; some groups moved straight from forming to norming. The stages describe a common pattern, not a law.

Second, teams do not move in a straight line. Even strong teams slide back to earlier stages under pressure, a reorganization, or a missed deadline. Regression is ordinary, not a relapse to be ashamed of.

Third, the model resets. The day a new person joins or a key person leaves, the team is partly back to forming, whatever the org chart says it reached. This is exactly why the what-to-run column never retires: a team that gained a member this quarter needs the forming moves again, not a certificate that says it is performing.

So do not call the model proven, and do not use it to grade a team. Use it to name what the team is feeling and to choose the next intervention.

The discipline complement: the team performance curve

Tuckman tells you how a team feels as it grows. It says nothing about what a team owes itself to become good. For that, the more demanding companion is Jon Katzenbach and Douglas Smith’s team performance curve, from The Wisdom of Teams (1993) (Katzenbach and Smith, via Praxis). They define a team narrowly: a small number of people with complementary skills, committed to a common purpose and set of goals, who hold themselves mutually accountable for how they get there.

Their curve runs through five points: working group, pseudo-team, potential team, real team, and high-performing team. The warning in the middle is the part worth keeping. A pseudo-team, a group that calls itself a team but shares no real purpose or mutual accountability, performs worse than a plain working group that never pretended to be one. Naming a team is not the same as being one.

Read together, the two models divide the labor. Tuckman tells you where a team sits emotionally. Katzenbach and Smith tell you what to demand of it: a real shared goal and complementary work rather than a pile of overlapping tasks. Above all, accountability that people hold to each other, not up to a boss. A team does not drift into performing. It commits its way there.

Facilitators who prefer a model built around questions sometimes reach for the Drexler/Sibbet Team Performance Model instead, which frames seven stages, from orientation to renewal, as questions a team has to answer (the Grove). It front-loads trust, which makes it a natural fit alongside the warming work in this guide.

Using both with a real team

In practice, use Tuckman to read the room and the performance curve to decide what to push for. When a team feels stuck in polite forming, the intervention is warmth and clarity: warm it up and give it something concrete to agree on. When a team is comfortable but coasting, the intervention is a harder goal and clearer accountability. Both models circle the same question this guide keeps returning to: what makes a team work rather than only meet.

Frequently asked questions

What are the 5 stages of team development?

The five stages are forming, storming, norming, performing, and adjourning. Bruce Tuckman described the first four in 1965 and added adjourning in 1977 with Mary Ann Jensen. Forming is cautious, storming brings conflict to the surface, norming settles into shared agreements, performing is where the team delivers, and adjourning is the wind-down when the work ends.

Who created the forming, storming, norming, performing model?

Psychologist Bruce Tuckman published the forming-storming-norming-performing sequence in a 1965 review of small-group studies. It was a synthesis of other researchers’ observations rather than an experiment. He and Mary Ann Jensen added the fifth stage, adjourning, in a 1977 follow-up review of further studies.

Does every team go through a storming stage?

No. In Tuckman’s own 1965 review, only about half the studies showed a distinct conflict stage, and some groups went straight from forming to norming. If your team never obviously storms, that is normal. The real warning sign is conflict that gets suppressed to keep the peace rather than aired in the room.

Do teams move through the stages in order?

Not reliably. The model describes a common pattern; it does not predict a fixed sequence. Teams regress to earlier stages under pressure, and a team resets toward forming whenever someone joins or leaves. Treat the stages as a way to read a team, not a schedule it is bound to keep.

What should you do at each stage of team development?

Match the intervention to the stage. In forming, run icebreakers and check-ins and start a charter. In storming, agree working norms and make disagreement safe. In norming, lock in the charter and measure with a health check. In performing, protect the cadence. In adjourning, run a closing retrospective to capture what you learned.