← All foundations
1965Learning

Tuckman's stages of team development

The model lets the coach say "you are in storming, that is normal". It is used only as language, because as an empirical sequence it is far weaker than its popularity suggests.

The point, in one line

Forming, storming, norming, performing — a shared vocabulary for friction. Not a diagnosis and not a score.

Concept diagram
Four stages, a fifth added in 1977 — and the study that did not find the sequence
TUCKMAN, 1965+ 1977: ADJOURNINGForming01Storming02Norming03Performing04Adjourning05Gersick (1988), eight naturally occurring task groups: there was no uniform stage sequence.Instead: long inertia, broken by concentrated change triggered by a deadline.THE 1977 REVIEW: OF 22 STUDIES ONLY 1 SET OUT TO TEST THE HYPOTHESIS
The 1965 text is a review of 50 articles, not an experiment. gslk uses the stage names only as vocabulary for naming friction — never as a diagnosis or a score.
The same thing, in your club
  1. The situation

    At the third committee meeting two people clash for the first time over who owns sponsors, and that evening one of them writes that he is stepping down.

  2. What the model says

    This reads as storming, and the name alone takes some of the panic out: an argument is not evidence that the team is wrong.

  3. What you do

    At the next meeting say out loud that this is storming and that it is normal — that is the only thing this model is used for here.

What it claims

Tuckman proposed that small groups pass through a predictable developmental sequence, running in parallel across two realms — interpersonal and task. The mnemonic stage names are forming, storming, norming and performing; adjourning was added in 1977.

Honestly about the basis, and it differs sharply from the model's fame. The 1965 text is a literature review — Tuckman synthesised 50 articles on group development and induced a common sequence from other authors' descriptions. He ran no experiment, tested no hypothesis and collected no data of his own. The groups reviewed were also mostly therapy and training (T-)groups rather than work or student project teams — the transfer to modern teams was made by later practitioners, not by the 1965 paper.

The most telling datapoint comes from the authors themselves: in the 1977 review, of 22 studies examined only ONE had set out to test the hypothesis directly, and the paper closed by calling for more empirical work.

There is also a direct empirical contradiction: Gersick (1988, Academy of Management Journal, 31(1), 9–41), studying eight naturally occurring task groups, found they did not follow a uniform stage sequence but a "punctuated equilibrium" pattern — long stretches of inertia broken by concentrated change triggered by awareness of deadlines rather than by completing a stage. Bonebright's historical review (2010) describes how the model became popular among practitioners precisely because applied research was lacking. We found no meta-analysis establishing the sequence.

So gslk uses Tuckman only as vocabulary for normalising friction, and never as a diagnosis. There is no licensing question here: the model is freely citable and no official Tuckman instrument exists.

Who created it

BT1965
An illustrated emblem, not a portrait.
Bruce W. Tuckman
1965

Bruce W. Tuckman was then a psychologist at the US Naval Medical Research Institute in Bethesda, Maryland. He published "Developmental sequence in small groups" in Psychological Bulletin in 1965. In 1977, with Mary Ann C. Jensen, he reviewed the following decade's research and added a fifth stage — adjourning.

Why this is your problem

We have not written a practice step for this one yet. When we do, it will be as concrete as the rest.

Why gslk uses it

What this means for gslk

It answers a specific phenomenon: a first-year board spends half a semester arguing and concludes the team is "wrong". Having a name for what is happening is the cheapest tool available — it measures nothing, but it changes the interpretation. Which is why Tuckman in gslk is the coach's language and the frame for the weekly pulse, not a screen with a stage indicator.

Where it runs in the product

  • There is deliberately no stage score, no questionnaire and no dashboard indicator — a team's stage is not a quantity. What there is instead is the exercise at the foot of this page, which works on one real disagreement: when it happened and what it was actually about.
  • The language of the AI coach: recognising a team's stage and normalising friction in conversation.
  • Like the other coaching lenses, it lives in the coach's conversation — and the coach runs: the rail is on /admin.

Source

Reference

Tuckman, B. W. (1965). Developmental sequence in small groups. Psychological Bulletin, 63(6), 384–399. — Tuckman, B. W., & Jensen, M. A. C. (1977). Stages of small-group development revisited. Group & Organization Studies, 2(4), 419–427.

Read the primary source ↗
Rights and licence
In copyright

The primary source is in copyright. This page retells it in our own words and cites it rather than reproducing it.

What this connects to

These works are related to the one you just read — and not by accident:

Grounds these competency domains

Of the ten gslk competency domains, this work grounds:

The student version
Tuckman's stages of team development

The same work written for a member: what to do with it in the club.

Check it yourself

Links to publishers and libraries. There are no links to unauthorised copies here, and there will not be.

Links open in a new window.