At its first meeting, a project team can agree enthusiastically on a goal and still leave with four different ideas about who will make the decisions. A week later, those unspoken differences may surface as disagreement about priorities or missed work. Bruce Tuckman’s model offers a way to examine how a group moves from initial orientation through conflict and shared norms toward coordinated work.
The model’s early movement from forming a group, through storming over differences, to establishing norms is a proposed pattern, not a schedule. A change in membership or an unexpected task can reopen questions the team thought it had settled. Looking at what members actually need is more useful than assigning the group a permanent label.
Forming, Storming, Norming: The Proposed Sequence
In a 1965 review of small-group research, psychologist Bruce Tuckman proposed a sequence in which groups develop both their relationships and their approach to a task. The familiar four stages are forming, storming, norming, and performing. In a later review with Mary Ann Jensen, adjourning was added to describe the ending of a group’s work.
The sequence forming, storming, norming, performing offers a vocabulary for recurring challenges: orientation, disagreement, agreement on working practices, and coordinated action. A team does not necessarily experience each challenge cleanly or in the same way. The model is a lens for asking questions about a group, not a test that predicts exactly what it will do next.
Imagine a team of four people organizing a neighborhood repair event. One person knows local volunteers, another manages the budget, a third understands repairs, and a fourth handles publicity. They have six weeks to arrange a venue and invite residents. The example is hypothetical, but it makes the differences between the stages concrete: the task stays recognizable while the team’s working relationships change.
Forming: Finding the Task and Each Other
At the first meeting, members want to know what the event is meant to achieve, how much money is available, and who has authority to commit resources. They may be polite and cautious, especially if they have not worked together before. The volunteer coordinator assumes the event will be small; the publicity lead imagines a neighborhood-wide campaign. Both support the goal, but the goal has not yet been defined tightly enough for planning.
Useful work at this stage includes stating the purpose, identifying constraints, and making immediate responsibilities visible. The team can agree that the first event will serve a limited number of visitors, assign someone to check venue availability, and set a date for a decision on publicity. These steps do not eliminate uncertainty, but they give members enough shared information to begin. The early transition from team formation through disagreement to shared rules depends on making those expectations discussable.
A leader or facilitator can ask what each person expects from the others and how decisions will be made. The answers may reveal disagreements early, when they are still relatively easy to discuss. An agenda and a brief record of decisions also help members who were absent or reluctant to interrupt.
Storming: Making Differences Discussable
The repair specialist later argues that the team should limit attendance to match the number of available volunteers. The publicity lead wants a broader invitation and worries that a small event will disappoint residents. Both concerns are reasonable, but the group must resolve the tension between reach and capacity before publishing the announcement.
In the model, this is the kind of disagreement associated with storming. The issue may concern the task, authority, workload, or relationships. It need not involve shouting: a team can show conflict through repeated delays, private complaints, or decisions that are quietly revisited. Equally, disagreement is not evidence that the members are failing; it may reveal an important choice that was hidden by early politeness.
From disagreement through shared rules to productive work, the team must make assumptions explicit. How many repairs can volunteers realistically handle? What would happen if more residents arrive than expected? A small registration system and a waiting list might protect capacity while allowing wider publicity. The important action is to decide how evidence will settle the question, not to require everyone to feel equally enthusiastic about the same proposal.
If a disagreement becomes personal, the facilitator can separate the claim from the person making it and give each member time to explain the risk they see. A decision rule matters too: the team should know whether the group must reach consensus, whether one person has final authority, and how a decision can be reconsidered if new information appears.
Norming: Making Agreements Usable
After the attendance decision, the team begins to establish routines. Members agree to update a shared task list, raise budget changes before committing money, and use a brief weekly meeting to identify obstacles. These norms coordinate work because they make expectations visible. They are more useful than a general promise to communicate better, which each member might interpret differently.
Norming can also involve clearer relationships. The publicity lead knows when to ask the repair specialist to verify a claim, and the volunteer coordinator knows who can approve a purchase. A practical sign of progress is that the same confusion occurs less often and unresolved issues reach someone able to address them.
Agreement has a potential cost if members stop raising concerns for fear of disrupting harmony. A useful norm therefore includes a way to challenge a decision. For example, any member can flag a safety concern, and the group will decide who must review it before the event proceeds. The purpose of a norm is to support reliable work, not to silence disagreement.
Reviewing norming, storming, forming in reverse reveals the questions the team had to answer: how to coordinate, how to handle differences, and how to orient itself. The reverse order is a way to review the history; the proposed developmental sequence begins with forming.
Performing: Coordinating Around the Work
As the event approaches, volunteers report a shortage of a particular tool. The team checks the budget, asks a local partner for a loan, and updates the repair schedule. Members can act without holding a full meeting for every small decision because they understand the goal, know their responsibilities, and have a route for escalating a problem.
This is the practical meaning of coordinated performance in the model. The team still encounters difficulties and may disagree about solutions. What changes is its ability to use established relationships and working practices to address those difficulties while continuing the task. The progression from open disagreement to shared norms and effective work is about coordination, not a promise of frictionless collaboration. Earlier conflict, emerging agreements, and coordinated performance can overlap when the work changes.
A team can protect that capacity by reviewing whether its routines still serve the task. If a weekly meeting has become a long status recital, a written update and a shorter meeting for decisions may work better. If one member has become the bottleneck for every approval, delegating a defined range of decisions may help. The appropriate adjustment depends on the actual obstacle, not on a stage name alone.
When the Pattern Changes or the Work Ends
Suppose a venue cancels two weeks before the event and a new partner joins to provide space. The original team may have to revisit the purpose, redistribute authority, and negotiate unfamiliar constraints. Those conversations can resemble earlier orientation or conflict even though the group has already worked productively together. Similarly, a new member may need explanations of routines that established members take for granted.
A return to questions about formation, disagreement, and group rules is therefore not necessarily a failure. The team can explain existing decisions, invite the newcomer to identify gaps, and revise responsibilities where the task has changed. The movement between conflict, shared expectations, and joint work may be uneven; different parts of a team can also face different challenges at the same time.
Tuckman’s proposal was based on a review of group studies, and the later review called for further empirical work. Its enduring usefulness lies in the questions it prompts: Are members clear about the task? Is a disagreement being addressed? Are working agreements helping? Those questions do not establish that every group follows the same order or needs the same intervention.
When the repair event is over, adjourning gives the team a chance to close commitments: thank volunteers, settle expenses, return borrowed tools, and record lessons for anyone organizing the next event. A short review can identify which agreements helped and which need to change, while acknowledging that the people involved may move on to different work.
