Section III — Team Management ~10%
Section III carries 15 of the 150 scored questions. Its four parts are team formation, team facilitation, team dynamics and team training. It tests the interpersonal and organizational skills the Black Belt needs to lead project teams effectively. Questions often present realistic team scenarios — a disruptive member, resistance to a solution, a team stuck in conflict — and ask what the BB should do.
Team formation and stages
Tuckman’s model is the standard framework for team stages of development (part of team facilitation):
| Stage | What happens | BB’s role |
|---|---|---|
| Forming | Team members are polite, roles are unclear, little disagreement | Clarify charter, roles, and ground rules; high directive leadership |
| Storming | Conflict over direction, roles challenged, subgroups form | Facilitate conflict resolution; keep focus on charter; coach not command |
| Norming | Norms established, cohesion builds, trust increases | Step back; let team self-manage; reinforce positive norms |
| Performing | High productivity, shared goals, minimal conflict | Remove obstacles; celebrate wins; prepare for transition |
| Adjourning | Project ends; team disbands; lessons learned captured | Recognize contributions; document lessons; hand off to process owner |
Team formation and team training
- Team formation: team types (improvement, cross-functional, self-directed, virtual) and their constraints; roles (sponsor, champion, facilitator, team leader, timekeeper, scribe, member); selecting members for the skills and process knowledge the project needs; launching with a clear charter, ground rules and decision method.
- Team dynamics: recognizing and handling group behaviors such as groupthink, dominant or reluctant participants, digressions, and unquestioned acceptance of opinions as facts.
- Team training: assess training needs, design and deliver the training, then evaluate whether it worked (for example, did on-the-job behavior and results change, not just test scores).
Note: organization-wide change management (including models such as ADKAR) is covered in Section I (Leadership), not here.
Conflict resolution approaches
| Approach | When to use | When to avoid |
|---|---|---|
| Collaborating (win-win) | Both issues and relationship matter; time available | When a quick decision is needed |
| Compromising | Both parties can give something; time-constrained | When one side has a clearly better answer |
| Forcing / competing | Quick decision needed; stakes high; authority clear | Team buy-in is required for implementation |
| Accommodating | Issue is minor for you but important to others; relationship priority | Ceding ground repeatedly undermines authority |
| Avoiding | Issue is trivial; cooling-off period needed | When ignoring the issue lets it grow |
Facilitation tools
- Brainstorming: Generating many ideas quickly without criticism; affinity diagrams (one of the seven management and planning tools in Section IV) then group them
- Nominal Group Technique (NGT): Structured brainstorm + vote to prevent groupthink and give quiet members equal voice
- Multi-voting: Reducing a long list of ideas by giving each member a fixed number of votes
- Force field analysis: Mapping driving forces (for change) and restraining forces (against change) to plan where to focus
Try the free 25-question CSSBB diagnostic: questions across all 9 BoK sections, with an explanation for every answer and a score by section.
Take the free CSSBB diagnosticRelated: Team dynamics · Change management (ADKAR, Section I)
All CSSBB sections
CSSBB Quest by Bizarre Act. Original study material; not affiliated with ASQ. CSSBB is a certification of ASQ. Terms · Privacy