What is it?
The Stages of Team Development model helps a group recognise the changing needs that appear as people form, test boundaries, establish working agreements and become effective together.
What's it really for?
It is really for normalising some of the awkwardness of becoming a team without excusing poor behaviour. Friction may be part of the work of learning how to disagree, decide and depend on one another.
You know when…
The team was launched with a workshop, a photograph and matching lanyards. Two weeks later decisions are being revisited, roles overlap and polite meetings are followed by less polite corridor conversations.
Have a go
- Ask what the team is currently trying to work out: belonging, influence, agreements or delivery. ☐ Compare observations rather than labelling people. ☐ Make purpose, roles and decision rules explicit. ☐ Create space for constructive disagreement. ☐ Revisit the diagnosis after membership or conditions change.
Why it works
Teams behave differently as relationships, roles and expectations develop. Naming the stage gives leaders a more useful response than treating uncertainty, conflict or dependence as a fixed flaw in the people.
Look for…
Dependence on the leader, unspoken tests of authority, recurring conflict, emerging working agreements, peer-to-peer problem solving and regression after a new member or major change.
Watch out…
Do not treat the stages as a neat timetable or use ‘storming’ to tolerate harmful conduct. Teams can move backwards, occupy different stages on different work and develop without following the model precisely.
Worth noticing…
A team may look calm because it is settled, or because nobody believes disagreement is safe yet. The meeting alone may not tell you which.
Try next…
Use Team Habits to build working agreements. Use RACI when role ambiguity dominates. Use Stakeholder Analysis when the team boundary itself is unclear.