What the team development stage test shows
The team development stage test helps you judge which stage of development your team is currently in. It is based on the best-known model of team development. In 1965, the American psychologist Bruce Tuckman described four stages in a review of research on small groups: forming, storming, norming and performing. In 1977, together with Mary Ann Jensen, he added a fifth stage, adjourning, for the point at which a group comes to an end.
The twelve questions describe situations from everyday team life: how meetings run, how you deal with disagreement, how clear roles are and what part the team lead is playing right now. Every answer counts towards one stage. At the end you see not only the strongest stage but the whole spread. That matters, because real teams rarely sit neatly in a single stage. A team that works well overall, for example, may still hit friction again when a new topic comes up.
The test is not a grade for your team. No stage is bad – each one has its own job to do. A team in the storming stage is not doing anything wrong. It is working out how it wants to work together. The result is most useful for choosing the right kind of support: a team that is forming needs something different from a team that is about to break up.
The five stages at a glance
Each stage has typical signs and a typical question on the team’s mind. The overview below sums up the model briefly.
The English stage names are used in many languages, often alongside local terms. The important thing is that the stages describe the team as a whole, not individual people. A new member may still be finding their feet while the team as a whole has long been working smoothly – in that case it is mainly that person who needs support, not the whole team.
- Forming – orientation: people are polite and cautious, get to know each other and look to the leader for direction. The key question: who are the others, and what is our goal?
- Storming – friction: different expectations, working styles and ambitions collide. The key question: who decides what, and whose way wins?
- Norming – finding the rules: the team agrees on processes, roles and ways of working, and a sense of “we” develops. The key question: how do we want to work together?
- Performing – high performance: the team works smoothly, flexibly and largely on its own. The key question: how do we reach the next goal?
- Adjourning – closure: a project ends, the team disbands or changes significantly. The key question: how do we finish well, and what do we take with us?
Why teams move back and forth between stages
Tuckman described the stages as a sequence, but in practice development rarely runs on rails. Teams slip back, seem to skip a stage or get stuck in one for longer. Common triggers for slipping back are new team members, a change of leader, a new goal or a reorganisation. Even a single new person can send a well-established team back into forming or storming for a few weeks, because roles and habits are being renegotiated.
The size and type of team matter too. A small project team with a clear deadline sometimes moves through all the stages in a few weeks, while a large permanent team takes months. Other researchers have therefore proposed complementary models. In the late 1980s, Connie Gersick described how project groups tend to progress in leaps – with a long, steady period and a clear turning point roughly halfway through the time available. Tuckman’s model is still useful, because it gives teams a shared language for what is happening right now.
What leaders can do at each stage
Depending on the stage, a team needs a different kind of leadership. A rough guide: lots of direction at the start, then more and more trust and freedom. A leader who still dictates every detail when the team is performing slows it down. A leader who only facilitates too early in forming leaves the team without orientation.
- Forming: state the goal, the framework and the first roles clearly, make room for people to get to know each other, and explicitly welcome questions.
- Storming: address conflicts openly and factually rather than suppressing them, make decision-making transparent, and agree on fair ground rules for discussions.
- Norming: write down agreements, hand responsibility to the team step by step, and make early shared successes visible.
- Performing: clear obstacles out of the way, give the team freedom, offer new challenges and recognise good work.
- Adjourning: celebrate what has been achieved, capture knowledge, clarify the next step for each person and plan a deliberate ending.
How to use your result as a team
The test is most revealing when several people take it independently. Ask your team to complete it, then compare only the results in a short meeting, without names. If the team lead sees the team as performing while several members see it as storming, that very difference is the most important thing to talk about.
Three questions help here. How do we recognise our stage in everyday work? What do we need now to move forward well? And what do we want to try out concretely over the next few weeks? Stick to one or two small actions, such as a team agreement, clearer roles or a regular retrospective. After a few weeks you can repeat the test and see whether the spread has shifted.
One important point: do not use the result to judge individuals or assign blame. A team in the storming stage above all needs a safe space in which differences can be voiced openly.
Team events that fit the stage
A shared experience can support a stage, but it does not replace work on goals, roles and conflicts. In forming, formats where everyone gets to know each other in mixed groups work well. When moving from storming to norming, a task that can only be solved together can help people experience how different strengths fit together. In performing, an event is often a reward, and in adjourning a fitting farewell.
At Secret Mission in Vienna, a team works together on a case with professional actors at real locations. Because the information is spread out and only comes together through exchange, it often shows, almost in passing, how the team is working together right now – a good starting point for talking about your own stage afterwards.