Wheelan's model: how teams develop in four stages
Why does the same leadership style work brilliantly in one team and terribly in another? Psychology researcher Susan Wheelan spent decades studying work groups and arrived at an answer: groups mature in predictable stages, and the leadership that helps a group in one stage can hold it back in another.
Her book Group Processes: A Developmental Perspective summarizes this research in a model that has become widely used, not least in Sweden. For anyone leading project teams, it is a practical tool for reading where the group currently stands — and choosing the right intervention at the right time, instead of applying the same leadership style regardless of the situation.
What does the research say?
Wheelan's model is known as the Integrated Model of Group Development. It builds on earlier group research and describes four stages plus an ending. In the first stage, dependency and inclusion, members are polite, cautious and dependent on the leader — they are looking for answers about whether they fit in and what is expected of them. In the second stage, counterdependency and fight, members begin to challenge the leader and each other. It sounds unpleasant, but according to Wheelan it is a necessary step: the group is negotiating roles, goals and ways of working.
If the conflicts are handled openly, the group reaches the third stage, trust and structure, where roles become clearer and communication grows more open and matter-of-fact. Only in the fourth stage, work and productivity, does the group devote most of its energy to the task itself rather than to internal dynamics. Groups that disband also go through a termination stage that is worth handling deliberately — especially in projects, where teams are by definition temporary and endings are part of everyday life.
The model's most important point for leaders: adapt your behavior to the stage. Early on, the group needs structure, clear goals and a present leader. Later, it needs space, delegation and trust instead. Wheelan also showed that groups do not automatically move forward — they can get stuck in a stage, and they can slip back when conditions change, for example when members are replaced.
What does this mean for you as a project manager?
At kickoff: provide structure without apologizing for it. A new project team in stage one needs clear goals, roles and ground rules. Expecting self-directed team members from day one is asking a stage-one group for stage-four behavior.
When conflict arrives: don't panic. Pushback and friction after a few weeks are often a sign of development, not failure. Bring the issues into the open, let different perspectives clash and keep the goal in focus — sweeping the conflict under the rug is what makes groups get stuck.
When things change: expect the group to regress. When a key person leaves or new members join, the group often slides back toward earlier stages. Redo the inclusion work: introduce people, clarify roles and rebuild psychological safety, instead of wondering why productivity has dipped.
How to practice this
Knowing the stages is one thing — leading well in the middle of a kickoff or a group conflict is another. In Project-simulator you practice team conversations with AI counterparts that behave like real group members in different stages, in a safe environment where nothing can truly break, and get feedback grounded in what you actually said. You can 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