A new team seems polite in its first meeting and argumentative a month later. Calling the change “storming” can give people a shared vocabulary, but the label does not explain the disagreement or tell the manager what to do next.
Atlassian’s guide to Tuckman’s model describes forming, storming, norming and performing, and discusses how changes in membership or direction can change a team’s situation. Use those stages as prompts for inquiry rather than a calendar that promises a productive team after a particular number of weeks.
Describe the behaviour before choosing a stage
Replace “we are storming” with an observation: “People disagree about what counts as a completed review.” That statement can be investigated. Ask for a recent example, compare the expectations and decide what needs clarification.
In an invented team discussion, two people argue because one expects an early rough draft and the other expects a polished document. Naming a developmental stage does not resolve that mismatch. Agreeing what the next review should contain does.
Use the model to choose a useful conversation
- Are people still learning the purpose and their roles?
- Which disagreements concern work, and which concern how decisions are made?
- Which working agreements are understood consistently?
- What lets the team deliver without repeatedly renegotiating the basics?
These questions are more useful than asking everyone to vote on a stage and leaving it there. Different parts of the work may show different patterns at the same time.
Do not use the model to normalise bullying, persistent exclusion or an unsafe workload. A developmental description is not permission to leave harmful behaviour unresolved. Address the actual issue through the appropriate management process.
After a change in membership or purpose, revisit the agreements that depend on it. Keep a short note of the observation, the action chosen and when you will review it. The model earns its place when it helps the team ask better questions, not when it replaces them.

