Team Stages & Negative Dynamics
Key Takeaways
- Tuckman’s stages—forming, storming, norming, performing, adjourning—predict how Six Sigma teams behave as they form, conflict, align, deliver, and close.
- Recognition at milestones and at adjourning reinforces desired behaviors and supports sustainment after handoff.
- Negative dynamics include overbearing and dominant members, reluctant contributors, groupthink, feuding, floundering, rush to accomplishment, attribution errors, digressions, and tangents.
- Green Belts diagnose the stage and the dynamic, then choose facilitation responses rather than ignoring conflict or forcing premature decisions.
- BoK II.F.1 is Understand level: match scenarios to stages and name counterproductive team behaviors on the exam.
Team Stages & Negative Dynamics (CSSGB BoK II.F.1 — Understand)
Quick Answer: Teams typically progress through forming → storming → norming → performing → adjourning. Expect polite uncertainty early, conflict next, then shared norms, high delivery, and structured closure with recognition. Negative dynamics—overbearing or dominant members, reluctance, groupthink, feuding, floundering, rush to accomplishment, bad attribution, digressions, and tangents—need named interventions, not silence.
Green Belt projects are team sports. Even strong DMAIC tools fail when the team never gels, avoids conflict forever, or “agrees” on a weak fix. BoK II.F.1 expects you to understand team stages and counterproductive dynamics so you can recognize them in exam scenarios and on the Gemba.
Tuckman Stages Applied to DMAIC Teams
Bruce Tuckman’s model (with later adjourning) remains the ASQ-friendly language for how temporary project teams develop.
| Stage | What you see | Typical project moment | Leader / Green Belt focus |
|---|---|---|---|
| Forming | Politeness, role ambiguity, dependence on the belt or champion | Kickoff, first SIPOC workshop | Clarify charter, roles, ground rules, meeting cadence |
| Storming | Disagreement on problem framing, data, or workload; cliques | Scope fights, “my metric vs yours,” root-cause debates | Normalize conflict; facilitate; bring data; restate goals |
| Norming | Shared language, trust, routines, constructive challenge | Steady Define/Measure rhythm | Reinforce norms; hand more ownership to members |
| Performing | High autonomy, rapid problem-solving, strong collaboration | Analyze–Improve pilots, control design | Remove barriers; coach; avoid over-controlling |
| Adjourning | Closure energy, anxiety about handoff, pride or loss | Tollgate close, lessons learned | Document, transfer ownership, celebrate, capture learning |
Forming. Members size each other up. They may not challenge the charter even if scope is fuzzy. The risk is false harmony: everyone nods while the problem statement is still vague. Use the charter, SIPOC, and explicit working agreements early.
Storming. Disagreement surfaces. This stage is uncomfortable but healthy when conflict is about ideas and evidence, not personalities. Suppressing storming often produces later feuding or groupthink. Facilitation, parking lots, and decision rules (consensus vs recommend-to-sponsor) keep storming productive.
Norming. The team settles how it works: who pulls data, how minutes are kept, when to escalate. Norms can be positive (speak with data) or negative (never disagree with the senior manager). Green Belts explicitly reinforce useful norms.
Performing. Energy goes into analysis and experiments. Meetings are shorter and more decision-oriented. The belt shifts from directing every step to coaching methods and quality of thinking.
Adjourning. Temporary teams end. Without deliberate adjourning, knowledge walks out, the control plan is orphaned, and operators never hear “why we changed the work.” Closure includes lessons learned, resource release, and recognition.
Recognition
Recognition is not fluff; it is reinforcement. Effective recognition is specific, timely, and fair:
- Name the behavior or result (“reduced first-pass rejects 18% in pilot cell B”), not generic “great job, team.”
- Include sponsors, process owners, and frontline contributors—not only belts.
- Use mix of public (town hall, visual board) and private (thank-you from champion) channels.
- Link recognition to sustainment expectations after handoff, not only launch parties.
Exam stems that mention celebration, awards, or lessons-learned sessions at project end map to adjourning + recognition, not only performing.
Negative Team Dynamics
ASQ materials highlight patterns that stall progress. Learn the labels and the first response.
| Dynamic | Description | Typical intervention |
|---|---|---|
| Overbearing participant | Uses rank, expertise, or volume to shut others down | Private coach; structured turns; “round-robin” input; invite quieter members by name |
| Dominant participant | Talks most; monopolizes airtime (may not intend harm) | Timeboxes; written brainstorming first; facilitator enforces equal voice |
| Reluctant participant | Withholds ideas; may fear blame or lack expertise | Psychological safety; assign concrete tasks; pair with mentor; ask for Gemba expertise |
| Groupthink | Premature consensus; dissent suppressed; weak alternatives ignored | Devil’s advocate; anonymous idea capture; require two alternatives before decide |
| Feuding | Personal conflict between members or functions | Mediate offline; refocus on charter metrics; separate issues from personalities |
| Floundering | Unclear goals, methods, or next steps; meetings wander | Revisit charter; agenda with decisions; facilitator restates purpose |
| Rush to accomplishment | Jump to solutions before root cause or data | Re-anchor in DMAIC phase gates; require evidence criteria |
| Attribution error | Blame people (“lazy operators”) instead of system/process | Process walk; data stratification; “system not person” framing |
| Digressions / tangents | Side topics consume meeting time | Parking lot; timekeeper; agenda owner redirects |
Overbearing vs dominant: Overbearing often weaponizes status (“I’m the director—we’re doing X”). Dominant may simply be energetic and verbose. Both starve the room of ideas; both need structure.
Groupthink is especially dangerous in Improve: the team “agrees” on a favorite solution that never faced alternatives or FMEA. Techniques in II.F.3 (NGT, multivoting) reduce groupthink by separating idea generation from evaluation.
Rush to accomplishment shows up when a champion demands “a fix by Friday” and the team skips Measure. Green Belts protect the method without disrespecting urgency—scope a quick win only when the problem truly is trivial, and say so explicitly.
Attribution problems poison culture: if every defect is “operator error,” measurement system, training, and process design never get studied. Redirect to process and data.
Diagnosing Stage + Dynamic Together
A new team in forming that already rushes to solutions needs both charter clarity and a phase-gate reminder. A performing team that suddenly feuds may be under resource stress or an unclear handoff, not “bad people.” Exam questions often combine a stage cue (kickoff, first conflict, pilot success, closeout) with a dynamic cue (one person talks over others; no one challenges the VP).
Exam Focus
- Order of stages and what each looks like
- Adjourning includes knowledge transfer and recognition, not only a party
- Name the dynamic from a short vignette and pick the sensible facilitation response
- Storming is normal; unresolved storming becomes feuding or groupthink
Master the vocabulary, then practice matching one-paragraph team stories to stage and dynamic. That is the Understand-level skill CSSGB expects before you apply roles, RACI, and idea-generation tools in the next sections.
A Green Belt kicks off a new DMAIC team. Members are polite, look to the belt for every decision, and avoid challenging a vague problem statement. Which stage best describes this team?
During Improve, the team quickly unites behind the champion’s favorite software change, no alternatives are documented, and dissenters stay quiet in meetings. Which negative dynamic is most evident?