Study guide

13.3 Employees as Resources: Empowerment, Team Roles & Team Development

ASQ Certified Quality Inspector CQI

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Shop Mathematics & Algebra

1.1 Basic Shop Math & Precision Measurement 1.2 Basic Algebra & Technical Formulas 1.3 Measurement Systems & Unit Conversions

2 Chapter 2: Geometry & Applied Shop Trigonometry

2.1 Applied Shop Geometry 2.2 Right-Triangle Trigonometry 2.3 Shop Trigonometry Applications & Sine Bars

3 Chapter 3: Handheld Variable & Attribute Gages

3.1 Variable Hand Measuring Instruments 3.2 Fixed Attribute & Limit Gages 3.3 Transfer Gages & Precision Accessories 3.4 Special Gages: Electronic, Pneumatic, Force & Environmental Instrumentation

4 Chapter 4: Surface Plate Inspection, Optical Systems & CMMs

4.1 Gage Selection, Care & Environmental Control 4.2 Surface Plate Tools & Layout Inspection 4.3 Optical Comparators & Vision Systems 4.4 Coordinate Measuring Machines (CMM) & 3-2-1 Alignment 4.5 Gage Correlation & Cross-Instrument Agreement

5 Chapter 5: Surface Metrology, Calibration Systems & MSA

5.1 Surface Texture & Finish Measurement 5.2 Calibration Systems & NIST Traceability 5.3 Measurement System Analysis (MSA) & Gage R&R 5.4 Measuring Mass, Form & Profile, and Inclination

6 Chapter 6: Technical Drawing & Blueprint Reading

6.1 Engineering Drawing Structure & Conventions 6.2 Views, Sectioning & Feature Representation 6.3 Dimensions, Tolerancing & Fit Classifications

7 Chapter 7: Geometric Dimensioning & Tolerancing (GD&T)

7.1 GD&T Fundamentals & Datum Reference Frames 7.2 Material Condition Modifiers & Bonus Tolerance 7.3 Form & Orientation Tolerances 7.4 Location, Profile & Runout Tolerances

8 Chapter 8: Sampling Inspection & Acceptance Sampling Plans

8.1 Sampling Fundamentals & Operating Characteristic (OC) Curves 8.2 Attribute Sampling with ANSI/ASQ Z1.4 8.3 Variables Sampling with ANSI/ASQ Z1.9

9 Chapter 9: Inspection Planning, Processes & Material Disposition

9.1 Inspection Planning, Receiving & In-Process Inspection 9.2 First Article Inspection (FAI) & Documentation 9.3 Nonconforming Material Control & MRB 9.4 Inspection Errors & Human Factors 9.5 Product Traceability, Age Control & Shelf Life

10 Chapter 10: Materials Testing & Nondestructive Examination

10.1 Mechanical & Destructive Testing 10.2 Surface & Subsurface NDE Methods 10.3 Volumetric & Electromagnetic NDE Methods 10.4 Functionality, Force & Elastomer Hardness Testing 10.5 Software for Test Equipment & Software Validation

11 Chapter 11: Statistical Process Control & Process Capability

11.1 Statistics Fundamentals & Normal Distribution 11.2 Control Charts for Variables 11.3 Control Charts for Attributes & Run Rules 11.4 Process Capability & Performance Analysis

12 Chapter 12: Quality Systems, Continuous Improvement & Safety

12.1 The 7 Classic Quality Control Tools 12.2 Continuous Improvement & Problem-Solving Methodologies 12.3 Quality Management Systems, Audits & CAPA 12.4 Workplace Safety, Environmental Controls & PPE 12.5 Failure Mode and Effects Analysis (FMEA) & Fault Tree Analysis (FTA)

13 Chapter 13: Quality Fundamentals, Teams & Documentation Systems

13.1 Quality Improvement Concepts, Products & Processes 13.2 Audit Tools, Tracing Techniques & Audit Communication 13.3 Employees as Resources: Empowerment, Team Roles & Team Development 13.4 Quality Documentation, Reference Standards & Document Control

13.3 Employees as Resources: Empowerment, Team Roles & Team Development

Key Takeaways Explain This Topic AI

Empowerment requires four elements together — authority, information, resources, and accountability; granting authority without the other three sets people up to fail.

The team leader owns the content and the result, while the facilitator owns the process and stays neutral on the content — this is the most frequently tested team-role distinction.

Ground rules are the team’s own agreements about how it will work and are set by the team itself at its first meeting, not imposed by management.

A team charter defines purpose, scope, boundaries, deliverables, membership, resources, and measures of success, and its main practical function is preventing scope creep.

Tuckman’s stages run forming, storming, norming, performing, and adjourning; storming is a normal and necessary phase that a team must pass through rather than avoid.

Last updated: September 2026

Why the Body of Knowledge Includes Teams

An inspector rarely solves a quality problem alone. Material review boards, corrective action teams, first article reviews, kaizen events, and Six Sigma projects are all team activities, and the inspector is usually the member holding the data everyone else needs. Body of Knowledge topic IV.F.3 is tagged (Remember) , so the exam tests vocabulary and structure rather than facilitation skill.

Employee Empowerment

Empowerment is giving employees the authority and the means to make decisions about their own work. It is not a slogan and it is not delegation of blame. Real empowerment requires four elements together :

  • Element What it means What happens without it
  • Authority A defined right to act and to decide People escalate everything; nothing moves
  • Information Access to the data needed to decide well Decisions are guesses
  • Resources Time, tools, budget, training Good decisions cannot be executed
  • Accountability Ownership of the outcome, with support Authority becomes arbitrary

Grant authority without information and you get bad decisions. Grant authority without resources and you get frustration. Grant authority without accountability and you get inconsistency.

Empowerment in an Inspection Department

The clearest example is the inspector's authority to reject . A quality system that formally grants inspectors the authority to hold nonconforming material, and then routinely overrides it under schedule pressure, does not have empowered inspectors — it has an unenforced policy. Meaningful inspection empowerment includes documented authority to hold or reject, a defined escalation path when the decision is challenged, protection from reprisal, and the training and reference material to make the call correctly.

The manufacturing analogue is stop-the-line authority , expressed in the Toyota Production System as jidoka — building in the ability to stop when something abnormal occurs — signalled by an andon cord or light. The principle is identical: the person closest to the work is authorized to halt it when quality is at risk.

The Value Employees Add

Process knowledge. The operator who runs a machine every day knows things no engineer's study captures: which fixture is sticky, which tool degrades early, what the machine sounds like before it drifts.

Suggestion systems. Structured collection and evaluation of improvement ideas, with feedback given whether or not the idea is adopted. A suggestion system that never responds dies quickly.

Quality circles. Ishikawa's contribution — small voluntary groups from the same work area meeting regularly to identify, analyze, and solve their own quality problems.

Kaizen participation. Small continuous improvements owned by the people doing the work, covered in section 12.2.

Gemba insight. Observation at the actual place where work is done, which is where the facts are.

Near-miss and early-warning reporting. Reporting conditions that could have caused a defect, which requires a blame-free culture to function.

Team Types

  • Type Composition Typical purpose
  • Quality circle Volunteers from one work area Solve local problems in that area
  • Natural work team The people who work together daily Ongoing improvement of their own process

Cross-functional team Members from several departments Problems that cross boundaries — corrective action, new product launch

Self-directed work team Members manage their own scheduling and assignments Ongoing operation with minimal supervision

Virtual team Geographically distributed members Multi-site or supplier-involving issues

Project team Assembled for a defined objective, then dissolved A Six Sigma project, a launch, a specific investigation

Cross-functional membership is what makes corrective action work. A dimensional escape usually involves design, purchasing, production, maintenance, and quality, and a team drawn only from quality will produce a corrective action that only quality can implement.

Team Roles and Responsibilities

The BoK names facilitator, ground rules, and team charter specifically, but the full role set is testable.

Role Responsibility

Sponsor / champion Senior manager who authorizes the team, removes organizational obstacles, supplies resources, and accepts the result

Team leader Owns the content and the outcome; runs meetings, assigns tasks, reports progress

Facilitator Owns the process , not the content; keeps discussion productive and balanced; remains neutral on the subject matter

  • Scribe / recorder Captures decisions, actions, owners, and due dates; produces the minutes
  • Timekeeper Keeps the team to its agenda
  • Team member Contributes expertise, completes assigned actions, attends
  • Subject matter expert Contributes specialized knowledge, often on an as-needed basis
  • Leader Versus Facilitator

This is the most frequently tested distinction in the topic.

The team leader is invested in the answer. The leader wants the problem solved a particular way, advocates positions, and is accountable for the result.

The facilitator is deliberately neutral about the answer . The facilitator's job is that the team reaches its own good decision: drawing out quiet members, restraining dominant ones, keeping the discussion on the agenda, surfacing disagreement rather than burying it, and choosing the right tool for the moment. A facilitator who starts advocating a technical position has stopped facilitating.

For that reason, facilitators are often drawn from outside the team's own function, and a facilitator who is also the leader compromises both roles.

Ground Rules

Ground rules are the team's explicit agreements about how it will operate. Typical examples:

Meetings start and end on time; attendance is expected, and a delegate is sent when a member cannot attend.

One conversation at a time; no side discussions.

Every member speaks; no one dominates.

Disagree with ideas, not with people.

Decisions are supported by data, not by seniority or volume.

Decisions are made by consensus, with a stated fallback if consensus fails.

What is said in the room stays in the room, unless the team agrees to share it.

Action items always have a named owner and a due date.

Two facts about ground rules are testable. First, the team sets its own ground rules , normally at its first meeting; rules imposed by management are compliance requirements, not ground rules, and they do not produce the same ownership. Second, ground rules are only useful if they are enforced , and enforcing them is a core facilitator responsibility — usually by referring to the posted rule rather than by criticizing the person.

The Team Charter

A team charter is the written authorization and definition of the team. It is produced at the start, approved by the sponsor, and revisited when circumstances change.

Charter element Purpose

Problem or purpose statement Describes the problem in factual, measurable terms without presuming a cause or a solution

  • Business case Why this matters — cost, risk, customer impact
  • Scope and boundaries What is in, and explicitly what is out
  • Goal and success measures The specific, measurable target
  • Deliverables What the team will produce
  • Membership and roles Who is on the team and in what role
  • Resources and authority Time, budget, access, and what the team may decide without escalating
  • Milestones and timeline Checkpoints and end date
  • Sponsor approval Signature authorizing the work

The charter's most valuable practical function is preventing scope creep . A team chartered to reduce bore-position defects on one part family will be asked, repeatedly, to also fix surface finish, then the fixture design, then the supplier's packaging. The written boundary is what lets the leader decline without conflict. The second function is preventing the most common failure of improvement teams: a problem statement that contains a solution . "Install a new fixture on the boring machine" is not a problem statement; "bore position on part 10025 exceeds tolerance on 6.2% of units, causing $94,000 in annual scrap" is.

Stages of Team Development

Bruce Tuckman's model is named directly in the BoK and must be known in order.

Stage Behavior What the team produces Leader and facilitator action

Forming Polite, tentative, dependent on the leader; members test boundaries and look for direction Little real output Provide structure, clarify the charter, make introductions, establish ground rules

Storming Conflict over goals, roles, approach, and authority; frustration; some members disengage Output often dips Do not suppress the conflict; surface it, return to the charter and data, enforce ground rules, clarify roles

Norming Agreement on roles and methods; ground rules become habits; trust builds Output rises Step back, reinforce the norms, let the team make decisions

Performing Cohesive, self-managing, focused on the task; disagreement is productive Peak output Support and remove obstacles; intervene rarely

Adjourning Task complete; recognition and closure; some sense of loss Final deliverable and handoff Document results, verify handoff, recognize contributions, capture lessons learned

Two points the exam presses:

Storming is normal and necessary. A team that appears to skip it usually has not aligned; it has suppressed disagreement, which resurfaces later as passive resistance. The facilitator's job in storming is to make the conflict about ideas and data rather than about people.

Adjourning is a real stage that adds a fifth step to the original four-stage model, and skipping it costs the organization the lessons learned and leaves the improvement without a documented owner.

Teams also regress . Adding a member, changing the sponsor, or a major change in scope typically drops a performing team back to forming or storming, and the leader should expect it rather than treat it as failure.

Making Decisions as a Team

Method How it works When it fits

Consensus Everyone can live with and will actively support the decision, even if it is not their first choice Important decisions requiring commitment to implement

Majority vote More than half decide Low-stakes or time-pressured choices

Multivoting Members distribute a limited number of votes across a long list to narrow it Reducing many candidate causes or ideas to a workable few

Nominal group technique Silent individual idea generation, round-robin sharing, clarification, then ranking Avoiding dominance by senior or loud members; equalizing input

Authority decision with input The leader decides after hearing the team Genuine emergencies and decisions outside the team's authority

Consensus is not unanimity. Consensus means every member can support the decision in action, even while preferring a different option. Treating consensus as unanimity gives every member a veto and paralyzes the team.

Groupthink is the failure mode in which cohesion suppresses dissent and the team converges prematurely on a comfortable answer. Countermeasures include assigning someone to argue the opposing case, soliciting outside review, and using nominal group technique to collect independent views before any discussion.

Common Exam Traps

Facilitator versus leader. The facilitator owns the process and is neutral on content; the leader owns the content and the result.

Ground rules come from the team , not from management.

Storming is expected , not a sign of a bad team.

Adjourning is a stage , and the five-stage sequence is forming, storming, norming, performing, adjourning.

Consensus is not unanimity.

A charter's problem statement must not contain a solution.

Empowerment needs all four elements. Authority alone is not empowerment.

Quality circles are voluntary and drawn from one work area , which distinguishes them from cross-functional project teams.