Tuckman's Team Stages, Watched From the Inside
Every newly assembled team I have led went through the same arc, and the first time I did not have a name for it, I made it worse. The polite early weeks fooled me into thinking we were fine; the friction that followed felt like the team breaking; and my instinct, smoothing every disagreement flat, turned out to be exactly wrong. Tuckman's model, forming, storming, norming, performing, gave the arc a name, and more usefully, it told me the leader's job changes at each stage.
Forming: the politeness is not health
A new team is quiet, agreeable, and slow, because everyone is scanning: what is safe to say, who decides, what happens when things go wrong here. Mistaking this calm for cohesion is the classic error. Nothing real has been tested yet.
The leader's job in forming is to shrink the scanning period: be explicit about how decisions get made, what done means, how disagreement is expected to sound. On distributed teams I over-invest here deliberately, because remote forming stretches; people cannot read a room they are not in, so the norms must be written down instead of absorbed. A one-page working agreement in week one has saved me a month of polite guessing more than once.
Storming: the friction is the work
Then the real opinions arrive. Architecture disputes, estimation fights, someone testing whether deadlines here actually mean anything. It feels like regression. It is progress, because the team is finally negotiating the things the politeness postponed, and the negotiation is how those things get settled for real.
The leader's mistake in storming is suppressing it, and I speak from experience: every conflict I smoothed over instead of resolving came back later with interest, a pattern I unpacked in the conflict post. The actual job is to keep the fights clean, about the work, backed by argument, decided by someone identifiable, and to make sure the quieter members' positions enter the ring too, since storming rooms default to the loudest voices.
Norming: write down what the fights decided
Storming, survived honestly, produces agreements: how we review, how we estimate, what quality bar we hold, and a definition of done that means something (the quality-in-execution post is largely a norming artifact). Norming is when these stop being contested and start being how things are done here.
The leader's job is codification. Agreements that live in memory dissolve under the next pressure spike or the next new joiner; agreements written into working agreements, checklists, and the tracker survive. This is also the stage to watch for a subtle failure: norms forming around comfort instead of quality. A team can norm into "we don't challenge estimates here" just as easily as into good review discipline. You get the norms you let settle.
Performing: the stage you protect, not manage
A performing team routes work without the leader, disagrees without drama, and notices its own slippage before anyone else does. The temptation is to conclude the team no longer needs attention. What it needs is protection: from thrash, from casual reorganization, from the assumption that a high-performing unit can absorb one more urgent thing indefinitely.
And one non-obvious fact worth its own line: the stages restart. Change enough members, or the mission, and a performing team drops back to forming, wearing its old confidence. Treating a reshuffled team as still-performing, because the name on the roster is the same, is how a leader gets blindsided by a storm they thought was two years behind them. Teams are rebuilt more often than they are built, and the model applies every single time.
Nguyễn Hải Nam
Project Management Lead. 16+ years from code to delivery. PMP®. Writing here about project management and engineering.