Tuckman and team development. How teams grow into performance

Projects often place most of their attention on planning, risks, budget, and decision making. That makes sense. Yet the content side of a project is only part of the story. The way a team develops, works together, and handles tension has a major impact on the outcome as well.

That is why the Tuckman-model still matters.

It describes team development as a progression through five phases: forming, storming, norming, performing, and adjourning. Each phase comes with its own dynamics, and recognizing those dynamics helps project leaders guide teams more effectively. In practice, this is not a theoretical model that belongs in a textbook. It is a useful lens for understanding what a team needs at a given moment and what may be holding it back.

A project team is not automatically a team

People can be assigned to the same initiative and still not function as a team.

That happens all the time in projects. People come together from different disciplines, business units, vendors, or technical domains. They may not know each other. They may have different priorities. They may even bring old frustrations or hidden tensions with them. In that situation, a group can still deliver work, but that does not mean it has become a real team.

That gap matters. It costs energy, creates friction, and often puts extra pressure on the project manager. Work still gets done, but more through effort and coordination than through real teamwork.

The five phases of Tuckman

The strength of Tuckman lies in its simplicity. It shows that teams usually do not start in a mature state. They grow into one.

• Forming: In the forming phase, people are still finding their place. They look for clarity, structure, and direction. Roles are not fully settled yet, and people are often somewhat cautious in how they interact.
• Storming: Storming is the phase in which tension starts to surface. Differences in style, expectations, pace, responsibility, or interpretation become more visible. This is the phase where conflict, irritation, or mistrust may emerge.
• Norming: In norming, the team begins to settle. People start understanding each other better. Working agreements become clearer. Roles are accepted more easily, and a sense of rhythm starts to develop.
• Performing: In the performing phase, the team begins to function as a real unit. People work with each other instead of around each other. Problems are solved more naturally, collaboration becomes smoother, and energy can go into results rather than internal friction.
• Adjourning: Finally, there is adjourning, the phase in which the team dissolves because the project ends or a major stage is completed. That phase deserves attention too, even though it is often overlooked in practice.

Storming is not a sign of failure

One of the most important lessons in the Tuckman model is that storming should not automatically be seen as a bad sign.

In many projects, tension is treated as something that should be avoided or smoothed over as quickly as possible. That often creates the illusion of calm, while the real issues stay under the surface. Those issues usually return later, often in a more disruptive form.

Storming is uncomfortable, but it is also normal. A team that never has friction may simply not be surfacing the differences that matter. That makes the role of the project leader important. The task is not to suppress every sign of tension, but to help the team move through it in a productive way.

Teamwork requires a shift in focus

Teams usually become stronger when people stop seeing the work only as their own individual task and start recognizing the shared task of the team.

That sounds simple, but it is one of the harder shifts to make. People need to understand not only what they themselves are doing, but also how their work affects others, where dependencies sit, and what the team as a whole is trying to accomplish.

This is where project leadership becomes more than task coordination. A project manager helps make those interdependencies visible and helps the team understand that collaboration is not a side issue. It is part of the work itself.

Leadership needs to change with the phase

Another reason the Tuckman model remains so practical is that it shows why one leadership style does not fit every phase of team development.

In forming, teams often need more direction and clarity. In storming, they usually need active guidance, confidence, and someone willing to make tension discussable. In norming, leadership often shifts more toward enabling and strengthening cooperation. In performing, teams usually benefit from more space and less close control.

That means strong project leadership is not static. It adjusts to the maturity and the needs of the team.

What this looks like in practice

In practice, teams move faster when the project manager actively pays attention to how the team is forming, not just to what the team is producing.

That may mean starting the group well, creating room for people to get to know each other, making roles clearer earlier, and naming tension when it arises instead of pretending it is not there. It may also mean changing the way work is organized if the current setup is reinforcing friction rather than reducing it.

Sometimes even naming the phase helps. When people understand that tension is part of development rather than proof that the team is failing, the atmosphere often changes. Conflict becomes easier to discuss, and the team can focus more on how to move forward.

Team building is not a side activity

Team building is often treated as something separate from the real work, almost as if it were an optional extra.

In reality, it is part of the work. A team grows through repeated interaction, shared experiences, reflection, and the way collaboration is shaped over time. That can include kickoffs, working agreements, retrospective moments, informal sessions, or targeted interventions when a team gets stuck.

The point is not to organize a single symbolic activity and assume the team is now strong. Team development is continuous. It needs attention throughout the life of the project.

Why this matters for Quilyx

At Quilyx, we do not look only at planning, structure, and reporting. A project team also has to function as a team.

That is why Tuckman is useful. It helps identify where a team is, what kind of tension is normal, what kind of support is needed, and where leadership has to adapt. It also helps avoid a common mistake: assuming that because work is moving, the team must be healthy.

That is not always true. A team can still be productive while carrying unnecessary friction. Over time, that usually becomes visible in quality, pace, ownership, or trust.

Strong team development supports predictability, because teams that work well together usually create fewer surprises. It strengthens ownership, because people more readily take responsibility when the team feels safe and clear. And it supports calm, because less energy is wasted on hidden friction and avoidable tension.

A project that wants to perform at a high level cannot afford to ignore how its team is developing.