According to the model in this lesson, what do teams pass through as they mature?
Choose an answer, then check it.
Management & Leadership · Foundations
Team Development
On this page 9 sections
In 30 seconds
Team development The process by which a group of people becomes a working team, moving through stages as it matures; the model in this lesson comes from Bruce Tuckman. Full entry → is the process by which a group of people becomes a working team, moving through stages as it matures. The model in this lesson comes from Bruce Tuckman: Forming The polite first stage, when members are introduced, stay cautious, and look to the leader for structure and direction. Full entry →, Storming The conflict stage, when members assert their ideas, test roles and processes, and clash over goals and control. Full entry →, Norming The stage when the team agrees on ground rules, roles settle, and members begin to trust and respect one another. Full entry →, and Performing The stage when the team is self-directed and focused on results, needing little management direction. Full entry →, with Adjourning The closing stage, when the team disbands at the end of a project and members reflect on what they accomplished. Full entry → added in 1977 for when a project ends. Real teams loop back and skip stages, and conflict in the early stages is normal, not failure. Leaders adjust their support to the stage the team is in.
Why this matters
Anyone who has worked in a group has felt the stages: the polite first meeting, the arguments, the moment things finally click. Knowing the model changes what those moments mean. Early conflict stops looking like a broken team and starts looking like a normal step that can be worked through. A leader who knows the stages gives the team what it needs at each one: direction while it forms, patience and structure during storming, and room to run once it performs. Teams that understand development also recover faster when a new member or a new task knocks them back a stage.
The college version
What team development is: the working definition
Team development is the process by which a group of people becomes a working team, moving through stages as it matures. The definition this lesson follows the model developed by Bruce Tuckman and presented in OpenStax's Principles of Management: teams and team members start from friendliness and excitement, and then the real work begins—and as they work, they move through recognizable stages. OpenStax is careful to call them stages, not ages: a team does not graduate from one to the next like a student moving up a grade. The stages describe how the group's relationships and its way of working change over time. The model has five stages in this lesson—forming, storming, norming, performing, and adjourning—because Tuckman added the fifth, adjourning, in 1977 to describe what happens when a team disbands at the end of a project. What a team is, how to resolve conflict, and how to communicate well each get their own topics.
The five stages: forming, storming, norming, performing, adjourning
Forming is the polite opening stage. Members are introduced, stay cautious, and focus on similarities; the group looks to the leader for structure and direction, and enthusiasm mixes with uncertainty about roles. Example: at Northgate, a regional grocery co-op, five coworkers meet for the first time as the online-ordering project team and wait for the store manager to explain what to do first. Storming is the conflict stage. Members assert their ideas, test roles and group processes, and clash over goals, tasks, and progress; OpenStax calls it the win-lose stage, and frustration builds. Example: at Northgate, the designer and the software developer argue for a week over whether checkout should work on phones, and two members start choosing sides. Norming is the settling stage: ground rules are agreed, roles become clear, responsibility is shared, and trust grows. Example: after the manager sets clear decision rules, the Northgate team adopts a weekly review and stops re-litigating settled choices. Performing is the self-directed stage: the team has confidence and momentum, needs little management direction, and focuses on results; the strongest teams, OpenStax notes, optimize both task and people relationships. Example: Northgate's team ships the system and handles new issues without daily supervision. Adjourning is the closing stage: the project ends, the team disbands, and members reflect on the work and the relationships they built.
Why stages matter: early conflict is normal
The stages matter because they give a name to experiences almost every team has, and the most valuable name is storming. When a new team argues, members often conclude the team is broken. The model says otherwise: storming is where real differences surface—about goals, methods, roles, and control—and those differences need to surface before the team can genuinely agree. OpenStax describes storming as the stage when the attitude about the team and the project shifts negative and frustration builds around goals, tasks, and progress. Corporate Finance Institute adds the constructive side: conflict can be healthy when managed constructively, because it can lead to better decision-making and team cohesion. And Wikipedia's summary of Tuckman records that he described the phases as necessary and inevitable for a team to grow, face challenges, and deliver results. That is the honest insight of this lesson: early conflict is not evidence that the team is failing; it is evidence that the team has started doing real work together.
Stage versus reality: loops, skips, and slides
The model is a map, not a schedule. OpenStax is explicit that the stages are not linear: when a team member is added, the change can disrupt the dynamic enough to cause a backwards slide to an earlier stage, and a new project task that creates confusion can do the same; the team has to re-group and will likely re-form and re-storm before getting back to performing. CFI agrees, noting that a new member can take a team working well at the norming stage back to storming, and that team development is not a linear process. Teams also skip: a group that has worked together before may pass through forming in a single meeting, and a routine task may never produce a real storm. The practical reading is simple. Watch for the stage the team is actually in, not the stage the calendar says it should be in. When a change arrives—a new member, a new task, a new leader—expect the team to dip back, and treat the dip as normal regrouping rather than a crisis.
The leader's role, and what maturity looks like
Different stages need different support. OpenStax notes that a forming team looks to the leader for structure and direction, while a performing team is self-directed and needs little management direction. CFI fills in the middle: in forming, leaders provide clear direction and establish goals; in storming, they encourage open communication and mediate conflicts; in norming, they reinforce positive behavior; in performing, they step back and allow autonomy; and in adjourning, they acknowledge contributions and provide closure. The general practice, stated simply: give more structure early, more room later, and steady attention to the team's relationships the whole way. Maturity shows up as smoother work. A performing team does not necessarily work harder than a brand-new one; it works with less friction, because roles, norms, and trust are already in place. That is the performance connection: mature teams spend their energy on the task instead of on sorting out how to work together, and the strongest of them get results while preserving the relationships that let them keep performing.
Eli explains
The same idea, in plain words
Explain it like I’m 10
Team development is how a group of people slowly becomes a real team. Most teams pass through the same stages. Forming: everyone is polite and figuring out who does what. Storming: people disagree, argue, and test one another. It feels bad, but it is normal, and it is how real issues surface. Norming: the team agrees on how to work, roles settle, and trust grows. Performing: the team runs itself and gets results. Adjourning: the project ends and the team wraps up. Real teams do not march through these stages in a straight line. They loop back, skip stages, and slide backward when someone new joins. Storming is a stage, not a failure.
Picture it like this
Think of a band learning a new song. First rehearsal: everyone is polite, watching the sheet music, waiting for the singer to count in. Then the disagreements start; the drummer thinks the tempo is too fast, the bassist wants a different ending, and the singer is frustrated. That is storming. Slowly they settle on an arrangement and the song comes together; that is norming. By the night of the gig they play it without cues; that is performing. Then the set ends and they pack up; that is adjourning.
Where the picture stops working
The analogy has limits. A band's members usually know their instruments from the start, while a work team may form with people who have never worked together and whose roles are unclear. A band can also choose its members; many teams get no say in who joins, and one new member can knock the whole group back to storming. And bands rehearse a fixed song, while work teams keep getting new tasks, which is why the stages repeat.
Worked example
Follow Northgate, a regional grocery co-op, as it builds a new online-ordering system. The five-person project team forms at a first meeting where everyone is polite and the store manager lays out the schedule. In storming, the designer and the software developer argue for a week about whether the checkout should work on phones, and two members start choosing sides. After the manager sets up a weekly review and clear decision rules, the team norms: roles settle, and the group agrees on how to test new ideas. In performing, the team ships the system and handles problems without daily supervision. When the project ends, the team adjourns: members hold a wrap-up meeting, review what worked, and move to other roles.
Key takeaway
Team development is the process by which a group becomes a team, moving through forming, storming, norming, performing, and adjourning. Early conflict is a normal stage, not failure; teams loop back and skip stages; and leaders adjust their support to the stage the team is in.
Quick check
3 questions here, of 5 in this lesson’s practice set. Answers stay hidden until you check.
Five coworkers at Northgate, a grocery co-op, form a project team to launch online ordering. At the first meeting everyone is polite, no one challenges the proposed schedule, and the group waits for the store manager to explain what to do first. Which stage of team development is the team in?
Choose an answer, then check it.
Three weeks in, the Northgate team argues openly: one member wants a phone-first checkout, another insists on a desktop-first design, and a third says they are both overcomplicating it. Two members have started trading messages about the fight before meetings. What does this lesson say about what is happening?
Choose an answer, then check it.
Study tools & related lessonsYou’ll learn to · Common mistakes · Easily confused · Key vocabulary · Related
You’ll learn to
- State the working definition of team development, attributed to Tuckman's model as presented by OpenStax's Principles of Management.
- Name the five stages of Tuckman's model—forming, storming, norming, performing, and adjourning—with one line and one original example for each.
- Explain why conflict in the early stages is normal rather than a sign of failure.
- Describe how real teams loop back and skip stages, and name one event that can slide a team backward.
- Explain how a leader's support changes as a team moves through the stages.
- Describe how team development connects to performance: mature teams work more smoothly and need less direction.
Common mistakes
Reading storming as failure.
Early conflict looks like a broken team, but the model says storming is a normal stage where real differences surface. The task is to work through it, not to declare the team doomed.
Expecting a straight line.
Teams do not reliably march through forming, storming, norming, and performing in order. A new member or a confusing new task can slide a team backward, and some teams skip stages entirely.
Leading every stage the same way.
A forming team needs direction; a storming team needs open communication and mediation; a performing team needs autonomy. One style for all stages ignores what the team actually needs.
Skipping closure.
Treating adjourning as an afterthought wastes the chance to acknowledge contributions and capture lessons that the next project could use.
Confusing a mature team with a conflict-free team.
A performing team still disagrees; the difference is that disagreements get handled through the norms the team built instead of flaring into storms.
Easily confused
Forming vs. Storming
Forming is the polite, cautious opening stage, when members look to the leader and avoid conflict; storming is the stage when members assert ideas, test roles, and clash. Both are early stages, and one usually leads into the other.
Performing vs. Adjourning
Performing is the stage of self-directed, high-output work; adjourning is the closing stage when the project ends, the team disbands, and members reflect on the work and the relationships they built.
Key vocabulary
- Team development
- The process by which a group of people becomes a working team, moving through stages as it matures; the model in this lesson comes from Bruce Tuckman.
- Forming
- The polite first stage, when members are introduced, stay cautious, and look to the leader for structure and direction.
- Storming
- The conflict stage, when members assert their ideas, test roles and processes, and clash over goals and control.
- Norming
- The stage when the team agrees on ground rules, roles settle, and members begin to trust and respect one another.
- Performing
- The stage when the team is self-directed and focused on results, needing little management direction.
- Adjourning
- The closing stage, when the team disbands at the end of a project and members reflect on what they accomplished.
- Regression
- A slide back to an earlier stage of development, often triggered by a new member joining or a new task disrupting the group.
- High-performing team
- A team that has optimized both its task work and its relationships among members, maximizing performance and effectiveness.
Sources & references
- Principles of Management, Section 15.2: Team Development Over Time — OpenStax, Rice University
- Understanding Tuckman's Team Development Stages: The 5 Stages Explained — Corporate Finance Institute (CFI)
- Tuckman's stages of group development (Wikipedia) — Wikipedia
EliExplains lessons are original prose written from the open, credible references above. See Copyright & Licensing.
Researched 2026-08-22
Educational content only. It is not medical, legal or professional advice. Found an error? Tell us.