GSLKThe club library

Tuckman's stages of team development

A new board spends its first term arguing and concludes the team is wrong. Usually the team is fine — it simply has not got past a stage that has a name.

← The whole library

Bruce W. Tuckman · 1965

How it works

A team clashes and everyone concludes the team is bad. Tuckman gave that friction names — forming, storming, norming, performing — and the name alone takes some of the panic out.

Formingeveryone is polite and nobody has said what they actually want
Stormingthe first real argument; this is where teams usually fall apart
Normingan order nobody wrote down appears, and everyone keeps to it
Performingthe work moves without anyone having to be asked
Adjourningthe end of the term; this stage was added in 1977

This is vocabulary for naming friction, not a diagnosis: the sequence was never tested, so teams are under no obligation to pass through it in order.

What you do first

Next time a meeting turns tense over who decides what, say out loud that this is a normal phase, then ask one question: what exactly do we need to settle today? It costs one sentence and changes the whole tone.

Do not overdo this part: This is a literature review, not an experiment, and the groups studied were not student teams. Useful as shared language, not as a diagnosis.

Who thought of it

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.

The full biography is on the public version →

No freely licensed likeness of this person exists, so this is a generated emblem. It is not a portrait.

Why this matters

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 this runs in the platform

These screens carry out this specific work. Every published work in the library also has at least an exercise — it is at the foot of this page.

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

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.