The Stages of Team Development: How Teams Learn to Work Together

The project began with great energy.

During the kickoff meeting, everyone was polite. Members volunteered ideas, agreed with the project leader, and promised to support one another. The new team appeared united.

Three weeks later, the mood had changed.

Sales wanted to move faster. Operations wanted more time to test. Finance questioned the budget. Two experienced members began challenging the project leader’s decisions. Meetings became longer, and conversations continued privately after people left the room.

The manager became worried.

“We were working well at the beginning,” she said. “Now we have a teamwork problem.”

The team did have a problem—but the disagreement was not necessarily proof that teamwork had failed.

At the beginning, people had not yet worked together long enough to discover their real differences. Once the project became difficult, competing priorities, expectations, habits, and opinions surfaced.

The team had moved from politeness into friction.

This movement is part of team development.

The stages of team development describe how people move from being a collection of individuals to becoming a team capable of working through differences, coordinating action, and producing results together.

The best-known model describes five stages:

1. Forming
2. Storming
3. Norming
4. Performing
5. Adjourning

These stages provide a useful map, but they are not a fixed staircase. A team does not complete each stage once and leave it behind forever.

A new member can send a performing team back into forming. A new strategy can reopen storming. A crisis can expose weak norms. A leadership change can require people to redefine roles, decisions, and expectations.

Teams develop, adjust, regress, and develop again.

Understanding the stages helps leaders recognize what the team needs now. It also prevents them from treating every teamwork problem with the same activity.

For a broader discussion of shared goals, team effectiveness, team-building experiences, and daily follow-through, visit our complete guide to team building.

What are the stages of team development?

The stages of team development describe the changing questions a team must answer as its members learn to work together.

During forming, people ask:

What are we here to do, and where do I belong?

During storming, they ask:

Whose ideas will guide us, and how will we deal with our differences?

During norming, they ask:

How have we agreed to work together?

During performing, they ask:

How can we use our strengths to produce the result?

During adjourning, they ask:

What have we accomplished, learned, and left for those who continue the work?

These questions may not be spoken aloud, but they appear in people’s behavior.

A member who remains quiet during a new team’s first meeting may still be studying who has influence. Two managers arguing about priorities may be testing how decisions will be made. A team that creates a weekly review routine may be developing a norm. Members who solve a problem without waiting for the boss may be demonstrating mature team performance.

The stages help us interpret these behaviors. They do not excuse harmful conduct, poor leadership, or missed commitments. They help us understand what must become clearer, stronger, or more dependable.

Teams do not develop in a straight line

The familiar diagram often shows five stages arranged in one direction:

Forming → Storming → Norming → Performing → Adjourning

That sequence makes the model easy to remember. Real teams are less orderly.

A newly created team may begin storming before everyone has been properly introduced. A long-established group may perform exceptionally well in familiar work but return to forming when given a completely different assignment. A team may develop strong norms, only to discover that those norms protect comfort instead of performance.

Even one project can place different parts of the team in different stages.

Members may have strong relationships but remain unclear about the new objective. They may coordinate routine operations well while struggling to make strategic decisions. They may trust one another personally but avoid discussing missed commitments.

A team does not occupy a stage as neatly as a person occupies a room.

Use the stages as diagnostic lenses. Ask which developmental challenge is most visible and which question the team must answer next.

The purpose is not to label the team.

The purpose is to help it move.

Stage 1: Forming

Forming begins when people come together around a new team, goal, project, leader, or situation.

Members are trying to understand the assignment and find their place within the group. They look for signals about expectations, authority, acceptable behavior, and the people they can trust.

The team may appear cooperative. Meetings may feel positive because members are still being careful. They offer safe ideas, avoid strong disagreement, and wait for the leader to provide direction.

This politeness can be mistaken for unity.

But people may be carrying different answers to basic questions:

• What are we trying to accomplish?
• Which result matters most?
• What is my responsibility?
• Who has the authority to decide?
• How much can I challenge the leader?
• What can I expect from the other members?
• What will happen when something goes wrong?

Until these questions become clearer, the group may cooperate without being truly aligned.

What teams need during forming

A forming team needs direction, connection, and enough structure to begin working.

The leader must clarify why the team exists and what result requires people to work together. Members need to understand not only their individual roles but also where their work connects with everyone else’s.

This is also a useful time for relationship building. People are more likely to approach colleagues when they understand their backgrounds, strengths, responsibilities, and working preferences.

However, forming should not become an endless series of introductions and icebreakers.

The team must begin the work.

Suppose employees from sales, operations, finance, and customer service are brought together to improve client onboarding. It is useful for them to know one another personally. But they must also understand the customer result they share, where handovers currently break, and how their decisions affect the next person.

Connection helps people begin talking.

A shared objective gives them something important to talk about.

Useful team-building objectives during forming

A team-building experience for a forming team may help members:

• Build familiarity without forcing intimacy.
• Clarify the shared objective.
• Understand how their roles depend on one another.
• Recognize the strengths and resources available inside the team.
• Establish initial expectations for communication and coordination.
• Identify the first result they must achieve together.

This is where team bonding can support team development. Bonding reduces social distance, while team building connects those relationships to a shared result.

The proof of progress is not simply that members remember one another’s names. It is that they know why they need one another.

Stage 2: Storming

Storming begins when differences become difficult to ignore.

Members disagree about goals, priorities, responsibilities, methods, authority, pace, or standards. Informal alliances may appear. People may compete for influence, resist the leader, protect their territory, or question whether the team’s direction makes sense.

Storming can be loud.

Arguments happen during meetings. People openly challenge decisions. Frustration becomes visible.

But storming can also be quiet.

Members agree in front of the manager and resist afterward. They withhold information, delay commitments, avoid certain conversations, or complain privately to people who cannot solve the problem.

A silent team is not necessarily a harmonious team.

Sometimes it is a storming team that has learned to hide the storm.

Storming is not always a failure

Many leaders become uncomfortable when a previously polite team begins to disagree. They attempt to restore harmony as quickly as possible.

This can drive the real conflict underground.

A team cannot become effective by pretending its differences do not exist. Members must learn how to discuss competing ideas, raise risks, challenge assumptions, and make decisions without turning disagreement into personal attack.

Storming allows the team to discover whether people can face friction and continue working together.

The enemy is not disagreement.

The enemy is destructive or avoided disagreement.

Destructive disagreement attacks people, protects territory, and keeps reopening decisions. Avoided disagreement produces artificial agreement while important concerns remain unspoken.

Useful disagreement places the shared objective at the center. Members can say, “I see the situation differently,” explain what they see, listen to other perspectives, and help the team choose.

What teams need during storming

A storming team needs clarity and a healthier way to handle friction.

The leader must make it safe to raise concerns while maintaining standards for respectful behavior. Decision authority must become clear. Members need to know which decisions require consultation, who makes the final call, and what everyone must do after the decision is made.

The team must also learn to separate intention from impact.

A manager may intend to maintain quality but create delays by requiring approval for every small decision. A salesperson may intend to serve the customer but create operational problems by promising an unrealistic deadline. An employee may intend to avoid conflict but allow a preventable problem to grow.

Good intentions do not remove the need to examine the impact.

This is why one of the Team Bayanihan commitments is Face the Friction. The team does not search for conflict, but it refuses to allow an important problem to hide behind politeness.

Useful team-building objectives during storming

A purposeful experience may help a storming team:

• Surface different assumptions about the objective.
• Clarify decision authority and responsibilities.
• Practise disagreeing without attacking.
• Raise concerns while there is still time to respond.
• Identify recurring sources of conflict.
• Separate task conflict from personal conflict.
• Create a process for making and supporting decisions.
• Turn complaints into direct, useful conversations.

A recreational event may temporarily reduce tension. That can be valuable, but it will not resolve a disagreement about priorities, authority, or accountability.

When friction grows from the work, the team must eventually face the work.

Stage 3: Norming

Norming begins when the team develops shared expectations about how members will work together.

Roles become clearer. Communication becomes more direct. Members understand how decisions are made, how work is handed over, and what they can expect from one another.

People begin saying “we” with greater confidence because the team now has a recognizable way of working.

Norms are often informal.

No document may say that people should warn teammates early when a deadline is at risk. But members learn that this is what responsible teammates do. No policy may require employees to challenge an unclear request. But the team makes clarification part of its ordinary practice.

These repeated behaviors become the team’s operating system.

Not every norm is useful

Norming sounds positive, but teams can normalize weak behavior.

A team can develop a norm of arriving late. Members can learn not to question the most senior person. Departments can accept incomplete handovers because “that is how it has always been.” Employees can cover for missed commitments to avoid embarrassing their friends.

Consistency alone does not make a norm healthy.

A useful norm helps the team achieve its shared objective while respecting the people doing the work.

This is why leaders should not ask only, “What do we usually do?”

They should ask:

Does the way we usually work help us win together?

A team may need to keep some norms, strengthen others, and deliberately replace those that no longer serve the work.

From values to commitments

Words such as trust, respect, accountability, and collaboration are often displayed as team values. But each team must define what those words require during daily work.

Accountability might mean warning the team early when a commitment is at risk.

Respect might mean challenging the idea directly instead of criticizing the person privately.

Collaboration might mean giving the next person the complete information needed to continue the work.

Support might mean helping a teammate solve a problem without quietly taking ownership away from that person.

These definitions turn abstract values into team commitments.

At Team Bayanihan, five commitments help teams examine their everyday behavior:

• Play the Same Game — Protect the result everyone shares.
• Back Each Other Up — Offer support without removing ownership.
• Serve the Next Person — Complete your part so the next person can succeed.
• Face the Friction — Address what prevents the team from moving.
• Finish the Last Mile — Close the loop and complete the commitment.

A team does not need to adopt these exact words. It does need commitments that members can recognize, practise, and reinforce.

Useful team-building objectives during norming

A team-building experience may help a norming team:

• Turn lessons into practical working agreements.
• Define what trust, support, and accountability look like.
• Improve handovers between roles or departments.
• Create clear meeting and decision routines.
• Agree on how members will raise and resolve concerns.
• Establish a rhythm for reviewing commitments.
• Identify proof that the new practices are helping.

The team is no longer asking only, “Can we work together?”

It is deciding, “This is how we work together.”

Stage 4: Performing

Performing begins when the team can direct most of its energy toward producing the shared result.

Members understand the objective and how their contributions connect. They coordinate without waiting for the leader to manage every interaction. They raise concerns, adjust plans, share information, and offer support more naturally.

Conflict does not disappear.

In fact, performing teams may disagree frequently because people are willing to place difficult information on the table. The difference is that disagreement serves the result instead of consuming the team.

Members do not need to protect themselves from every challenge. They can question an idea, learn from failure, and change their approach without treating adjustment as defeat.

Performing is more than hitting a target

A group can achieve a target once through heroic effort, overtime, or the work of a few exceptional employees.

That does not necessarily make it a performing team.

Team performance includes the ability to produce results without repeatedly exhausting people, hiding risks, depending on one rescuer, or creating problems for another department.

A performing team becomes more capable through the work.

Members learn. They improve the system. They prepare other people to lead. They notice changes and adjust before the old plan fails completely.

The result matters, but so does the team’s growing ability to produce the next result.

This is the heart of team effectiveness. An effective team achieves a meaningful shared result, maintains the ability to work together, and becomes more capable of facing future challenges.

What leaders do during performing

Leaders sometimes interfere with a performing team by continuing to provide the same level of direction the group required during forming.

People ask for permission because the manager expects to approve everything. Good ideas slow down. Capable members stop taking initiative because authority never moves closer to the work.

The leader’s role must develop with the team.

Instead of controlling every action, the leader protects direction, provides context, removes barriers, strengthens decision capability, and helps the team prepare for the next challenge.

This does not mean disappearing.

Performing teams still need leadership. They need leaders who make the shared objective clear, maintain standards, examine evidence, and create room for others to contribute fully.

Useful team-building objectives during performing

A team-building experience for a performing team may help members:

• Respond to a larger or unfamiliar challenge.
• Improve decision-making under pressure.
• Strengthen shared leadership.
• Examine risks created by current success.
• Invite new perspectives and challenge old assumptions.
• Build greater adaptability.
• Prepare successors or new team members.
• Redesign a working practice that has reached its limit.

A performing team does not need a basic lesson about cooperation. It needs a challenge worthy of its present capability.

The experience should help members discover their next edge.

Stage 5: Adjourning

Adjourning happens when the team, project, or present form of the work comes to an end.

A project is completed. A temporary group is dissolved. Members move into new assignments. An organization restructures. A leader leaves. Two teams are combined into one.

People often focus on finishing the remaining tasks and quickly moving to whatever comes next.

But endings affect people and performance.

Some members feel proud. Others feel relieved, disappointed, uncertain, or sad. A team that has worked intensely together may lose an important source of identity and connection.

The organization can also lose valuable knowledge if members leave without reflecting on what they discovered.

What teams need during adjourning

An adjourning team needs closure, learning, appreciation, and a responsible transfer of unfinished work.

Members should examine what they accomplished, what helped them succeed, what they would do differently, and what the next team needs to know.

They should also close commitments.

Documents must be completed. Responsibilities must be transferred. Stakeholders need to understand what happens next. People who continue the work must not be left to reconstruct important decisions from scattered emails and memory.

Celebration matters here.

Recognition helps people see that their effort counted. It strengthens the stories the organization carries forward. But celebration should include more than awards and photographs. It should name the contributions, decisions, practices, and acts of cooperation that made the result possible.

Useful team-building objectives during adjourning

A closing experience may help the team:

• Recognize contributions and celebrate progress.
• Capture lessons and useful working practices.
• Complete or transfer remaining commitments.
• Rebuild relationships affected by difficult work.
• Prepare members for new roles or teams.
• Preserve stories that express the team’s best values.
• Identify what the organization should repeat or avoid.

Adjourning is not an unimportant final ceremony.

The way a team ends influences how people enter their next team.

How to recognize your team’s present stage

The following signs can help begin the conversation.

Stage	What you may observe	What the team may need
Forming	Politeness, uncertainty, dependence on the leader, unclear roles	Shared direction, role clarity, connection, first working agreements
Storming	Conflict, resistance, private complaints, competing priorities, power struggles	Honest dialogue, clear authority, conflict practices, shared priorities
Norming	Growing trust, stable routines, clearer expectations, stronger coordination	Practical commitments, useful norms, better handovers, review rhythms
Performing	Shared ownership, direct communication, adaptability, dependable execution	Stretch challenges, distributed leadership, innovation, renewal
Adjourning	Completion, transition, mixed emotions, knowledge-transfer risks	Reflection, recognition, closure, learning, responsible handover

Do not diagnose the stage from one meeting.

Look for repeated patterns. Ask members how work moves, where decisions get stuck, what happens when someone disagrees, and how the team responds when a commitment is at risk.

Most importantly, connect the stage to the shared objective.

The same behavior can have different meanings in different situations. A team that asks the leader many questions may be forming—or it may be responding to a leader who has refused to share authority. A quiet meeting may reflect clear alignment—or fear of speaking honestly.

The stages help organize inquiry. They should not replace it.

The enemy is stage blindness

Managers, HR leaders, and team-building organizers are not the enemy. Most genuinely want teams to succeed.

The enemy is stage blindness.

Stage blindness happens when we treat every team as if it has the same need.

A newly formed group receives an advanced problem-solving challenge before members understand the objective. A storming leadership team is sent to a recreational outing instead of facing its disagreement. A performing team is given basic activities about trust and communication. A project team disbands without capturing what it learned.

The activity may be well facilitated. It is simply designed for a different team.

Stage blindness also appears when leaders demand performing behavior from a team that has not been given forming clarity.

The manager says, “Take ownership,” but nobody knows who has the authority to decide.

She says, “Collaborate,” but departments are rewarded for conflicting targets.

She says, “Speak up,” but people who raise bad news are blamed for creating the problem.

Teams cannot skip the questions their stage requires.

Match team building to the stage

The stages of team development can improve the way organizations set team-building goals and objectives.

During forming, the central objective may be shared direction and interdependence.

During storming, the objective may be facing conflict and clarifying decisions.

During norming, the objective may be establishing team commitments and dependable routines.

During performing, the objective may be adaptability, shared leadership, or a more demanding result.

During adjourning, the objective may be learning, closure, and knowledge transfer.

This does not mean every team-building event should carry a label announcing the team’s stage. It means the experience should respond to what the team is trying to become capable of doing.

Begin with five elements:

Objective → Friction → Commitment → Practice → Proof

The stage helps you understand the team’s likely developmental objective.

The friction identifies the working pattern preventing progress.

The commitment describes how members will act differently.

Practice gives the team an opportunity to perform the behavior.

Proof shows whether the new commitment is helping during real work.

Suppose a recently merged team is in storming. Members protect their former departments, challenge one another’s procedures, and send most disagreements to the new department head.

The objective is not simply to “build camaraderie.” The team needs to make cross-functional decisions without turning every difference into a contest between the two former groups.

The friction is territorial thinking and unclear decision authority.

The team may choose this commitment:

We will place the shared customer result before the preference of our former department, bring relevant evidence into the discussion, and support the final decision after it is made.

Participants can practise this commitment during a carefully designed challenge. Afterward, the manager can use it during actual planning meetings.

The team then looks for proof. Are fewer decisions being escalated? Are members discussing evidence instead of defending territory? Do people support decisions consistently after leaving the meeting?

Now the experience has a job to do.

A team-building event does not move a team through every stage

A well-designed experience can create an important shift. It can help members see a pattern, practise a behavior, hold a conversation, or create a commitment.

But a team does not become performing simply because participants completed a day of activities.

Development continues during meetings, deadlines, handovers, customer problems, disagreements, and everyday decisions.

Leaders must reinforce the new behavior. Systems must support it. Members need opportunities to practise, review, and improve.

This is the difference between a team-building event and continuing team development.

Team building can create a focused experience around a developmental challenge. Team development carries the work across time as the team faces new situations and builds stronger capability.

The goal is not to make every intervention longer.

The goal is to stop pretending that one day can complete work that daily experience must continue.

When established teams return to forming and storming

Leaders sometimes say, “We have worked together for years. We should already be performing.”

Time alone does not produce team maturity.

A long-established team can return to forming when:

• A new leader arrives.
• Several new members join.
• The team receives a different mandate.
• The organization restructures roles.
• Two departments merge.
• A major customer changes its requirements.
• New technology changes the work.
• A crisis changes priorities and decision authority.

The same team can return to storming when its former agreements no longer fit the new situation.

This movement should not automatically be treated as regression. Sometimes it is evidence that the team is adjusting to reality.

The greater danger is pretending that nothing has changed.

Old roles remain in place even when the strategy requires new contributions. Members follow yesterday’s routines while the customer expects something different. Leaders demand unity around a direction nobody has had the opportunity to examine.

Mature teams are not teams that never reform or restorm.

They are teams that recognize the change, return to the necessary conversations, and move through them more skilfully.

Five questions that help a team move

When you are uncertain about the team’s stage, bring people back to five practical questions.

1. What result must we win together?

This clarifies the shared objective. It helps forming teams find direction and prevents established teams from protecting routines that no longer serve the result.

2. What is making that result difficult?

This surfaces the friction. It gives storming teams something more useful to discuss than personalities and blame.

3. What must we be able to expect from one another?

This begins the work of norming. Members turn broad values into specific commitments.

4. Where will we practise this during real work?

This bridges team building and everyday teamwork. The team identifies the meetings, handovers, decisions, or projects where the commitment must appear.

5. What proof will tell us we are improving?

This directs attention toward performance. The proof may be faster decisions, earlier risk reports, cleaner handovers, fewer reopened issues, or more commitments finished on time.

These questions do not force a team through a neat sequence. They help members address the work their development requires.

Do not ask, “Why can’t this team just perform?”

Forming teams need clarity before they can coordinate confidently.

Storming teams need a constructive way to face differences.

Norming teams need agreements that improve the work rather than merely protect comfort.

Performing teams need new challenges and room to exercise their capability.

Adjourning teams need to finish, learn, and leave the work in responsible hands.

Each stage carries a different developmental task.

The leader’s job is not to keep the team permanently comfortable. It is to help members answer the question their present situation has placed in front of them.

Sometimes that means providing direction.

Sometimes it means allowing useful disagreement.

Sometimes it means turning good intentions into firm commitments.

Sometimes it means stepping back so others can lead.

And sometimes it means helping people finish well.

The stages of team development are not labels for judging teams. They are a map for understanding movement.

Use the map to see where your team is. Name the result it must achieve. Face the friction keeping it from moving. Create a commitment members can practise, and watch for proof during real work.

A team does not become effective because it has avoided every storm.

It becomes effective because its members learn how to move through uncertainty, difference, agreement, action, and change—together.

If your organization wants a purposeful experience matched to your team’s present challenge, explore our facilitated team-building workshops.