Tuckman’s Five Stages of Team Development
Bruce Tuckman’s model describing how teams evolve from a disparate group of people into a high-functioning unit. Teams don’t always progress linearly and can revisit earlier stages.
The five stages
1. Forming
- Team members get to know each other
- Roles, norms, and project context are unclear
- PM’s job: clarify project goals, roles, and context
2. Storming
- Frustrations emerge as real work begins
- Individuals take issue with processes they find inefficient or teammates they disagree with
- Particularly intense when tasks turn out to be more complex than they first appeared
- PM’s job: focus on conflict resolution, listen as the team addresses problems, share insights on how the team can function better as a unit
3. Norming
- Most conflict is resolved
- The team is working together
- PM’s job: codify team norms, make sure the team is aware of them, reinforce when needed
4. Performing
- Team works together seamlessly
- High trust, high productivity
- PM’s job: delegate, motivate, provide feedback to keep momentum
5. Adjourning
- Project wraps up
- Team disbands
- PM’s job: celebrate final milestones and successes; conduct formal retrospective
Application
- New team? Expect forming. Don’t skip the introductions and clarity work.
- Conflict suddenly appearing after a scope change or new joiner? Storming. Don’t suppress it — work through it.
- Team suddenly going quiet and calm after weeks of friction? Norming. Capture the norms before they fade.
- Teams can regress — a new team member, a leadership change, or a major scope shift can push a performing team back to storming.
Connections
- course-4-project-execution
- change-management — major changes can trigger regression
- scrum-framework — Scrum teams go through the same stages, usually faster due to tight feedback loops