A group of competent people is not yet a team, and the distance between the two is predictable enough to be worked through on purpose. Bruce Tuckman described that distance in 1965 as four stages, forming, storming, norming and performing, and added a fifth, adjourning, in 1977. PMI uses the five stages in the People domain as the standard account of how a project team develops, and a candidate is expected to recognise which stage a described team is in and what its leader should do about it.
The stages run in order, and they run more than once. A team returns to the beginning whenever its membership, its goal or its way of working changes, which on a long project happens several times. The sections below describe the stages, the leadership each one needs, what sends a team back to the start and the safety that all of it depends on.
The five stages at a glance
| Stage | What it looks like from outside | What the leader does |
|---|---|---|
| Forming | Polite meetings, every question routed to the leader, agreement that costs nothing, very little finished | Supplies explicit goals, explicit boundaries and an explicit account of who knows what, and answers the literal question asked |
| Storming | Estimates challenged, decisions reopened, two people arguing about the approach, someone going quiet | Keeps the disagreement pointed at the work, names the conflict the group is talking around and makes it safe to say the estimate is fantasy |
| Norming | Working agreements appear without being asked for, people correct each other, meetings get shorter | Steps back into a supporting position and leaves the team's own rules alone |
| Performing | Problems solved without reaching the leader, the team inducts its own newcomers, delivery becomes boringly predictable | Protects the conditions, absorbs the interruptions and reads the outcome while leaving the method alone |
| Adjourning | Attention drifting to what comes next, handover written late or never, people quietly reallocated | Recognises what was done, releases people cleanly and captures what the organisation learned while anybody remembers |
What the leader does at each stage
The right hand column changes from row to row because each stage needs a different kind of leader. Forming is polite and unproductive because nobody yet knows who everyone is or what is expected, so the questions come to the leader and the answers are taken literally. Direction is cheap at this stage and clarity is scarce, which is why the stage needs explicit goals, explicit boundaries and an explicit account of who knows what.
Storming is where the group discovers that it disagrees about how the work should be done and who gets to decide. The instinct to smooth that over is the wrong one, because the disagreements are the group working out how it will operate, and suppressing them only moves the argument somewhere less visible. The leader's job is to keep the disagreement pointed at the work, to name the conflicts the group is talking around and to make it safe to be the person who says the estimate is fantasy.
Norming is when the group settles how it will operate and begins policing that for itself. The leader steps back into a supporting position and resists reinstating rules the team has already written better versions of. A rule the team wrote is enforced by the team, and a rule the leader imposed is enforced only while the leader is watching.
Performing needs delegation and very little else. The team is solving problems the leader never hears about, and the useful contribution is protecting the conditions the team works in.
Adjourning is the stage that gets skipped. Closing a project properly means recognising what was done, releasing people cleanly to whatever comes next and capturing what the organisation learned while anybody still remembers it.
What sends a team back to the beginning
A team that has reached performing does not stay there by right. The trigger for a return is a change in membership, in goal or in the way of working. A new joiner in month eight puts a performing team back into forming for a fortnight, because the working agreements live in people and the newcomer holds none of them. A reorganisation that changes who the team reports to does the same, and so does a change of scope large enough that the old agreements were written for a different project.
Expecting the return makes it cheap. The leader reissues the explicit version of what everyone else absorbed months ago, runs the introductions properly and lets the group storm briefly over what it had already settled. The alternative is a leader wondering why a good team has gone quiet, which is a fortnight lost to something that had a two hour answer.
Ground rules and the team charter
The working agreements a newcomer lacks are usually written down in a team charter, which is the team's own statement of how it intends to work. It typically covers the shared goal, who does what, how decisions get made, how the group handles disagreement and the working agreements that would otherwise be discovered by breaking them.
Its value comes almost entirely from being argued out. A charter produced in a room creates the disagreement in advance, which is far cheaper than having it during the first crisis, and it gives the team something to point at when somebody drifts. A charter drafted by the project manager and circulated for comment produces a document nobody consults again.
Ground rules are the part of the charter that gets enforced. They work when they are specific enough to be broken visibly, so a rule saying that decisions are made by whoever is in the room at the time is worth ten rules saying the team will communicate openly.
The psychological safety the stages depend on
Nobody will name a broken ground rule, argue during storming or admit an error in performing unless the team has psychological safety. This is the shared belief that the group will accept a person who speaks up. In working terms it is the belief that admitting an error, asking an obvious question or challenging a senior person carries no cost, and it sits comfortably alongside demanding standards. Comfort and niceness are different things, and a team can have plenty of both while nobody says anything that matters.
Everything above depends on it. Storming cannot happen without it, ground rules go unenforced because nobody will name the breach, and the team performs faithfully against a plan that a quiet member knew was wrong in week two. The symptom is a team whose estimates are always confident and always late.
A team that has never stormed
That symptom often belongs to a team that is read as healthy because it is quiet, and a quiet team is more often a team that has not yet said anything difficult. Real work produces real disagreement, because two competent people looking at the same architecture, the same estimate or the same deadline will sometimes reach different conclusions. Where none of that reaches the surface, the likely explanation is that people have decided it is not worth the trouble.
Storming is therefore a sign of progress, provided it stays about the work. The distinction that matters is between a team arguing about the sequencing of two workstreams and a team arguing about who is difficult to work with. The first is a group finding its way to norming. The second has already left these stages behind and needs handling as conflict.