Bruce Tuckman 5 Stages of Group Development in Lean Six Sigma Teams
A Lean Six Sigma project can have the right charter, the right data, and the right tools, yet still struggle because the team has not learned how to work together. Process improvement is technical, but it is also deeply human.
Bruce Tuckman’s model helps explain why teams often feel awkward at the start, tense in the middle, productive later on, and reflective at the end. His original model described four stages of group development in 1965: Forming, Storming, Norming, and Performing. The fifth stage, Adjourning, was added later with Mary Ann Jensen.
For Lean Six Sigma teams, this model is especially useful because projects often bring together people from different departments, roles, shifts, and levels of experience. A Green Belt might lead a team with operators, supervisors, finance analysts, quality specialists, maintenance technicians, and customer service staff. Each person sees the process from a different angle.
That variety is powerful, but it also creates friction. Understanding the Bruce Tuckman 5 Stages of Group Development in Lean Six Sigma Teams helps project leaders prepare for that friction instead of treating it as failure.
Why Tuckman’s model matters in Lean Six Sigma
Lean Six Sigma projects are built around structured problem solving. Teams define the problem, measure the current state, analyze root causes, improve the process, and control the gains. That structure is usually known as DMAIC.
But DMAIC does not remove the need for trust, communication, and shared responsibility. In fact, it often exposes weak spots in team dynamics.
A team may ask questions such as:
Who owns this process?
Can we trust the data?
Are we solving the real problem or someone’s favorite problem?
Will this change make daily work easier or harder?
Who decides when the solution is ready?
Tuckman’s five stages give leaders a practical way to read the room. When a team is quiet, it may not mean agreement. When people argue, the project may still be healthy. When the team becomes faster and more independent, the leader should step back rather than control every move.
The model is not a rigid timeline. Teams may move back and forth between stages, especially when the scope changes, a key member leaves, or new data challenges earlier assumptions. Still, the pattern is common enough to be useful.
Stage 1. Forming is when the team comes together
Forming is the first stage of group development. The team is new, roles are unclear, and people are still figuring out the purpose of the project and where they fit.
At this stage, team members tend to be polite and cautious. They may avoid disagreement because they do not yet know how open the group is to challenge. People look to the project leader, sponsor, or facilitator for direction.
Common characteristics of forming include:
High interest but limited clarity
Polite conversation
Unclear roles and expectations
Dependence on the leader
Questions about goals, scope, timing, and authority
Limited trust because people have not worked together yet
In a Lean Six Sigma project, forming often happens during the Define phase. The team reviews the project charter, problem statement, business impact, high-level process map, and customer requirements.
For example, a hospital team may start a project to reduce patient discharge delays. The team includes nurses, case managers, physicians, pharmacy staff, transport staff, and admissions coordinators. At the first session, everyone agrees that discharge delays are a problem, but each person sees a different cause. Some point to late medication orders. Others mention missing transportation. Others believe the issue starts with unclear discharge criteria.
At this point, the team does not need instant agreement on root cause. It needs a shared frame for the work.
A Lean Six Sigma leader can help the forming stage by:
Clarifying the problem statement
Confirming what is in scope and out of scope
Explaining DMAIC in plain language
Defining roles such as sponsor, process owner, team member, and data owner
Setting meeting norms and decision rules
Asking each person what they need from the team to contribute well
The main risk during forming is false alignment. Everyone nods, but people leave with different assumptions. A strong charter review, SIPOC diagram, and voice of the customer discussion can prevent confusion later.
Stage 2. Storming is when tension and conflict surface
Storming is the stage where differences become visible. Team members challenge assumptions, question data, debate priorities, and test the boundaries of the group.
This stage can feel uncomfortable, but it is often necessary. Lean Six Sigma depends on finding real causes, not surface symptoms. That means teams must be willing to question old habits and compare opinions with evidence.
Common characteristics of storming include:
Disagreement about the problem or solution
Frustration with project pace
Confusion over responsibilities
Resistance to data collection
Concerns about workload or blame
Competing priorities between departments
Pushback against proposed changes
In a Lean Six Sigma project, storming often appears during the Measure and Analyze phases. This is where teams discover that the process is more complex than expected. Data may be incomplete. Definitions may vary by shift or location. People may disagree about what counts as a defect.
For example, a manufacturing team works on reducing defects in a packaging line. Operators believe the main issue is machine wear. Maintenance believes operators are skipping setup checks. Quality staff believe the inspection standard is not clear. The supervisor worries that the project is becoming a blame exercise.
This conflict is not a reason to abandon the project. It is a signal that the team needs better facts and better conversation.
A project leader can guide storming by:
Keeping the discussion focused on the process, not personal blame
Using data definitions so everyone measures the same thing
Facilitating root cause tools such as fishbone diagrams and 5 Whys
Making disagreements visible on flip charts or boards
Asking quieter members to share observations
Separating facts, assumptions, and opinions
Returning to the customer need and project goal
Storming becomes harmful when the leader avoids it or shuts it down too quickly. If people cannot raise concerns, they may disengage. If conflict turns personal, the team may lose trust. The goal is not to remove disagreement. The goal is to make disagreement useful.
Stage 3. Norming is when the team builds working agreements
Norming is the stage where the team starts to settle into a productive rhythm. Members understand the project purpose, accept their roles, and develop shared ways of working.
The team may still disagree, but the conflict becomes less personal and more focused. People begin to trust the process and each other. They know how decisions are made, how data is reviewed, and how tasks move forward.
Common characteristics of norming include:
Clearer roles and responsibilities
Better communication
Growing trust
Shared definitions and standards
More balanced participation
Greater willingness to help across functions
Agreement on how the team handles decisions and conflict
In Lean Six Sigma, norming may show up as the team moves deeper into Analyze or begins the Improve phase. The team has cleaned up the data, confirmed the main causes, and agreed on how to test solutions.
For example, a call center team is working to reduce repeat customer calls. At first, agents, team leads, and process analysts disagreed about the cause. After reviewing call categories and listening to sample calls, the team agrees that unclear handoff notes create many repeat contacts.
During norming, the group sets clear standards:
Agents will use the same call reason categories.
Team leads will audit a small sample each week.
Analysts will update the run chart before each project session.
The team will test one script change before changing the full workflow.
These agreements reduce noise. The team no longer spends every meeting debating basic definitions. That leaves more time for improvement work.
Lean Six Sigma tools can support norming well. A RACI chart can clarify responsibilities. Standard work can define the preferred method. A data collection plan can align measurement. Visual management can show progress without long explanations.
At this stage, the leader should still guide the work, but not dominate it. The team is learning to manage itself.
Stage 4. Performing is when the team delivers results
Performing is the stage where the team reaches high productivity. Members are confident, focused, and able to work through issues with less direction. Trust is stronger, roles are clear, and the group can make good decisions faster.
This is the stage most leaders want from the beginning, but it usually has to be earned. Performing depends on the earlier work of forming, storming, and norming.
Common characteristics of performing include:
High ownership
Strong collaboration
Fast problem solving
Open communication
Productive use of data
Flexibility when barriers appear
Focus on results and sustainability
In Lean Six Sigma, performing often appears during the Improve and Control phases. The team tests countermeasures, studies results, adjusts the solution, and creates controls to hold the gains.
For example, a warehousing team wants to reduce picking errors. After analysis, the team identifies unclear bin labeling and similar-looking product locations as major causes. During the Improve phase, the team pilots new labels in one zone, changes the pick path, and adds a simple verification step for high-risk items.
A performing team does not wait for the project leader to solve every issue. When the pilot exposes a new problem, the picker, supervisor, and inventory specialist review it together. They adjust the layout and update the standard work. They check the data again before wider rollout.
That is performing in practice: not perfection, but quick learning with shared ownership.
The project leader’s role changes here. Instead of pushing every task, the leader protects focus, removes barriers, and makes sure the team does not skip control planning. Performing teams can move fast, but Lean Six Sigma gains must be held. Control plans, training, process owners, reaction plans, and visual checks keep the improvement from fading.
Stage 5. Adjourning is when the team closes the project
Adjourning is the final stage. The project ends, the team disbands or shifts to other work, and members reflect on what they achieved and learned.
This stage is easy to ignore. Many organizations rush from one project to the next. Yet adjourning matters because it turns project experience into organizational learning.
Common characteristics of adjourning include:
Completion of project work
Handoff to the process owner
Reflection on lessons learned
Recognition of team contributions
Documentation of new standards
Mixed feelings about the team ending
Transition to daily management or future projects
In Lean Six Sigma, adjourning usually happens once the Control phase is complete. The team has validated the improvement, created control methods, trained the right people, and handed ownership back to the operation.
For example, a finance team completes a project to reduce invoice rework. The new process includes clearer intake requirements, an updated checklist, and weekly defect tracking. Before closing the project, the team reviews what worked, what was harder than expected, and what future teams should know.
A strong project closeout might include:
A final review with the sponsor
Updated standard operating procedures
A control plan with named owners
Before-and-after process maps
Lessons learned
Recognition for team members
A list of follow-up opportunities
Adjourning also protects the project result. If no one owns the new process after the team ends, old habits can return. The handoff is not paperwork. It is the bridge between project success and lasting performance.
How leaders can use the five stages during DMAIC
Tuckman’s model becomes more useful when project leaders connect it to daily team behavior. The table below shows how the stages often align with Lean Six Sigma work.
Tuckman stage | Common Lean Six Sigma moment | What the leader should watch for | Helpful response |
Forming | Define phase | Polite agreement, unclear scope, hidden assumptions | Clarify charter, roles, goals, and decision rules |
Storming | Measure and Analyze phases | Data disputes, resistance, blame, competing priorities | Use facts, define measures, facilitate fair discussion |
Norming | Analyze and Improve phases | Better trust, clearer roles, shared working methods | Lock in agreements, assign ownership, keep communication steady |
Performing | Improve and Control phases | Fast testing, shared ownership, fewer escalations | Remove barriers, protect focus, build control plans |
Adjourning | Project closeout | Loose handoff, rushed documentation, loss of learning | Recognize work, transfer ownership, capture lessons learned |
This is not a perfect one-to-one match. A team can return to storming during Improve if a pilot fails or if a new stakeholder joins late. A team can also move quickly through forming if members have worked together before.
The value is awareness. When leaders can name the stage, they can choose a better response.
Practical signs that a Lean Six Sigma team is stuck
Some teams do not move smoothly through the stages. They get stuck.
A team stuck in forming keeps revisiting the project purpose. Meetings feel pleasant, but little gets decided. The fix is clearer structure.
A team stuck in storming keeps arguing without learning. People defend departments instead of studying the process. The fix is better facilitation, clearer data, and stronger ground rules.
A team stuck in norming may become too comfortable. Members agree with each other but avoid hard experiments. The fix is to return to the project goal and test changes in real conditions.
A team stuck in performing may move so fast that it under-documents the solution. The fix is to slow down enough to create controls.
A team stuck in adjourning may never truly close. The project fades away without ownership. The fix is a formal closeout and process owner handoff.
The real lesson for project success
Tuckman’s five stages do not replace Lean Six Sigma tools. They make those tools work better.
A fishbone diagram works best when people feel safe sharing causes. A control chart is more useful when the team agrees on the measure. A pilot test improves faster when team members trust each other enough to report problems early. A control plan lasts longer when the process owner accepts the handoff.
For project leaders, the lesson is simple: manage the work and the team. Both matter.
Forming needs clarity. Storming needs honest, structured conflict. Norming needs shared agreements. Performing needs focus and ownership. Adjourning needs closure and learning.
When Lean Six Sigma teams understand these stages, they stop seeing tension as a sign that something is wrong. They learn to read it as part of the journey from a group of individuals to a team that can improve a process and sustain the result.
Comments