Most leaders who take over a new crew, a merged shift, or a freshly formed project group expect it to work as a team within a few weeks. The stages of team development explain why that timeline rarely holds, and why the friction leaders see early on is usually a normal part of the process.
Picture a plant that stands up a new production line with a mix of ten-year veterans and new hires. By week three, the veterans are frustrated with the pace of the new hires, the new hires feel talked over, and the supervisor is fielding the same complaints from both groups. It is easy to conclude that the wrong people were put together. More often, the team is moving through a stage that every team passes through, and the leader’s next move depends on knowing which one.
This article walks through the five stages, what each one looks like in a plant and in an office, the mistakes leaders tend to make along the way, and how to tell where your own team stands today.
Where the Stages of Team Development Come From
The most widely used framework, often called the Tuckman model, comes from psychologist Bruce Tuckman. In a 1965 paper in Psychological Bulletin, he described four stages of small group development: forming, storming, norming, and performing. In 1977, Tuckman and Mary Ann Jensen added a fifth stage, adjourning, after reviewing the research that followed. Together, these make up the five stages of team development that most leaders have heard of, and they are often taught as the Tuckman stages of group development. Many leaders know the sequence simply as forming, storming, norming, performing, a phrase that has become shorthand for the whole model.
Leaders who search for team building stages will find the same five names repeated everywhere, and the model has lasted for decades because it matches what leaders see. Teams do not arrive ready to perform. They build trust, work out how the work gets done, settle on shared habits, and eventually start to run themselves.
One caution before going further. The stages are not a straight line that a team walks once and finishes. A new supervisor, a change in shift pattern, two or three people rotating in, or a major new piece of equipment can send a team back a stage. Leaders who treat the stages as a one-time checklist are often surprised when a team that was performing last quarter starts to struggle again.
The Five Stages of Team Development and What Each One Looks Like
Each of these team development stages asks something different of the leader. The descriptions below use plant and office examples, since the same patterns show up in both.
-
Forming
In the forming stage, people are polite, careful, and watching each other. Roles are unclear, and the team leans heavily on the leader for direction. On a plant floor, this is the first few weeks of a new line crew or a newly merged shift, when nobody is sure who makes which call.
The leader’s job is to give the team a clear purpose, clear roles, and clear expectations, and to create structured chances for people to learn how their teammates work. A short working session on how handoffs will run is worth more than a team lunch.
- Storming
Storming is where friction appears. People disagree about roles, methods, and authority, and some respond with open conflict while others quietly withdraw. In manufacturing this often shows up as arguments about handoffs, who owns a quality issue, or whose way of running the line should win. Many leaders read this as a sign the team is failing and try to shut it down, which is the most common mistake at this stage. Working through the disagreement is how a team earns the trust and agreement it needs later. The leader’s job is to coach people through the conflict, keep it focused on the work, and make decision rights explicit so the same argument does not repeat every shift.
- Norming
In the norming stage, the team settles on agreed ways of working. Trust grows, people begin giving each other direct feedback, and routines such as standard work and shift communication start to hold without constant supervision. The risk at this stage is mistaking calm for strength. A quiet, agreeable team can still be avoiding the hard conversations, and leaders who stop paying attention here may find out later that real concerns were never raised. - Performing
A performing team owns its results. Roles flex as needed, and problems get solved at the team level before they reach the leader. In a plant, picture a crew that catches an issue at one end of the line and fixes it with the people at the other end, without escalating. The leader’s job shifts from directing to protecting and stretching the team: removing avoidable disruption, setting new challenges, and staying close enough to notice when something changes. - Adjourning
Adjourning happens when a project ends, a line is retired, or a team is reorganized. It matters more than most leaders expect. A deliberate close, with recognition and a review of what the team learned, protects morale and gives the next team these people join a better start.
Why Teams Get Stuck, and How Leaders Make It Worse Without Meaning To
Most stalled teams are held back by a mismatch between the stage they are in and the way they are being led. A few patterns come up again and again:
- Skipping storming. Leaders who rush past conflict often end up with surface agreement that falls apart under production pressure.
- Mistaking calm for performing. A team that is quiet and compliant may be sitting in an early stage with real concerns left unspoken.
- Ignoring resets. A new supervisor, a shift change, or a few new members quietly move the team back, and expectations do not adjust.
- Leading the same way at every stage. Heavy direction suits a forming team and can stall a performing one, while leaving a forming team to figure things out wastes weeks.
- Treating team building as an event. A single off-site or training day cannot move a team through a stage without follow-through in daily behavior.
Each of these is fixable once the leader can name the stage. The harder part is seeing it clearly from the inside.
How to Tell Where Your Team Is Right Now
Start with what you can observe this week. Notice how decisions get made and who speaks in meetings. Notice how conflict is handled, whether people take disagreements to each other or to you, and how often problems get escalated instead of solved where they happen. Those signals say more about a team’s stage than its output numbers do, because a team can hit its production targets while still sitting in an early stage.
Consider a hypothetical second shift crew that meets every target but never raises a problem until it becomes a stoppage. On paper it looks like a performing team. In practice, people may be staying quiet because speaking up has not felt safe, which points to an earlier stage than the numbers suggest.
A leader’s own read of the team also has limits. Leaders close to the work tend to see their teams the way they hope they are, and team members often tell the leader what the leader wants to hear.
This is where an assessment-informed team diagnostic helps. It gives an evidence-based read on communication patterns, decision-making styles, and alignment gaps, interpreted by someone trained to see what the data and the conversations show together. It informs the leader’s judgment and does not replace it.
Questions to Ask About Your Team’s Stage
These questions can help you place your team in the arc before you decide what to do next.
- Has anything changed in this team in the last six months, such as a new leader, a new shift pattern, or new members?
- When two people on this team disagree, does it get resolved, avoided, or escalated to me?
- Do people give each other direct feedback, or do they only share concerns with me privately?
- Could this team solve its next recurring problem without me in the room?
- Am I leading this team the way it needs to be led today, or the way it needed to be led a year ago?
If several of these are hard to answer, that is useful information in itself. It usually means the team has not been looked at closely since it last changed.
How DMC Approaches Team Development
At Dynamic Management Consulting, team development starts with the same philosophy behind everything we do: validated data, interpreted by experts, applied to real decisions.
Diagnose First
We begin with an assessment-informed read on where the team stands, so workshops are built around what the data and the conversations show instead of a standard agenda.
Workshops Built Around the Team
Sessions on communication, trust, and cohesion are customized to the team’s situation, including its stage, its shift structure, and the work it does. A team forming around a new line needs something different from a team that has worked together for years and hit a wall.
Follow-Up That Holds
Coaching and reinforcement after the workshop help new behaviors survive the first busy week back on the floor. Matt Fearrington has spent nearly 20 years working with organizations, including manufacturers across North Carolina, Tennessee, and Virginia, and that experience shapes both the examples and the pace of the work.
Knowing the Stage Changes What You Do on Monday
Every team is somewhere in this arc, and the right move for a leader depends on where. Naming the stage gives you a reason to stay with the hard part of the work, whether that is the conflict in storming or the unspoken concerns in norming, instead of replacing people or starting over.
The stage can also change with one new hire or one new supervisor, so it is worth checking again after any major change.
If you are leading a team that is not working the way you expected, I would be glad to talk through where it stands. Book a 15-minute call with me, and we can look at what stage your team may be in and what a team diagnostic could show.
