After the friction of Storming, something shifts. Disagreements that once threatened to derail a meeting become almost routine to navigate. Roles stop being contested and start being understood. The team develops a rhythm — shared habits, a working shorthand, a sense of how decisions get made around here. Tuckman called this third stage Norming, and for most leaders it feels, finally, like relief.

That relief is exactly where Norming gets dangerous. Having survived Storming, it’s tempting to read the calm as the finish line — to step back, assume the hard work is done, and let the team’s new rhythm run on autopilot. Norming isn’t the finish line. It’s where a team’s habits get set, for better or worse, and whether those habits are examined now or left to harden determines a great deal about how the team performs later.

What’s actually happening in Norming

Trust, tested properly in Storming, starts converting into something more durable: a working consensus about how this team operates. People know who to go to for what. Meetings get shorter because less needs relitigating. Feedback starts flowing more easily in both directions, and conflict, when it happens, resolves faster because the relationships underneath it are sturdier than they were a stage ago.

The team also starts needing the leader differently. Less direction, less refereeing — but more calibration. This is the stage where a team’s standards get quietly set. Left unexamined, “how we do things” drifts toward whatever was easiest to agree on, not necessarily what’s actually best. Norming rewards a leader who stays involved in a lighter, more deliberate way, not one who reads the calm as permission to disengage.

Where it goes wrong

Norming fails quietly, which is exactly what makes it dangerous. Five pitfalls account for most of the damage:

1. Mistaking agreement for commitment. Nodding along in a meeting is not the same as genuinely buying in. Without actively testing whether people are truly committed, or simply not objecting, you find out the difference later, when the work doesn’t get done the way it was “agreed.”
2. Letting harmony tip into complacency. A team that has learned to get along can start avoiding anything that might disturb that. Standards quietly slip, challenge becomes rarer, and “good enough” starts passing for the team’s actual best.
3. Stepping back too far, too soon. A calmer team needs less direction, not less attention. Leaders who read Norming as a cue to disengage miss the chance to shape the standards and habits that are being set right now, while they’re still malleable.
4. Leaving norms unspoken and unreviewed. Working habits that form informally in Norming tend to ossify, and not always around the right things. Norms that are never made explicit can’t be deliberately improved — only inherited.
5. Confusing consensus with clarity. Chasing everyone’s agreement can quietly replace making the right call. Good decisions sometimes land without full consensus; what matters is that everyone has genuinely been heard and will commit to the outcome regardless.

Why half-hearted commitment is more expensive than open disagreement

Lencioni places Lack of Commitment directly above Fear of Conflict in his model, and Norming is where that sequencing shows its hand. A team that worked through Storming honestly — surfacing real disagreement and resolving it — tends to arrive at commitment that actually holds, because people know their views were genuinely considered even when the decision didn’t go their way. A team that avoided real conflict, or papered over it to reach the calm of Norming faster, carries that unresolved ambiguity forward. It shows up here as commitment that looks solid in the room and evaporates the moment it’s tested.

The fix isn’t more meetings seeking more agreement. It’s clarity: decisions stated plainly, owners named, and an explicit expectation that the team will commit to the call even where opinions genuinely differed. Commitment, in Lencioni’s sense, was never about everyone agreeing. It was about everyone being willing to act as though they did.

What good Norming actually looks like

A team norming well keeps a light version of the discipline that got it here. Working norms are discussed explicitly rather than left to settle on their own, and revisited periodically rather than assumed to be permanent. Decisions get stated clearly enough that “what did we actually agree?” is never a live question a fortnight later. The leader stays present — coaching more than directing, but still genuinely in the room.

We find this is often the right moment to take a team outdoors again, not to build trust this time but to consolidate it — a day spent reflecting together, away from the usual pressures of the inbox, turns the norms a team has arrived at informally into ones it has actually chosen. The habits a team sets out in nature, with time to think and no email pulling at their attention, tend to be the ones that are genuinely examined rather than simply inherited — and those are the habits that still hold once the team is back at its desks and the pressure returns.

The second piece in this series looked at why Storming is the stage most leaders try to skip. Our Decision Making and Problem Solving work digs further into turning agreement into genuine commitment, and Lencioni’s Five Dysfunctions of a Team sets out the fuller model behind the thinking here.