You Ran the Workshop. The Team Is Still Storming.
A team lead I talked to did everything right. She walked her team through Tuckman's model. Forming, storming, norming, performing. She ran the exercises. She put the four stages on a slide and asked the team to name where they were.
Everyone said "norming." Three weeks later, the same two people were still fighting over the same decision. The team had named the stage. It had not moved through it.
This is the gap in most Tuckman model exercises. They describe the stages well. They do almost nothing to move a team from one to the next.
What the Tuckman Model Actually Is
Bruce Tuckman published the forming-storming-norming-performing model in 1965. A fifth stage, adjourning, came later. It is one of the most cited team-development frameworks in the world, and for good reason — the four stages are a clear, memorable way to describe what teams go through.
Two things are worth knowing about where it came from. First, Tuckman built the model by reviewing studies of therapy groups, not workplace teams. Second, Tuckman himself wrote in that original paper that the literature could not be considered truly representative of small-group development. He was honest about the limits. The model spread faster than the caution did.
That history matters for one reason. The Tuckman model is a description, not a method. It tells you what the stages look like. It does not tell you how to get a team from storming to performing. Most exercises built on it inherit that same gap — they help a team label its stage, and labeling is not movement.
Why the Exercises Don't Move the Team
There are three reasons a worksheet rarely moves a team forward.
Teams don't move in a straight line. The model looks linear on the slide. Real teams move back and forth. A team that reached performing drops back to storming the moment a new member joins, a leader changes, or the work itself changes. The research is clear on this — progression is not sequential, and any disruption can reset a team to an earlier stage. A one-time exercise assumes a straight line that does not exist.
Naming a stage is not the same as building the skill the stage needs. Storming is not a phase you wait out. It is a phase a team gets through by learning to disagree without killing each other's ideas. A worksheet that says "you are in storming" does not teach that skill. The team finishes the exercise exactly as able to handle conflict as it was before.
A team under no pressure tells you nothing. Ask a calm team in a conference room which stage it is in, and it could guess "norming" or "performing" — because nothing is testing it. Stages only become visible under load. The exercise people search for is a worksheet. The thing they actually need is a pressure test.
There is a deeper version of this. Some teams move through all four stages and still never learn as a team — they reach "performing" on the surface while the same unspoken patterns run underneath. Groupthink is what that looks like when the surface says performing and the substance says something else.
What Compresses the Four Stages
Here is what changes the picture: put a team into a real problem, with a clock, with consequences, and all four stages happen in one afternoon.
That is the design behind Save the Titanic. A team becomes the Senior Officers of the RMS Titanic in the minutes after the iceberg strikes. Limited time. Limited resources. 2,200 lives depending on their decisions. Inside three and a half hours, you watch every Tuckman stage compress into view.
Forming happens in the first few minutes — who is in charge, what is our role, what are we even doing here.
Storming hits fast and hard. Under a real clock, the team fights over what to do, and this is where most teams stall. They start killing each other's ideas to save time, which is exactly the move that costs them time.
Norming is the turn. The team agrees how it is going to work — who captures decisions, how it handles disagreement, how it moves.
Performing is the last stretch. The team executes against the clock with a way of working it actually trusts.
The storming stage is the one worth watching. Most teams treat storming as something to survive. In the simulation you see the better move: a team that learns to stop killing ideas — to acknowledge an idea before evaluating it — gets through storming in minutes instead of weeks. That single behavior is the bridge from storming to norming. No worksheet teaches it. Pressure plus a structured debrief does.
How to Use This With Your Team
You do not need a worksheet. You need a test and a debrief. Three moves.
Give the team a real, time-boxed problem. Not a status meeting. A genuine decision with a deadline and something at stake. Step back and watch. The stage your team gets stuck in is the stage your team is actually in — not the one it named on the slide.
Watch the storming behavior specifically. When the pressure rises, does the team start cutting each other off and discarding ideas to move faster? That is the tell. Storming-stuck teams kill ideas. Norming teams capture them and build on them.
Debrief the pattern, not the outcome. Whether the team "won" matters less than what you saw. Name the specific moment the team got stuck, and the specific behavior that would move it. A structured team debrief turns what you watched into behavior changes the team can use next week, and an after-action review does the same work in the format many operations teams already use.
Here is the quick artifact. After any pressured piece of work, ask the team four questions. Did we know our roles? That is forming. Did we fight productively, or just fight? That is storming. Did we agree how to work, or just start working? That is norming. Did we trust the way we were working? That is performing. The honest answers tell you the real stage. The slide never did.
What the Pressure Test Reveals
At ArcelorMittal, 710 leaders went through this kind of pressured simulation via Duke Corporate Education. Afterward they made decisions 30 to 40% faster. Not because anyone told them to hurry — because they had seen, under load, exactly where their team stalled, and they had a shared language for moving past it.
That is the difference between an exercise and a test. An exercise lets a team describe itself. A test shows a team what it actually does when it counts — and that is the only view that moves anyone forward. If you want to see what the pressure test looks like before you run one, watch how the Save the Titanic experience works.
Read next: Team Debrief Template