Topic
Tuckman stages of group development
Weak Weak
Bruce Tuckman's 1965 model: forming, storming, norming, performing, with adjourning added in 1977. It is the most widely taught team model in existence and one of the least empirically supported.
Evidence: Weak. A 1965 literature review of roughly 50 studies, mostly of therapy and training groups rather than work teams. Later research does not find that teams reliably pass through these stages in this order; Gersick's punctuated equilibrium work suggests a quite different pattern, with an abrupt transition near the temporal midpoint. The model also assumes stable membership, which most modern teams do not have. One message survives: early conflict in a new team is normal.
Use when: normalizing early team conflict so a new team does not conclude it is broken; giving a leader vocabulary for what to expect.
Do not use when: predicting a team's trajectory, diagnosing a stuck team, or justifying inaction ("we're just storming"). The evidence does not carry that weight.
The five stages
Forming: polite, tentative, dependent on the leader. Members test what is acceptable. Real disagreement is suppressed. Task progress is low; the work is orientation.
Storming: conflict over goals, roles, approach, and status. Frustration with the leader is common. Many teams stall here permanently, settling into a pseudo-norming truce in which the disagreement is simply no longer voiced.
Norming: agreement on how to work together. Norms form, roles settle, cohesion rises. Risk: cohesion purchased by avoiding the original conflict, which then resurfaces under pressure.
Performing: the team works interdependently on the task with little process overhead. Disagreement is about the work, not about the people.
Adjourning (or mourning): disbanding. Real loss for high-performing teams, and routinely unmanaged. See bridges-transition-model.
The evidence problem
- Tuckman's model was a literature review of about 50 studies, mostly of therapy groups, not work teams.
- Later research does not find that teams reliably pass through these stages in this order. Connie Gersick's punctuated equilibrium findings suggest teams instead maintain an initial pattern until roughly the temporal midpoint of a project, then undergo a sharp transition.
- Modern teams rarely have the stable membership the model assumes; people join and leave continuously, and "the team" is a moving object.
Evidence: weak. See evidence-based-practice.
What to use it for anyway
The one genuinely useful message: early conflict in a new team is normal and is not evidence of a wrong hire or a bad team. That message prevents real damage, and it is worth the model's continued use.
Beyond that, prefer models with better support:
- psychological-safety — what actually predicts team learning.
- google-project-aristotle — what predicted effectiveness in a large sample.
- drexler-sibbet-team-performance-model — more actionable, question-based, and diagnostic.
- lencioni-five-dysfunctions-of-a-team — also weakly evidenced, but more directly prescriptive.
Examples by audience
Health care: rotating junior staff mean many clinical teams re-form every few months and never leave forming. The remedy is not stage management; it is explicit, fast onboarding of norms — a written team charter, an introduction ritual, and a named person to ask.
Software: a newly formed squad arguing about branching strategy in week two is storming, and is fine. A squad still arguing about it in month six has an unresolved decision-rights problem, not a stage problem.
Executive: a new executive team's storming is expensive and public. Accelerate it deliberately with a facilitated chartering session — surface the conflicts on purpose rather than waiting for them to emerge in front of the organization.
Practical alternative: charter instead of stage-watch
Rather than waiting for stages, run a chartering session in week one:
- Purpose: why does this team exist, and what happens if it does not?
- Success: how will we know, by when?
- Roles: who decides what, and who must be consulted?
- Norms: meetings, response times, disagreement, escalation.
- Review: when do we revisit this? Put the date in the calendar now.