Tuckman’s 5 Stages of Team Development
Tuckman's Stages of Team Development
What are Tuckman’s five stages of team development?
- Forming → Storming → Norming → Performing → Adjourning
- Conflict (storming) is a natural part of growth
- Leaders need to adapt to each stage
The practical value of this model is that it turns the question “Is this team broken right now?” into “Which stage is this team in right now?” When a manager takes over a newly formed unit and voices get raised at every meeting three months in, most people blame individuals or doubt their own leadership. Seen through the stages, that is a typical symptom of storming, and what is needed is not a personnel action but a facilitation approach that brings conflict onto the table. Conversely, telling a team in the forming stage to “go ahead and work it out on your own” leads to nothing happening. The same delegation can be the right answer or plain neglect, depending on the stage.
Teams move between stages based on conditions, not time. To get from forming to storming, a team needs enough safety for real disagreements to surface. To get from storming to norming, it needs agreed rules for how “our team makes decisions.” That is why a team with no storming is often not a good team, but one stuck in forming because conflict never came to the surface. This is called “false norming.” On the surface it is quiet and meetings wrap up in 20 minutes, but objections burst out late, during execution. Another point to keep in mind is that the stages are not one-directional. If one member is replaced or the goal changes, even a performing team can slide back into storming.
The most common misconception in practice is treating this model as reassurance that “things will get better eventually.” A team will not reach the performing stage just by waiting. In a team that leaves storming unaddressed, conflict does not get resolved; it goes underground and settles into gossip and passive resistance. Conversely, if a leader declares “our team is in the performing stage now,” legitimate concerns raised afterward get treated as “remarks that hurt teamwork.” A team’s stage should not be diagnosed by the leader alone; confirm it by asking team members.
Yeonmi SongSpecialist instructor and coach in relationship management, resilience, and self-leadership
John KimInstructor John Kim, CEO of Nanum Consulting and author of “B2B Marketing Design”Psychologist Bruce Tuckman proposed four stages in 1965 and later added the adjourning stage.
Consider a hypothetical case. Company A, an industrial parts manufacturer with 90 employees, formed a task force of eight people drawn from production, IT, and quality to introduce a new smart factory. Three months after launch, they had not gotten past a single kickoff report. In weekly meetings, the production and IT teams spent a full 45 minutes trading accusations: “You don’t understand the shop floor,” and “The requirements change every time.” Director Park of Production Engineering, the task force lead, had already asked senior management whether to send two team members back to their original departments.
- An outside coach interviewed all 8 members individually, and 5 of them said, 'I don’t know what the IT team actually does.' The coach told Director Park, 'This is not a people problem; it is the storming stage, with the forming work left undone.'
- Director Park ran a half-day workshop and had everyone write their home-department KPIs and the hours per week they could give this task force on the whiteboard. When Manager Kim from IT said, 'I can only spare 8 hours a week, yet meetings are called every day,' the clash in expectations surfaced for the first time.
- Instead of burying the conflict, they put it on the agenda and set a rule: requirement changes are accepted only on Wednesdays, once a week, and anything else rolls over to the next cycle. Manager Lee from Quality opposed it, but they agreed on the condition of “a two-week trial, then revisit.”
- They also put the decision-making process in writing. The IT team lead makes the final call on technical questions, and the production team lead decides whether to apply something on the shop floor. If no conclusion is reached within 30 minutes, Director Park cuts the discussion off. After that, the average weekly meeting dropped from 45 minutes to 22 minutes.
- In month 5, one line owner was replaced and the mood in meetings turned sour again. Saying 'with a new member, we go back to forming,' Director Park added one session to share roles and expectations, and within 2 weeks the team recovered its earlier pace.
- Nine months after launch, the task force completed the first line rollout. It was two months behind the original plan, but no one dropped out, and in the closing survey, 7 of the 8 members said they would join this task force again.