The Five Stages of Team Development: What Teams Need at Each Stage

A team can be talented, well-intentioned, and still struggle to work together. People may be careful in early conversations, disagree once the real work begins, settle into more useful habits, and eventually perform with greater trust and autonomy. When the work ends or the team changes, the group has another transition to manage.

The five stages of team development are forming, storming, norming, performing, and adjourning. Bruce Tuckman introduced the first four stages in 1965. Tuckman and Mary Ann Jensen added adjourning in 1977.

The model is useful because it gives teams shared language for patterns that otherwise feel personal or mysterious. It is not a diagnostic test, a performance score, or a promise that every team will move through five neat boxes in order. Teams can revisit earlier dynamics when a new leader arrives, priorities shift, pressure rises, membership changes, or the work itself becomes less clear.

The practical question is not, "What label should we give this team?"

It is, "What does this group need from us now?"

The five stages at a glance

Stage	What may be happening	What the team needs	A useful leadership move
Forming	People are learning the task, the group, and what is safe to say	Purpose, boundaries, roles, and access to context	Make the work and expectations visible
Storming	Different assumptions, interests, styles, or power dynamics surface	A fair way to disagree, clarify, and decide	Slow down the interpretation and surface the real tension
Norming	The group develops shared expectations and repeatable ways of working	Explicit agreements, feedback, and reinforcement	Turn emerging habits into visible team practices
Performing	People coordinate with greater trust, clarity, and autonomy	Space to execute, good information, and protection from unnecessary friction	Delegate decisions while keeping outcomes and risks visible
Adjourning	Work, membership, or the team itself is ending or changing	Closure, learning, recognition, and a usable handoff	Capture what mattered before people disperse

No stage is a moral judgment. Storming does not mean the team is broken. Performing does not mean the team will never struggle again. Adjourning is not an administrative afterthought. Each stage contains real work.

1. Forming: people are looking for context

Forming begins when a group comes together around new work. That can mean a newly hired team, a cross-functional project, a reorganization, a new manager, or an established team taking on an unfamiliar goal.

Early politeness is common. People may be enthusiastic while still holding back questions, disagreement, or uncertainty. They are trying to understand the task and the social environment at the same time.

What forming can look like

Meetings are cordial but vague.
A few confident people carry most of the conversation.
Team members wait for the leader to define the "right" response.
Roles, decision rights, and boundaries are assumed rather than confirmed.
People agree in the room, then leave with different interpretations.

What the team needs

A forming team needs more than introductions. It needs enough shared context to participate responsibly.

Make these things visible:

Why the team exists and what outcome it owns
What is in scope and out of scope
Who decides, who contributes, and who needs to be informed
What constraints are already real
Where questions, risks, and disagreement should go
How the group will communicate and follow through

Do not demand trust before the operating conditions support it. Start by being reliable, answering real questions, and making it safer to say, "I do not understand yet."

A practical forming activity: The Working Start

Time: 15 to 25 minutes
Best for: 3 to 9 people
Materials: Shared document, whiteboard, or one sheet of paper

Ask each person to complete these prompts silently:

I believe this team is responsible for...
A strong outcome would look like...
One dependency or constraint we need to respect is...
One question I do not want us to carry silently is...
One thing I need from this group to contribute well is...

Compare the responses. Do not rush to wordsmith a perfect team charter. First identify where the answers materially differ. Those differences are the real forming work.

2. Storming: the differences are finally visible

Storming begins when the work becomes real enough to expose different priorities, interpretations, working styles, or levels of authority.

The name makes this stage sound louder than it always is. Some teams storm through open debate. Others storm quietly through side conversations, slow decisions, repeated rework, passive agreement, missed handoffs, or a pattern of revisiting the same issue.

What storming can look like

People use the same words but mean different things.
A disagreement about process is actually a disagreement about power or risk.
Team members defend their functions rather than the shared outcome.
Decisions keep returning because authority was never clear.
Feedback is interpreted as resistance, disrespect, or lack of commitment.
The group is "nice" in meetings and frustrated everywhere else.

What the team needs

The goal is not to eliminate disagreement. The goal is to make disagreement usable.

A storming team needs:

A shared description of the issue before solutions begin
Separation between observation and interpretation
Clear decision authority
Space for material concerns without rewarding endless debate
A record of what was decided, what remains open, and who owns the next move

One of the most useful facilitator moves is to replace accusation with verification.

Instead of: "Why are you blocking this?"

Try: "What risk or requirement do you believe the current direction does not address?"

Instead of: "We already aligned on this."

Try: "What do each of us believe was decided, and where is that decision recorded?"

If a team is separating facts from interpretations and trying to understand why reasonable people see the same situation differently, the free Perspective Mapping Facilitation Guide provides a structured 65-minute activity.

3. Norming: turn helpful behavior into a team practice

Norming happens when the group begins to establish shared expectations, more predictable relationships, and repeatable ways of working.

This stage can feel like relief after storming, but it has its own risk: the team may rely on unwritten habits that only current members understand. A routine is not yet an operating agreement if no one can explain it, teach it, or revisit it.

What norming can look like

People know how to raise a concern without derailing the work.
Roles are clearer, even when responsibilities overlap.
Meetings have recognizable purposes and outputs.
Team members ask each other for help earlier.
The group can explain how it makes and records decisions.
Feedback becomes more specific and less threatening.

What the team needs

Make emerging norms explicit enough to be reused and challenged.

Document agreements about:

Communication channels and response expectations
Meeting purposes and attendance
Decision rights and escalation paths
Handoffs and ownership
How the team handles disagreement
How risks, blockers, and changes become visible
When the group will review whether the agreements still work

The test is simple: could a new team member understand how work moves without relying on private coaching from one person?

If several operating issues are showing up at once, explore the DOaaS facilitation kits built around alignment, decision-making, ownership, prioritization, and follow-through.

4. Performing: protect clarity without adding control

Performing teams can coordinate with greater independence because people understand the work, one another, and the system around them. They can disagree without treating every difference as a relationship crisis. They can act without waiting for the leader to translate every next step.

Performing does not mean constant harmony, maximum speed, or heroic effort. A team that is exhausted, dependent on one expert, or quietly carrying unresolved risk may produce impressive output without being healthy or resilient.

What performing can look like

People make appropriate decisions close to the work.
Handoffs contain the context the next person actually needs.
Risks surface before they become emergencies.
Meetings are used for real interaction, not status theater.
Team members challenge ideas while protecting the shared outcome.
The group adapts its process without losing accountability.

What the team needs

The leader's job shifts from defining every move to protecting the conditions for good work.

That includes:

Keeping priorities and decision boundaries clear
Removing organizational friction the team cannot remove itself
Protecting focus from unnecessary work
Maintaining access to relevant information
Recognizing contributions without creating competition for visibility
Watching for dependency, overload, silence, and false confidence

Do not reward a performing team by filling every available inch of capacity. High performance needs margin for thinking, recovery, learning, and change.

5. Adjourning: close the work on purpose

Adjourning covers endings and transitions. A project finishes. A temporary team disbands. A reorganization changes membership. A leader leaves. Work moves to a different owner.

Teams often treat this stage as a calendar event instead of a group-development responsibility. The final deliverable ships, everyone moves on, and the learning disappears with the team.

What adjourning can look like

People are proud, relieved, disappointed, or uncertain at the same time.
Important context lives in scattered files and individual memory.
Unfinished decisions or risks do not have a clear home.
Contributions go unrecognized because attention has already shifted.
The next team receives artifacts without the reasoning behind them.

What the team needs

Close four loops:

Outcome: What was completed, changed, or learned?
Ownership: What remains open, and who owns it now?
Transfer: What context must move with the work?
Recognition: What contributions and relationships deserve acknowledgment?

A useful closeout is not a victory lap or a blame session. It is a deliberate transfer of value.

The Spider Web Context Map: make the hidden system visible

The spider web is a useful metaphor for team context.

Every web contains threads, anchor points, and signals. In a team, the threads may be projects, workflows, relationships, or decisions. Anchor points may be customers, leaders, partner teams, policies, vendors, or technical systems. A vibration may be feedback, a delay, a new requirement, or a risk moving through the system.

A leader near the center may feel the whole web. A person working at the edge may see only the few threads they touch. Neither view is automatically wrong. The context is unevenly distributed.

The Spider Web Context Map turns that metaphor into a practical team activity.

When to use it

Use the map when:

A new team is forming around complex work
A team is storming around dependencies or competing interpretations
A hybrid team has uneven access to context
One person has become the unofficial translator for everything
A reorganization or leadership change has altered the system
The group is preparing for a handoff or closeout

Do not use it to force public discussion of sensitive employee matters, formal grievances, legal concerns, or issues that require qualified independent support.

Time, participants, and materials

Time: 30 to 40 minutes
Participants: 3 to 9 people
Materials: Shared whiteboard or large sheet of paper, markers, and sticky notes
Output: One visible map, two or three context gaps, and one agreed repair

How to run the activity

Name the center. Write the shared outcome, customer need, or responsibility in the middle. If the group cannot agree on the center, stop there. That is the first issue to resolve.
Draw the main threads. Add the major workstreams, roles, or processes connected to the outcome.
Add the anchor points. Mark the people, teams, systems, decisions, or constraints that hold each thread in place.
Mark the signals. Note where feedback, changes, risks, or approvals enter the web. Identify who feels each signal first and who learns about it last.
Find fragile threads. Circle unclear ownership, overloaded connectors, missing context, duplicated paths, or single points of failure.
Compare perspectives. Ask, "What can you see from your position that the rest of us may not see?" Record differences without immediately deciding which view is correct.
Repair one part. Choose one meaningful improvement: clarify an owner, change a handoff, create a shared record, move a decision closer to the work, or schedule a specific follow-up.

The point is not to produce a beautiful diagram. The point is to help people see how their strand connects to the wider system.

How long does each stage last?

There is no reliable universal timeline for any stage. A team may form quickly around familiar work and then spend months storming around authority or tradeoffs. Another group may establish useful norms early but return to forming when several new members join.

Stage length depends on factors such as:

Stability of membership and leadership
Clarity of the outcome
Degree of task interdependence
Access to information
Decision authority
Organizational pressure
Prior relationships and history
Whether the group makes time to address how it works

Use the stages as a conversation aid, not a countdown clock.

Common mistakes when using the model

Treating storming as failure

Conflict can reveal ambiguity, incompatible goals, missing authority, or real risk. Suppressing it may make the team look calmer while the problem moves into private channels.

Assuming a team has one stage

A group may be performing in a familiar workflow and forming around a new responsibility at the same time. Discuss the stage in relation to specific work.

Diagnosing the team from above

Leaders have more organizational context, but they do not automatically have the most complete view of day-to-day team dynamics. Ask the group what it experiences.

Confusing friendliness with alignment

People can like one another and still hold incompatible assumptions about the work. Alignment requires a shared, usable understanding, not just a pleasant meeting.

Trying to facilitate beyond the method's limits

A team activity cannot replace formal authority, human resources support, legal guidance, safety processes, or an independent facilitator where power and consequences require one.

Frequently asked questions

What are the five stages of team development?

The five stages are forming, storming, norming, performing, and adjourning. The original 1965 model described the first four. Adjourning was added in 1977 to account for how groups complete, separate, or transition their work.

Which stage is the hardest?

Storming often feels hardest because differences become visible, but difficulty depends on the team and its context. Forming can be difficult when the purpose is unclear. Norming can fail when agreements stay implicit. Adjourning can be difficult when the work or relationships matter deeply.

Can teams skip a stage?

Do not assume every team will display every stage in an obvious or linear way. Some dynamics may be brief, quiet, overlapping, or specific to one part of the work. Teams can also revisit earlier dynamics after a change.

What helps a team move from storming to norming?

Make the disagreement specific, clarify decision authority, separate observation from interpretation, name the required tradeoff, and record the agreement. The goal is not forced consensus. It is a workable way to address differences and move responsibly.

What team building activity works during forming?

Use an activity that creates practical context, not just personal disclosure. The Working Start prompts in this article help people compare their understanding of purpose, outcomes, constraints, questions, and support needs.

Do the stages apply to remote and hybrid teams?

They can provide useful language for remote and hybrid teams, but distributed work changes how the dynamics appear. Storming may show up as message avoidance, uneven meeting participation, delayed decisions, or different versions of context across tools and time zones.

What happens when a new person joins a performing team?

Part of the team may return to forming while established members continue performing. Give the new person access to the outcome, decision rules, operating agreements, current risks, and the reasoning behind important choices. Do not make them reconstruct the web one private conversation at a time.

The model is a map, not the work

The five stages help a team name what it may be experiencing. The value comes from choosing a response that fits the situation.

Forming needs context.
Storming needs a fair way to surface and work through differences.
Norming needs explicit, reviewable agreements.
Performing needs autonomy with visible outcomes and risks.
Adjourning needs closure, transfer, and recognition.

The team does not need to "graduate" from one label to another. It needs to make the next useful part of the work visible.

Make different perspectives easier to work with

If your team is in the messy middle, start by separating what happened from what people think it meant. The free Perspective Mapping Facilitation Guide gives you a complete 65-minute agenda, facilitator language, common watch-outs, and a reusable working artifact.

Get the free Perspective Mapping guide

References

Bruce W. Tuckman, Developmental Sequence in Small Groups, 1965.
Bruce W. Tuckman and Mary Ann C. Jensen, Stages of Small-Group Development Revisited, 1977.