What Are the Stages of Team Development, and How Do You Speed Them Up?

The stages of team development are forming, storming, norming and performing, and a new team moves through them faster when its leader makes disagreement cheap early rather than expensive later. Bruce Tuckman described the sequence in 1965 and it has held up. The sequence is not optional. What a leader controls is the pace, and PowerProv is usually brought in for exactly that gap.

Forming, storming, norming, performing: what happens at each stage?

Four stages, first described by psychologist Bruce Tuckman in the paper Developmental Sequence in Small Groups, published in Psychological Bulletin in 1965. Tuckman and Mary Ann Jensen added a fifth in 1977.

Two things get misread about the stages of team development. The first is that it's a timetable. It isn't. Tuckman described a sequence, not a duration, and teams run through it at speeds that vary enormously. The second is that it's one-way. A team that loses two people, gains a new manager, or absorbs another function goes back to forming, whatever its previous stage.

Why do new teams stall in storming?

Because nobody wants to be first to say the awkward thing.

Storming is the stage where a team works out whose judgement it trusts and how it handles disagreement. That requires someone to disagree out loud. In most new teams, the perceived cost of doing that is high: you're new, you don't know how it lands, and the safe move is to nod and raise it later in a smaller room.

So the friction doesn't disappear. It goes underground and shows up as symptoms instead:

• Decisions that get made and then quietly relitigated
• Work redone because an objection surfaced after delivery
• Meetings that end in agreement and side channels that don't
• One or two people doing most of the talking while the rest wait

A team in this state can look calm and be badly stuck. The absence of visible conflict in a new team is not usually evidence of a healthy team. It's more often evidence that the disagreement hasn't found a safe route to the surface yet.

Can a team skip storming?

No. It can only postpone it, and the postponed version is worse.

The appeal of skipping is obvious: storming is uncomfortable and leaders are judged on how the team looks. A team that stays polite for six months has not avoided the stage. It has scheduled the stage for the first moment real pressure arrives, which is usually a deadline, a budget cut, or a project going sideways. Storming with a live crisis attached is far more expensive than storming in week three over something small.

The useful reframe: a new team that argues productively in its first month is ahead, not behind.

What moves a team from forming to norming?

Shared work with real stakes, plus a visible signal that disagreement is survivable.

Introductions don't norm a team. Neither does a values workshop or a personality profile, though both have their uses. Teams norm around the experience of doing something together and finding out how each other operates under a bit of pressure.

Google's Project Aristotle research into what makes teams effective landed on psychological safety as the strongest factor: the shared belief that the team is a safe place to take an interpersonal risk. That's the same thing storming tests. A team where saying "I think that's wrong" is survivable will pass through storming quickly. A team where it isn't will circle.

The practical moves that build it:

• Make standards explicit. New teams waste weeks guessing at norms nobody wrote down. Say how decisions get made, what "done" means, and how disagreement is expected to be raised.
• Be wrong in public, deliberately. A leader who says "I got that call wrong" once in the first month does more for psychological safety than any statement of values.
• Create early shared work. Something with a real outcome, small enough to fail safely.
• Watch who isn't talking. Silence in a new team is data, not consent. PowerProv's work on psychological safety covers how to read and change it.

What should a leader do in a new team's first 90 days?

Front-load the uncomfortable parts and stop trying to keep everyone comfortable.

A rough sequence that works:

1. Weeks 1–2: set the frame. Purpose, roles, decision rights, standards. Written down, not implied.
2. Weeks 3–6: create friction on purpose. Put the team on a real problem where opinions will differ, and let the disagreement happen in the room instead of managing it away.
3. Weeks 6–10: name the norms the team has formed. Say out loud what you're seeing, including the unhelpful patterns. Naming a pattern is most of changing it.
4. Weeks 10–13: step back. If the team still routes every decision through you at week 12, it hasn't normed. It has just learned to ask you.

Leaders new to the role often find step two the hardest, because it feels like letting things go wrong. It isn't. Managers moving into their first leadership role are usually applying the same skills they already had, just through other people's work rather than their own, and that shift is where the discomfort comes from.

Do the stages of team development change for remote or merged teams?

Yes, in both cases the middle stage runs longer, for different reasons.

Remote and hybrid teams lose the small, low-stakes friction that lets storming surface gently. On video, disagreement is either a scheduled agenda item or nothing. Distributed teams generally need to manufacture the shared experience that a shared floor would have produced.

Merged or restructured teams don't just form once. They form on top of two existing sets of norms, each of which feels obviously correct to the people who hold it. Storming here is about whose way of working wins, which is why it takes longer and gets personal faster. PowerProv covers this specific case in its piece on team building after a merger.

How does experiential training shorten the timeline?

By giving a team the storming and norming experience in a few hours, without a real deliverable at risk.

This is the specific reason PowerProv gets booked for new, merged and restructured teams. A workshop puts people into unfamiliar situations together where they have to think quickly, respond to each other, and get things wrong in front of colleagues. That is the storming experience in miniature, at a fraction of the cost of learning it live on a client project.

The mechanism underneath is what PowerProv calls the ensemble mindset: walking into work trusting that the people around you have your back, will support your decisions, will help make you look good, and will treat a mistake as something to learn from rather than something to blame. That mindset is what a team is trying to build in norming. It is also exactly what a well-run PowerProv workshop is built to install, which is why teams often describe the shift afterwards as knowing each other properly rather than just knowing each other's names.

Two objections come up whenever this is proposed for a brand new team, and both are worth answering. The first is that it sounds like a comedy workshop. It isn't one, and nobody is asked to be funny or put in front of an audience. The second is the more serious concern with a new group: you don't yet know who your quiet people are, and the last thing a forming team needs is an exercise that exposes someone in week two. Difficulty is built up gradually and most of the work happens in small groups, which is why the quieter half of a new team tends to engage rather than retreat.

Teams of 12 or more can start with a half-day workshop, or use the six-week embedded class when a team is forming and the goal is to make the change hold.

PowerProv, Personal Power Index™

The Personal Power Index™ is PowerProv's ongoing longitudinal study, measuring a set of skills before and after each workshop across hundreds of participants. It measures capability change, not how much people enjoyed the day.

Bottom line

PowerProv runs workshops for teams of 12 or more across Australia and APAC, in person and online, rated 4.9 stars over 13 years with organisations including Google, Westpac, PwC, Canva and Bain & Co. Every workshop carries a money-back guarantee.

Book a discovery call to talk through where your team is stuck, or see how it works first.