Organization Explore
Tuckman's Stages
Tuckman's stages are forming, storming, norming, performing, and adjourning: a map of how a group becomes a team, and then ends.
The questionWhat is this group working through right now, and is it stuck there?
Also called the Tuckman ladder. Adjourning was added in 1977, so older sources list four stages.
- 1 Forming Polite and cautious
- 2 Storming Disagreement comes out
- 3 Norming Roles and habits settle
- 4 Performing Work gets done
- 5 Adjourning The group breaks up
When to use it
- A project team has just been assembled from several departments and you are deciding how much structure to impose early.
- A sponsor wants to know whether the arguments in a three-month-old team are normal or a sign of a bad fit.
- A new leader has joined an established team and the team seems to have gone backward.
- You are planning a kickoff or an offsite and need a vocabulary the sponsor already recognizes.
When to avoid it
- The trouble is one broken relationship or one person's performance. A stage label hides it.
- You need evidence of team effectiveness. The stages are a way of describing behavior, not a measurement.
- The group is large, spread across sites, or changes membership constantly. It may never stay together long enough to move through anything.
- A staffing decision needs support. A claim that the team is in storming is not evidence about any individual.
Overview
Tuckman’s stages describe how a small group tends to change as it works together: forming, storming, norming, performing, and later adjourning. The model supports a practical choice. When a team is in friction, you decide whether it is a development issue that needs a settled question about authority or method, or something that needs a different diagnosis.
The 1965 paper was a review of fifty published studies, mostly of therapy and training groups, and Tuckman presented the sequence as hypotheses. Groups do not march through on a schedule. A new member, a new leader, or a change in scope can send a team back to an earlier stage, so a stage label is a working guess about one group on one day.
The stages
Forming
Members are polite and cautious. They ask what the task is, what the rules are, and who is in charge, and they look to the leader or to existing norms for direction. Conflict is mostly avoided. What helps is a clear purpose, stated boundaries, and decision rights that are written down.
Storming
Disagreement comes into the open. It is often about authority, method, or workload, and it can be personal. Some members push back on the leader, and some withdraw. What helps is working through the specific disputes. Suppressing them tends to postpone them.
Norming
The group settles how it will work together. Roles, meeting habits, and ways of handling disagreement become routine. The risk is that agreement is bought by avoiding hard topics. A test is what happens to the first serious dissent.
Performing
The group makes decisions and gets work done with little help from the leader, and it handles disagreement without losing momentum. A leader's job here is mostly removing obstacles.
Adjourning
The work ends and the group breaks up. Members may feel pride, loss, or both. What helps is a deliberate close, with a handover, a retrospective, and a recognition that the group is over. Many organizations skip it and move people straight to the next project.
What it is not
- A schedule. Teams do not move through the stages on a calendar. Some skip a visible storming stage, some stay in one stage for months, and many move backward when membership or scope changes.
- A finding about work teams. The 1965 review drew on therapy and training groups, and the author called the model a set of hypotheses.
The steps
-
Describe the group and its history
Note who is in it, how long they have worked together, and what has changed recently, such as a new member, a new leader, or a new scope. A significant change can reset the group to an earlier stage. What comes out is a one-paragraph description of the group.
-
Watch behavior, not mood
Sit in two or three meetings and note who speaks to whom, who defers, how disagreement is handled, and what happens to dissent. Add a short conversation with each member. What comes out is a log of observed behavior with examples.
-
Treat the stage as a hypothesis
Match behavior to stages loosely. Courtesy and rule-seeking point to forming. Open disputes about authority or method point to storming. Settled routines with little disagreement point to norming, or to avoidance. Decisions made without the leader, with dissent handled, point to performing. Write down what fits and what does not. A mixed picture is normal.
-
Choose what the group needs
For forming, supply purpose, boundaries, and decision rights. For storming, settle the specific disputes about authority and method. For norming, test whether the agreement is real by raising a hard topic. For performing, remove obstacles. For adjourning, plan a deliberate close. What comes out is one or two interventions matched to what you observed.
-
Recheck after any disruption
A new member, a new leader, a change of scope, or a sudden deadline can send the group back. Set a date to look again, and list the events that would call for an earlier look.
In practice
Seven weeks in, the sponsor sent the consultant a one-line message asking for the project lead to be replaced because the team was dysfunctional. Eleven people from finance, IT, and procurement had been put together to replace a billing system. The consultant sat in two meetings. Early on, people had been courteous and mostly silent, and that fit forming. In weeks four to six, they had argued repeatedly about who had the right to approve the cutover criteria, which fit storming.
The consultant asked what the fight was about. Nobody had told the team who decided. Waiting for the team to work through it was a poor option, because the dispute was about authority that had not been assigned and would not resolve itself. The consultant asked the sponsor to settle decision rights in one meeting and put them on a single page. Within two weeks the arguments moved to technical questions about data conversion, and the project lead stayed.
What you leave with
- A written description of the group's observed behavior, with examples.
- A working hypothesis about its stage, with the observations that support it and those that do not.
- One or two interventions matched to the hypothesis, such as decision rights settled or ground rules agreed.
- A list of events that would reset the group, and a date to look again.
Failure points
Waiting for storming to pass
Sponsors tell the team to work it out. If the dispute is about authority that nobody assigned, it will keep returning until someone settles it.
Labeling a person
Someone becomes a storming type, or the team's difficult member. The stages describe a group's behavior, and a label attached to a person closes off the conversation about what the person was reacting to.
Reading quiet as norming
A team that does not disagree may be afraid to, or may not yet trust enough to try. The test is how dissent is treated when it appears.
Developing a team that is not one
People whose work runs in parallel with little interdependence do not need team development. The effort goes into building cohesion that the work does not call for.
Ignoring resets
A new leader arrives, and the engagement keeps treating the team as performing. Behavior that looks like regression is the normal response to a change in leadership or membership.
The failures above are usually Presence: the framework was sound, but the attention of the stakeholders was not held.
Origin
Bruce Tuckman, then at the Naval Medical Research Institute in Maryland, reviewed 50 published articles on how groups change over time. The studies covered therapy groups, training groups known as T-groups, and a mix of natural and laboratory groups. He sorted the stages the authors described into a social realm and a task realm, proposed four general stages, and fitted the literature to them. He coined the terms forming, storming, norming, and performing. The paper presents the model as a set of hypotheses reflecting his own reading of the studies and subject to further test. By his own later account, the journal's editor first doubted the quality of the underlying studies, and Tuckman answered that he was drawing inferences from them, not endorsing them.
In 1977 Tuckman and Mary Ann Jensen reviewed 22 later studies, concluded that groups also go through a separation at the end, and added adjourning. The model is published scholarship with no trademark. The 1965 review was not a study of work teams in organizations, which matters when a client treats the stages as established fact about teams.
Further reading
- Developmental sequence in small groups
Tuckman's 1965 paper in Psychological Bulletin, as a free copy hosted on an MIT course site that may move. The method and the cautious language about hypotheses are worth reading. The journal version is paywalled.
- Citation Classic commentary on the 1965 paper
Tuckman's own one-page account of how he assembled the review, how it was nearly rejected, and why the terms caught on. Free PDF.
- Tuckman's stages of group development (Wikipedia)
An overview of the stages, the 1977 addition, and later variants. Use it for orientation and follow its references.
Last updated