Tuckman's Stages of Group Development

Theory & origin

Bruce Tuckman synthesized the model in 1965 from around fifty studies of small groups, and added adjourning with Mary Ann Jensen in 1977. The claim is developmental: teams pass through recognizable stages, and each stage has different work to do. Forming is orientation, where people test the edges of the room and depend heavily on the leader. Storming is the necessary fight over roles, status, and how work will actually happen, and it is where psychological safety gets built or broken. Norming settles the rules of engagement into working agreements. Performing is the payoff, where structure serves the work instead of consuming attention. Adjourning is the ending, grieved or celebrated, that most organizations simply ignore. Modern caveats matter: real teams loop rather than march (a new member or a new mission sends the team back to forming), the stages describe tendencies rather than laws, and remote teams often mute the storm into passive silence instead of visible conflict, which is worse. The model's enduring value is permission: it tells a leader that conflict at month two is developmental, not evidence of a bad hire.

Key components

The parts at a glance. Click any term for the full definition, a field example, and the common failure, in the model below.

How a consultant runs it

1. 01 Name the stage out loud with the team. Half the value of the model is a team recognizing "we are storming, this is the toll booth, not the destination."
2. 02 Design the storm instead of suppressing it: conflict norms, decision rules, and working agreements give the fight a container.
3. 03 Match the leadership style to the stage: directive in forming, coaching through storming, delegating by performing. One style across all stages is the classic error.
4. 04 Re-form deliberately on every membership change. A new joiner does not join a performing team, they create a new forming one.
5. 05 Close teams properly. Adjourning with a retrospective and real recognition is cheap, and skipping it teaches people that endings here are abrupt.

Worked example

A core-banking build squad at a Jakarta multifinance firm hits month three: velocity has halved, two seniors are fighting through pull-request comments, and the sponsor wants someone replaced. The stage read says storming, right on schedule for a team formed twelve weeks ago. Instead of swapping people, the fix gives the storm a container: a facilitated session where the two seniors argue the data-model question to a decision in the room, written working agreements, and decision rules for the next collision. The team norms within a month and hits its best velocity by month five. The sponsor learns the expensive lesson cheaply: the replacement they wanted would have reset the whole road to week one.

Common pitfalls

1. 01 Treating storming as failure and swapping people, which resets the team to forming with fresh strangers
2. 02 One leadership style for every stage, usually directive, which suffocates norming and performing
3. 03 Reading remote silence as harmony. Distributed teams storm quietly, in DMs and disengagement.
4. 04 Celebrating norming cohesion so hard that nobody risks conflict again, which caps the team below performing
5. 05 Skipping adjourning, so institutional memory and loyalty evaporate with the team

Sample deliverable

One real engagement, start to finish. Watch the numbers travel from raw input, onto the chart, into the finished artifact.