Tuckman's stages of group development

Psychologist Bruce Tuckman published the first four stages in 1965 after reviewing dozens of studies on small-group behaviour. He added the fifth, adjourning, in 1977 with Mary Ann Jensen. Sixty years later it survives because it describes something managers recognise immediately: new teams are polite, then difficult, then finally good — and most give up somewhere in the middle.

The five stages at a glance

Forming: everyone is on best behaviour

In forming, people are working out whether they are safe and whether they belong. Questions get asked in private, not in the room. Consensus is fast, because nobody wants to be the first to object — which makes forming feel deceptively productive.

The trap is reading that politeness as alignment. It isn't. It's uncertainty wearing a suit.

What to do in forming

• State the purpose in one sentence, then ask each person to say it back in their own words. The gaps you hear are the real starting point.
• Make decision rights explicit: who decides, who consults, who is simply informed.
• Give the team a small, real task with a deadline inside the first week. Shared work builds familiarity faster than any introduction round.
• Name the storm in advance: 'in a few weeks we'll disagree about something and that's the point.' It gives people permission later.

Storming: the stage most teams misread

Storming is friction about how the work gets done — standards, pace, ownership, who gets heard. It shows up as tense reviews, quiet re-litigating in side channels, and one person's opinion mysteriously always winning.

A team that never storms hasn't skipped the stage. It has buried it — and buried conflict resurfaces as attrition.

Managers make one of two mistakes here. Some suppress the conflict to keep things pleasant, and end up with a team that agrees in the room and disagrees everywhere else. Others let it run unfacilitated, and the loudest person sets the norms for the next two years. Both stall the team indefinitely.

What to do in storming

• Separate the person from the position. Ask 'what would have to be true for that approach to be right?' rather than defending your own.
• Move disagreements out of private channels and into one meeting with a decision at the end.
• Use a structure that gives quiet people airtime — written positions before discussion, or round-robin before open debate.
• Close every conflict explicitly: what we decided, who owns it, when we revisit. Unfinished conflicts restart weekly.

Norming: habits form, for better or worse

In norming, the team settles. Meetings get shorter. People know who to ask. Standards stop needing to be argued because they've become assumptions.

The risk is that norms form by accident. If the loudest storming voice won every argument, the team's new normal is that person's preference — and the cost of that only becomes visible much later, when the good people leave.

What to do in norming

• Write the norms down while they're still fresh: how you review work, how you escalate, what 'done' means.
• Audit whose habits became the standard. If one person's style won everything, the team hasn't normed — it has capitulated.
• Protect the new stability from reorganisation. Every added or removed member sends the team briefly back toward storming.

Performing: the stage people mistake for luck

A performing team solves problems without escalating them, disagrees productively in public, and absorbs a bad week without drama. Supervision drops because it is no longer needed.

This is where most of the value of a team lives, and it is also the stage leaders most often break by accident — through constant re-staffing, shifting priorities, or promoting the informal glue-holder away without replacing what they did.

What to do in performing

• Give the team harder problems, not more problems. Stretch sustains performing; volume erodes it.
• Keep the team intact where you can. Membership churn is the single fastest way back to storming.
• Have the team debrief its own wins, not just its failures. Teams that can name why something worked can repeat it.

Adjourning: the ending nobody runs

Projects end, teams get restructured, people move on. Tuckman's fifth stage is about the loss that accompanies that — and it is almost always skipped, which is why people carry unprocessed endings into their next team.

• Run a real closing debrief: what we'd repeat, what we'd never do again, what each person is taking with them.
• Name individual contributions publicly. Recognition at an ending travels with people into their next role.
• Capture the norms that worked so the next team doesn't rebuild them from scratch.

Where the model breaks down

Tuckman's model is a useful map, not a law. Three honest caveats:

1. It isn't strictly linear. Teams loop back. A new joiner, a new manager, or a change of mandate can push a performing team straight back into storming — sometimes in a single week.
2. The stages overlap. A team can be performing on familiar work and storming on anything new. Stage is often per-domain, not per-team.
3. The evidence is descriptive, not predictive. Tuckman synthesised existing observational studies; the model describes patterns well but doesn't tell you how long any stage lasts or guarantee a team will progress at all. Plenty of teams stall in storming for years.

Used well, it does one important job: it stops managers panicking during storming and reaching for the wrong fix. The conflict isn't the failure. Avoiding it is.

How to tell which stage your team is in

Ask three questions, honestly:

1. Do people disagree with me in the room, or afterwards? Only afterwards means forming or a suppressed storm.
2. Do decisions stay decided? Constant re-litigating is storming.
3. Can the team handle a bad week without escalating to me? If yes, you're in performing — protect it.

This is also why experiential training works on team development: put a team into a short, real challenge and the stage reveals itself in about fifteen minutes. Who takes charge, who withholds, whose disagreement gets heard — the pattern is the same one they run at work, just visible.

Tour De Force runs this as live, experiential training for teams worldwide — online and in person. Talk to us, or play Gamified learning appsThe Weekly Challenge to see the method in ten minutes.