04 · Team Development Stages (Tuckman's Model)

A team that argued productively for six weeks and then settled into smooth delivery did not get lucky, and a team that has been polite for nine months is not necessarily healthy. Groups move through a fairly predictable sequence, and the leadership behaviour that works at one stage actively harms the next one. The most common error at this level is treating storming as a discipline problem and suppressing it — which produces a team that is permanently stuck in a courteous, low-trust forming state. This module gives you a stage diagnostic, a behaviour-per-stage table you can act from tomorrow, and a worked example of moving a stuck team through storming on purpose.

1. The five stages

Tuckman's model, with the fifth stage — added later, and the one most leaders skip entirely.

Stage	What it sounds like	What the team needs from you
Forming	Polite, cautious, questions directed at you, everyone agrees	Direction. Clear goals, who does what, low ambiguity
Storming	Disagreement about approach, ownership and standards; some of it personal	Facilitation. Surface the conflict, hold the norms, don't pick sides early
Norming	"How we do things here" emerges; people cover for each other	Participation. Hand over decisions, codify the norms, resist re-centralising
Performing	High autonomy, healthy disagreement, you hear about problems after they're solved	Delegation. Supply context, remove obstacles, get out of the way
Adjourning	Project ends, people move on; usually unacknowledged	Closure. Name what was built, capture the learning, help people land

Two things that matter more than the diagram does. First, the sequence is not one-way: a new joiner, a reorg, a new manager, or a change of goal will drop a performing team straight back to forming, and that drop is normal rather than a failure. Second, storming is not optional. A team that never storms has not skipped a stage; it has buried one, and the disagreements are happening in DMs instead.

2. A stage diagnostic

Answer these honestly, then read the pattern rather than a total.

TEAM STAGE DIAGNOSTIC

A. Where do questions go?
   ( ) Almost all to me                                    -> Forming
   ( ) To me, but as appeals against each other            -> Storming
   ( ) To each other, escalating to me by exception        -> Norming
   ( ) To each other; I hear the summary                   -> Performing

B. What happens when two people disagree in a meeting?
   ( ) It doesn't happen                                   -> Forming
   ( ) It gets tense, or moves offline and festers         -> Storming
   ( ) They work it out, sometimes needing a nudge         -> Norming
   ( ) They resolve it and nobody reports it as an event   -> Performing

C. How do people describe the team's way of working?
   ( ) They describe my instructions                       -> Forming
   ( ) Differently from each other, with irritation        -> Storming
   ( ) Consistently, in their own words                    -> Norming
   ( ) Consistently, and they've changed it since I set it -> Performing

D. When something goes wrong, when do I find out?
   ( ) Immediately — nobody will act without me            -> Forming
   ( ) Late, and framed as someone else's fault            -> Storming
   ( ) Promptly, framed as a problem to solve              -> Norming
   ( ) After it's handled, as information                  -> Performing

E. What happens if I'm away for two weeks?
   ( ) Work stalls                                         -> Forming
   ( ) Open disputes stall it                              -> Storming
   ( ) It runs, with some decisions held for me            -> Norming
   ( ) It runs                                             -> Performing

Mostly one letter -> that stage.
Split between two adjacent stages -> you are in transition; lead
   for the earlier one.
Split between non-adjacent stages (e.g. Forming and Performing) ->
   you probably have two sub-teams, not one team. Diagnose separately.

3. The stage-appropriate behaviour table

The failure is almost always a mismatch: right behaviour, wrong stage.

Stage	Do this	Stop doing this	Classic mistake
Forming	Set explicit goals, roles and decision rights; run structured meetings	Asking "what do you all think?" into silence	Mistaking politeness for alignment and declaring the team high-performing
Storming	Name the conflict as expected; run the Module 2 structures; enforce behaviour norms hard and opinion norms not at all	Taking sides; going quiet and hoping	Reading disagreement as insubordination and suppressing it
Norming	Get the norms written down by them; delegate a real decision; publicly back one you'd have made differently	Re-opening settled decisions	Re-centralising the moment quality dips once
Performing	Supply context and air cover; ask what's in the way; absorb organisational noise	Attending meetings that don't need you	Boredom-driven meddling — inventing a reorg because you feel underused
Adjourning	Hold a proper close: what was built, what was learned, what each person can now do that they couldn't	Letting it dissolve silently	Rolling straight into the next thing, so nobody's growth gets named

4. A worked example: entering storming deliberately

Owen has led a five-person internal communications team for four months, after a merger brought two smaller teams together. Everyone is pleasant, everyone defers, every decision comes to him. He runs the diagnostic and scores Forming on all five questions — at month four, which is the warning sign. The two legacy teams hold incompatible working assumptions that nobody has said aloud. He decides to surface the conflict on purpose, in a working session.

Owen: I want to name something. We've been together four months and I don't think we've had a single real disagreement in this room. That's not because we agree — it's because we haven't said what we think. That's normal at this point, and I'd like to get past it today.

Owen: So, a specific question, and I want the actual answer. When a business unit asks us for a comms plan with four days' notice, what should we do?

(Silence.)

Owen: I'll make it easier. Jules, what did your old team do?

Jules: We said yes. Always. If comms says no, they go around us and send something worse.

Owen: Ravi, what did yours do?

Ravi: We said no. We had a two-week intake rule and we held it, because otherwise you spend the whole year on other people's fire drills and the planned work never happens.

Jules: And what happened when you said no?

Ravi: Sometimes they escalated. Mostly they planned better the next time.

Jules: That would never have flown with our directors.

Owen: Good — that's the disagreement, and it's a real one. I'm not resolving it by decree. Two rules for the next twenty minutes: argue about the approach, not about which old team was better run; and before you rebut, say back what the other person's reason is.

Ravi: Jules's reason is that a hard no doesn't stop the comms going out, it just makes it happen without us — which is worse than a rushed plan.

Jules: And Ravi's is that if we never protect the calendar, the planned work is the thing that dies, every time.

Owen: Both true. What's a rule that respects both?

Sofia: Tiering. Anything that goes to more than 200 people or is externally visible needs the two-week intake. Below that, we take it in and do a cut-down version.

Ravi: I could live with that if "cut-down" is actually defined, so it isn't just a full plan under time pressure.

Jules: Then let's define it. Three assets, no bespoke design, no review cycle beyond the requester.

Owen: Write those two things down as ours, not mine, and put them on the team page by Friday. I'll back it when someone escalates — and someone will, in about three weeks.

That session was uncomfortable, and that was the point. Owen supplied the permission, the norms and the reflect-back rule; the team supplied all of the content. Within a month the diagnostic moved to Norming on questions A, B and C. Note his last line: at the norming stage the leader's job is to publicly hold a boundary the team set, especially the first time it is tested. One failure to back it returns the team to forming immediately.

5. Regression is not failure

When a team drops back a stage, say so out loud. "We've added two people and changed the goal, so we're going to feel like a new team for about a month — I'll be more directive for a bit, and that's temporary" converts a confusing experience into an expected one. Teams tolerate regression well when it is named, and badly when it is denied.

How It Actually Works

Tuckman's stages describe a real, mechanistically-grounded process: a group of individuals has to build a shared mental model (of norms, roles, and how disagreement gets resolved) before it can function as a coordinated unit, and that model can only be built through actual friction, not declared into existence. Forming looks calm because no one has yet tested where the real boundaries are — people default to polite, low-information behavior because the group's operating norms are genuinely unknown. Storming is the necessary process of that model actually getting built: disagreements surface real information about priorities, working styles, and authority that politeness in Forming was hiding. A team that skips straight from Forming to apparent "Norming" (or is managed to avoid conflict) hasn't actually built a shared model — it has a norm of avoidance sitting on top of unresolved, undiscussed disagreements that will resurface later, usually at a worse time.

Why deliberately entering Storming is often the right leadership move, not a failure to prevent conflict. Suppressing early disagreement doesn't remove the underlying divergence in mental models — it just defers the friction to a moment the leader doesn't control (often under higher-stakes pressure later). A leader who structures a low-stakes, explicit disagreement early (as in the worked example) is deliberately triggering the model-building process while the cost of doing so is still low, which is a form of the same principle behind "fail fast" in engineering: surfacing a necessary failure early and cheaply beats letting it surface late and expensively.

Why regression under new stress is not a step backward in the model but consistent with it. A new member, a changed goal, or an external shock partially invalidates the team's existing shared model — the norms that worked don't fully apply to the new configuration, so some Storming-like renegotiation is mechanically necessary again. Treating this as failure (as if the team should have "arrived" at Performing permanently) misunderstands the model: Tuckman's own later revisions describe stages as recursive, not a one-way staircase, because the underlying cause (divergent mental models needing reconciliation) recurs whenever the group's composition or goals change materially.

Exercise

Run the diagnostic in section 2 for your team this week, then run it separately for two or three individuals — people join at their own pace, and a new starter is in forming even when the team is performing.

Now take your result to the table in section 3 and find your own mismatch: name one thing from the "stop doing this" column for your current stage that you actually did in the last two weeks. Replace it with one specific action from the "do this" column, on a date. If you scored Forming past the three-month mark, make that the exercise instead — plan a session like Owen's, built around one real question on which you know two people quietly disagree.