The core idea
Tuckman’s 1965 review proposed forming, storming, norming and performing as a way to understand group development. Adjourning was added with Jensen in 1977. Teams may need orientation, negotiation of roles, shared working norms and coordination around the task. The model is a heuristic: actual teams can revisit issues, change membership or develop in less orderly ways.
Source and attribution [1]Using it in practice
Ask what the team needs now rather than declaring its stage. Clarify purpose, decision rights and expectations when people join. Distinguish disagreement about work from personal hostility. Make working agreements specific enough to observe and revisit them after a major change. When a project ends, plan knowledge transfer and acknowledge contributions instead of letting closure happen by accident.
An example, not a reported case
Worked example · illustrative
A newly combined HR and payroll team argues about priorities. Calling this “storming” explains little. A facilitated session reveals conflicting deadlines and no agreed escalation route. The team maps dependencies, allocates decisions and tests a shared weekly triage. When another service is added, it revisits the agreements rather than assuming it has permanently reached “performing”.
What to watch for
Bullying and discrimination are not healthy developmental stages. The model does not establish how long any stage lasts or guarantee that all teams experience each one.
Use the stages as questions about current needs
Ask whether the team needs clarity about purpose, a way to handle disagreement, reliable working agreements or support to improve performance. A team may experience several of these needs at once. New members, a changed task or a crisis can disrupt established routines. Do not assume a team has permanently completed a stage because it has existed for a long time, or that conflict must occur in a prescribed sequence.
Make disagreement productive
In an illustrative cross-functional project, operations wants speed while HR wants consistent evidence. The disagreement may reveal a real trade-off rather than immaturity. Clarify the shared outcome, decision criteria and who decides if agreement is not possible. Separate criticism of an idea from criticism of a person. Calling the disagreement 'storming' should not become a way to avoid resolving it or to normalise bullying.
Turn agreements into routines
Write down how the team allocates work, shares information, raises concerns and makes decisions. Test these agreements in actual meetings and handovers. A team charter has little value if it is never used when pressure rises. Review whether absent, remote or quieter members can contribute. Adjust routines when they create unnecessary work or exclude people, rather than treating the initial agreement as a permanent contract that cannot be questioned.
Review transitions and endings
When membership or purpose changes, revisit responsibilities and knowledge transfer. At the end of a project, capture useful learning, recognise contribution and clarify where unfinished work goes. Do not assume high output means the team is healthy; it may depend on unsustainable effort by a few people. The model is a descriptive aid, not a diagnostic scale. Use observed collaboration, quality and workload alongside the team's own account of how it is functioning.
Use the stages to interpret interaction, not impose a timetable
A newly formed team may need clarity about purpose and roles, while an established team can revisit conflict after a change in membership or task. Notice the actual issue: uncertainty, competing expectations, working agreements or coordination. Do not assume every team must experience a dramatic storming phase, or excuse persistent harmful behaviour as a necessary developmental stage. The model simplifies a process that can be uneven and recursive.
Match the intervention to the observed difficulty
If disagreement concerns responsibilities, clarify decisions and handovers rather than arranging a generic bonding activity. If the team avoids useful challenge, model respectful disagreement and agree how concerns are raised. Review whether working agreements are used during pressure, not just accepted in a workshop. A team that appears harmonious may still lack the capacity to question errors. Revisit the arrangement after staff changes and recognise that performance depends on resources and organisational context as well as internal relationships.
Take it into your next conversation
Three useful questions.
- What is unclear about the shared task?
- Which disagreement needs a decision?
- What must be revisited after membership changes?
Related terms
Go to the evidence
Sources & attribution
[1] Tuckman, B. W. (1965). Developmental sequence in small groups. Psychological Bulletin. ↗
The core idea is an original summary of the cited work. Application notes, examples and sketches are our interpretations, not quotations or reproductions of the authors’ figures. Publisher records may require access to read the full original work.
Application guidance expanded on 26 September 2026. These practical suggestions and invented examples are editorial explanations; further-reading sources are not the original authors of the historical models unless expressly identified. Original overview review dates are retained.
Published 2026-09-20 · Reviewed 2026-09-22. Editorial approach