Tuckman's stages: forming, storming, norming, performing
A new project team is polite and guarded for the first few weeks. Then the friction starts: debates about ways of working, turf marking, irritation. Many project managers read this as a sign that something has gone wrong. More often it is the opposite – a sign that the team is developing exactly the way teams usually do.
In 1965, psychologist Bruce Tuckman reviewed a large body of studies on how groups develop over time and summarised the pattern in a model that has become one of the best known in team research: forming, storming, norming and performing. More than sixty years later, it is still the most widely used map for understanding where a team stands – and therefore what it needs from its leader right now.
What does the research say?
Tuckman's review showed that groups tend to move through four stages of development. In forming, members are polite and uncertain; everyone is finding their role and testing what the rules are. In storming, the tensions break through: disagreement about goals, ways of working and influence. In norming, the group settles on shared ground rules and an identity of its own. Only in performing can the group put its full energy into the task instead of into managing its internal dynamics.
Tuckman later added a fifth stage – in 1977, together with Mary Ann Jensen: adjourning, when the group dissolves. Every project manager will recognise it, since projects by definition come to an end.
Two things are important to know. First, the model is a simplification: real teams jump back and forth, and a change such as a new member or a new mission can throw a mature team back into earlier stages. Second, the order of the stages is a tendency, not a guarantee; some teams get stuck in storming, or skirt around it without resolving anything. The model's value lies in helping the leader make the right diagnosis: different stages call for different leadership.
What does this mean for you as a project manager?
Adapt your leadership to the stage. A team in forming needs structure and clarity: roles, goals, ways of working. The same close direction in performing comes across as distrust. Regularly ask yourself where the team is and whether your way of leading matches that – rather than your own comfort.
Don't be afraid of the storming stage. Friction over ways of working and influence is a normal step in development, not a failure. Your job is not to suppress the conflicts but to make them manageable: bring them to the surface, keep them factual and steer them towards shared ground rules. Teams that are never allowed to really storm often end up polite but mediocre.
Expect restarts. Every time the team's composition or mission changes, parts of the journey begin again. Plan for it: a short reset covering roles and expectations when a key person is replaced is cheaper than months of silent friction.
How to practise this
The hard part is not knowing the names of the stages but acting well in the moment: facing a team meeting in full storming mode without either ducking or taking over. Situations like these can be practised. In Project-simulator you face team and group situations where the right move depends on where the group stands, and you get feedback on how you handled them. Try it free for a week.
In Project-simulator you practice these conversations against an AI counterpart and get feedback grounded in research like this.
Try free for 7 days