Org, people & execution
Tuckman's Stages of Group Development
A five-stage account of how small groups develop: forming, storming, norming, performing and adjourning. Each stage pairs a relationship problem with a task problem, giving leaders a language for why a capable team is not yet delivering and what the current stage needs from them.
Also known as Forming-storming-norming-performing, Tuckman model. First set out by Bruce W. Tuckman in 1965; the primary source is cited in full below.
Where this is contested
The famous five-stage version is a composite: Tuckman's 1965 paper proposed four stages from a review of studies dominated by therapy and laboratory groups, and 'adjourning' was added only in the 1977 review with Jensen. Tuckman himself presented the sequence as a hypothesis in need of testing, not an established law of teams.
- Format
- Process / loop
- Level
- Team
- Best for
- Plan execution
- Decision stage
- Diagnose · Execute · Review
- Difficulty
- Introductory
- Time to apply
- An hour to locate a team's stage and adjust approach; applying it well spans the team's whole life, from kick-off to deliberate closure.
Plate · The model
The components
Forming
Orientation and testing. Members establish what the task is, how they fit, and what behaviour is acceptable, while depending heavily on the leader for direction.
Signals of strength
Politeness and guarded contributions · Frequent questions about purpose, scope and roles · High dependence on the designated leader
Storming
Conflict and polarisation around interpersonal issues, and emotional resistance to task demands. Members contest roles, methods and influence as real differences surface.
Signals of strength
Challenges to the leader and to each other's roles · Arguments about method that carry more heat than the topic warrants · Subgroups and alliances forming
Norming
Cohesion develops: the group settles roles, standards and ways of working, and open exchange of views becomes possible. Resistance is overcome and in-group feeling emerges.
Signals of strength
Agreed working practices actually being followed · Disagreement expressed without relationship damage · Members covering for and helping each other unprompted
Performing
Structure becomes functional: roles are flexible, energy flows into the task, and the group solves problems without constant leader mediation.
Signals of strength
Problems resolved inside the team without escalation · Roles flexing to fit the work rather than the org chart · Output and quality visibly compounding
Adjourning
The ending stage added in 1977: the group completes its task, disbands and deals with separation, including recognition, learning capture and, often, real loss.
Signals of strength
Wind-down anxiety or premature disengagement as the end nears · Nostalgia and stocktaking conversations · Attention turning to next assignments before the work is done
When it earns its keep
- You are assembling a new team under deadline and want to anticipate the friction that follows the polite early weeks rather than be surprised by it.
- A team is conflicted or underperforming and you need a diagnostic frame: is this destructive dysfunction, or ordinary storming that needs steering rather than suppressing?
- Membership or leadership has changed materially, which typically sends an established team back through earlier dynamics.
- A team is disbanding after intense work, and the adjourning stage argues for deliberate closure, capturing lessons and marking the end, rather than quiet dispersal.
And when it doesn't
- As a project plan. The stages describe tendencies observed across studies, not a timetable; scheduling 'storming week' misreads the model's status as description rather than prescription.
- For deadline-driven project teams specifically, evidence favours punctuated equilibrium: long inertia broken by a sharp transition near the temporal midpoint, which the stage sequence does not capture.
- When the problem is structural, unclear goals, missing skills or impossible resourcing. Labelling a resourcing fight as 'storming' normalises a problem that needs a management decision.
- For fluid, constantly reforming groups, where membership churn means the group never has a stable identity to develop.
How to run it
Before starting, gather the inputs the analysis depends on:
- A defined team with reasonably stable membership and a shared task, since the model assumes a group with boundaries.
- Honest observation of current behaviour: how conflict is handled, how decisions get made, how much energy goes to task versus interpersonal issues.
- The team's history, including recent changes in membership, leadership or mandate that may have reset its development.
- A leader or facilitator willing to adapt their style by stage, since the model's practical payload is that different stages need different leadership.
- 1
Locate the team's current stage
Read the behaviour, not the calendar. Tuckman's stages each pair an interpersonal dynamic with a task dynamic: orientation and testing in forming, conflict and emotional response to task demands in storming, cohesion and open exchange in norming, functional role-relatedness in performing. Teams do not announce their stage; infer it from how conflict and work are actually being handled.
- 2
Match leadership to the stage
Forming needs direction, clarity of purpose and ground rules. Storming needs steady facilitation that keeps conflict on issues rather than persons, and resists the urge to shut disagreement down. Norming needs consolidation, standards and delegation. Performing needs the leader to get out of the way and manage the boundary. The model's practical value is mostly here.
- 3
Work through storming rather than around it
Treat conflict over roles, methods and influence as developmental work the team must do. Suppressed storming resurfaces as passive resistance in norming; equally, a team stuck in storming for months is not developing, and needs intervention on the actual disputes, often about roles and decision rights.
- 4
Watch for regression and re-entry
Development is not one-way. New members, a new leader, a changed mandate or a shock will send a performing team back through earlier dynamics. Expect to re-run forming rituals whenever composition changes materially.
- 5
Close deliberately
For temporary teams, plan the adjourning stage: acknowledge the ending, capture what was learned, recognise contributions and release people well. Tuckman and Jensen added the stage in 1977 because separation is real group work, with real feelings attached, and unmanaged endings squander both learning and goodwill.
Reading the result
A diagnosis of where the team currently sits, a leadership approach matched to that stage, and realistic expectations about the friction that precedes performance, plus a deliberate plan for endings on temporary teams.
- Use the stages as a vocabulary and a rough map, not a schedule. The claim worth keeping is that conflict is a normal developmental phase, not evidence the team is broken.
- Judge stage by observed conflict-handling and task behaviour, not by elapsed time; teams can stall, skip and regress.
- If a deadline-driven team shows long inertia then a midpoint jolt, read it through Gersick's punctuated equilibrium instead and use the midpoint as the intervention window.
A worked example
An architecture practice assembles a design team for a stadium bid
A 60-person London architecture practice forms an eight-strong team for a twelve-week stadium design competition: two senior architects with equal claim to design leadership, three project architects, a structural engineer seconded from a partner firm, a visualiser and a bid manager. The practice director uses Tuckman's model to anticipate the team's dynamics across the bid.
- Forming
- Weeks one and two are productive-looking but shallow: enthusiastic reference-gathering, polite workshops, nobody contesting anything. The director reads this as classic forming and invests in it deliberately, a clear brief, decision rights on paper (one senior architect leads design, the other leads client interface), and ground rules for design reviews.
- Storming
- Weeks three to five deliver the predicted conflict: the two seniors clash over a timber-roof concept versus a retractable scheme, the engineer is accused of killing ideas too early, and the visualiser is caught between competing instructions. Because storming was expected, the director does not panic or suppress it; she chairs a structured concept shoot-out with agreed criteria, and the roof dispute is settled on evidence rather than seniority.
- Norming
- By week six the team has settled real norms: engineering joins concept sessions from the start rather than reviewing after, design crits run twice weekly with the criteria from the shoot-out, and the second senior fully owns the client story. The bid manager notes the tell-tale sign of norming: disagreements now end with a decision and lunch, not a corridor campaign.
- Performing
- Weeks seven to eleven produce the best work: the team iterates the design across disciplines quickly, hands tasks across roles without ceremony, and self-corrects a costing error without the director ever hearing about it until it was fixed. Her job shrinks to protecting the team from partner interference and scope creep from the client's advisers.
- Adjourning
- The bid is submitted in week twelve; the result is months away. The director closes deliberately: a retrospective capturing what the crit format and early-engineering norm did for quality, written recognition into each member's review file, and a plan to reuse the pairing of the two seniors, which nearly failed in week four and became the bid's engine. The seconded engineer leaves with an agreed route back for future bids.
The read. The model earned its keep twice: it stopped the director treating week-four conflict as failure, and it made the ending a designed event rather than a dispersal. The honest caveat is that the team's trajectory also fitted Gersick's midpoint pattern, the real design breakthrough came in week six of twelve, and the stages did nothing to predict that timing. Tuckman gave the vocabulary for the friction; the calendar, as much as the stages, drove the work.
Pitfalls
- Treating the sequence as a law. Real teams stall, skip stages, regress and loop; the model describes common tendencies, not a guaranteed path.
- Using 'storming' as a euphemism that normalises genuine dysfunction, bullying, structural conflict or a wrong hire, which need intervention, not patience.
- Assuming performing is permanent. Any material change in membership, leadership or mandate can send the team backwards, and often should.
- Forgetting adjourning entirely, so temporary teams end by evaporation, losing lessons and leaving people flat.
- Applying the model to large organisations or loose networks. It was derived from small-group studies and its claims do not scale.
What the critics say
Gersick's field study of eight naturally occurring project teams found no universal stage sequence at all: teams framed their approach in the first meeting, persisted through a long inertial phase, then transformed abruptly at the temporal midpoint of their deadline, a punctuated-equilibrium pattern that directly contradicts a gradual linear progression.
Gersick, C. J. G. (1988) 'Time and transition in work teams: toward a new model of group development', Academy of Management Journal, 31(1), pp. 9-41.
The model was built from a literature review dominated by therapy and T-groups rather than work teams, and later reviews note that longitudinal empirical tests of the fixed sequence remain thin; the model's endurance owes more to its intuitive appeal and usefulness as a vocabulary than to strong predictive evidence.
Bonebright, D. A. (2010) '40 years of storming: a historical review of Tuckman's model of small group development', Human Resource Development International, 13(1), pp. 111-120.
Practitioner-facing reviews have proposed revised models because observed groups frequently fail to storm at all, storm late, or cycle between stages, suggesting the stages are better read as recurring issues every group must manage than as an ordered developmental sequence.
Cassidy, K. (2007) 'Tuckman revisited: proposing a new model of group development for practitioners', Journal of Experiential Education, 29(3), pp. 413-417.
Sources and further reading
- Tuckman, B. W. (1965) 'Developmental sequence in small groups', Psychological Bulletin, 63(6), pp. 384-399. ↗
- Tuckman, B. W. and Jensen, M. A. C. (1977) 'Stages of small-group development revisited', Group & Organization Studies, 2(4), pp. 419-427. ↗
- Gersick, C. J. G. (1988) 'Time and transition in work teams: toward a new model of group development', Academy of Management Journal, 31(1), pp. 9-41.
- Bonebright, D. A. (2010) '40 years of storming: a historical review of Tuckman's model of small group development', Human Resource Development International, 13(1), pp. 111-120. ↗