Tuckman Model: Forming, Storming, Norming, Performing, Adjourning

Leaders often import last quarter’s habits into this week’s group.

A new team is polite and late. The manager reads that as healthy culture and withholds structure. Another team argues in standups. The manager reads that as a hiring error and tries to shut conflict down. A third team shipped well last year, then a new director arrived, and the old habits slipped. The manager reads that as laziness.

Those misreads are expensive. Forming needs purpose and roles. Storming needs conflict that can be worked. A slump after a shock is often a recycle, not a character verdict.

Tuckman is a way to name the dominant pattern before you pick an intervention. It will not make a group “high performing” by labeling them Performing.

Bruce Tuckman (1965) described four stages of group development from a review of studies. With Mary Ann Jensen (1977) he added Adjourning for groups that end.

The teaching order is a map. Real teams recycle after membership, purpose, or leadership shocks. Mixed signals often mean a transition or two subgroups. They do not require a sixth official stage.

A useful pass is behavior, stage, blocker, then a matching focus.

1. Collect observable patterns

How do people decide, disagree, and wait for the leader? Prefer meetings and delivery habits you can point to. Do not use tenure as a proxy (“they have been together eight months, so they must be Performing”).

2. Match a dominant stage

Pick the pattern that explains most of what you see. If Forming politeness and Storming conflict both show, say transition rather than averaging them into Norming.

3. Name the stage-specific blocker

Forming often lacks purpose or roles. Storming often lacks a way to disagree. Norming can over-value harmony. Performing can hide a missing strategic context. Adjourning can skip loss and handover.

4. Match leadership focus

Intervene for this stage, not for an ideal stage. Wishing the group into Performing while it is Forming usually means more speeches and less structure.

Revisit after a shock. Regression is a signal to reapply an earlier focus, not a moral failure.

When another lens fits better, or when you need a complementary view, these frameworks do different jobs.

Tuckman is the lens for a team’s developmental pattern. Other methods help when the question is a person’s conflict mode, conflict type, a change curve, or role assignment.

• A new team. Politeness and leader-dependence look like harmony and are still Forming.
• Conflict that might be Storming. Arguments about how to work are not automatically a toxic-hire story.
• A disruption. New members, a new manager, or a scope reset after which old norms slipped.
• Closeout. A project team needs handover and recognition, not only a last sprint.

Example: New cross-functional squad

A squad forms for a six-month launch. First two weeks are polite. People wait for the product lead to assign tickets. Two engineers privately disagree about the stack and never say it in the room.

Reading this as Performing because calendars are full would miss Forming. The leadership focus is purpose, decision rights, and a structured way to surface the stack conflict before it becomes Storming-by-chat.

Example: Team that “used to work”

The same squad shipped a beta. A new engineering manager arrives and changes review rules. Standups become arguments. People say “we were Performing, now we are broken.”

A Tuckman-shaped reading is recycle: the shock sent the group back through Storming (and maybe Forming on the new rules). The focus is to work the conflict and restated constraints, not to demand last quarter’s autonomy on day three of a new manager.

What the Tuckman Model can help with

• Naming a dominant developmental pattern from behavior
• Matching leadership focus to Forming, Storming, Norming, Performing, or Adjourning
• Interpreting conflict as possible Storming rather than instant failure
• Expecting recycle after disruption

What the Tuckman Model cannot replace

• Thomas-Kilmann. How a person handles a conflict episode is a style choice, not a group stage.
• 4 Patterns of Team Conflict. Conflict types (not time stages) are a different cut.
• Satir Change Model. Emotional phases of a change event are not team-development stages.
• RACI. Who is Responsible or Accountable on work is role clarity, not Forming-to-Performing.
• A proof that stages never skip. The teaching sequence is a map. Real groups recycle. “Cannot skip” is a caution against wishing the team into Performing, not a laboratory law this page should sell.

Honest scope: Tuckman structures a stage judgment and a matching focus. It does not replace the methods above.