Study guide
4.3 Team Success Factors and Ground Rules
ASQ Certified Six Sigma Black Belt CSSBB
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Introduction & CSSBB Exam Strategy
1.1 CSSBB Exam Format, Scoring, and Testing Windows 1.2 Eligibility, Project Affidavits, Application, and Recertification 1.3 Open-Book Strategy, Reference Materials, and a 16-Week Study Plan
2 Chapter 2: Organization-Wide Planning and Deployment
2.1 Fundamentals of Six Sigma and Lean Methodologies 2.2 Selecting the Right Methodology: DMAIC, DFSS, and Lean 2.3 Business Systems, Processes, and Stakeholder Relationships 2.4 Strategic Planning and Deployment of Six Sigma Initiatives 2.5 Six Sigma Roles and Responsibilities 2.6 Organizational Barriers and Common Causes of Six Sigma Failure 2.7 Change Management: Stakeholder Analysis, Readiness, and Communication
3 Chapter 3: Organizational Process Management and Measures
3.1 Impact of Six Sigma Projects on Customers, Suppliers, and Stakeholders 3.2 Benchmarking Types and Performance Goal Setting 3.3 Performance Measures: Balanced Scorecard, KPIs, KBIs, OKRs, and Line of Sight 3.4 Leading and Lagging Indicators and Performance Dashboards 3.5 Financial Measures: Revenue Growth, Margin, NPV, ROI, and Cost-Benefit Analysis 3.6 Cost of Poor Quality and Hard versus Soft Savings
4 Chapter 4: Team Management
4.1 Team Types and Constraints 4.2 Team Roles, Responsibilities, and Member Selection 4.3 Team Success Factors and Ground Rules 4.4 Motivational Techniques and Overcoming Demotivators 4.5 Stages of Team Development and Conflict Resolution 4.6 Team Communication Plans 4.7 Team Leadership Models: Direct, Coach, Support, and Delegate 4.8 Group Behaviors, Conflict Resolution, and Meeting Management 4.9 Facilitation Techniques and Team Decision-Making Methods 4.10 Team Training: Needs Assessment, Delivery, and Evaluation
5 Chapter 5: Define Phase
5.1 Customer Identification and Segmentation 5.2 Customer Data Collection: Methods, Validity, and Reliability 5.3 Customer Requirements: CTX, CTQ Trees, and Operational Definitions 5.4 The Kano Model and Quality Function Deployment 5.5 SIPOC and Process Mapping 5.6 Business Case Justification 5.7 The Project Charter and the Problem Statement 5.8 Project Scope and Boundaries 5.9 SMART Goals and Project Performance Measurements 5.10 Project Charter Reviews and Toll-Gate Governance 5.11 Project Management Tools: Gantt Charts, Toll-Gate Reviews, WBS, and RACI 5.12 Analytical Tools Used Throughout the DMAIC Cycle
6 Chapter 6: Measure Phase
6.1 Process Flow Metrics and the Hidden Factory 6.2 Process Analysis Tools and Value Stream Mapping 6.3 Types of Data and Measurement Scales 6.4 Sampling Concepts, Methods, and Sample Size for Estimation 6.5 Data Collection Plans and Common Pitfalls 6.6 Gage R&R for Variable Measurement Systems 6.7 Attribute Agreement Analysis and Audit MSA 6.8 Measurement Systems Across the Organization, and Metrology 6.9 Population Parameters, Sample Statistics, and Valid Statistical Conclusions 6.10 Descriptive Statistics: Central Tendency, Dispersion, and Shape 6.11 Graphical Methods for Exploratory Data Analysis 6.12 Probability Concepts, Common Distributions, and the Central Limit Theorem 6.13 Additional Distributions: Hypergeometric, Exponential, Lognormal, Weibull, and Bivariate 6.14 Process Capability and Performance Indices 6.15 Capability Studies, Attributes Capability, Yield Metrics, and Long-Term Capability
7 Chapter 7: Analyze Phase
7.1 The Correlation Coefficient, Its Confidence Interval, and Causation 7.2 Linear Regression and Residual Analysis 7.3 Multivariate Tools: Factor Analysis, Discriminant Analysis, and MANOVA 7.4 Hypothesis Testing Terminology, Errors, and Single-Sample Tests 7.5 Statistical Versus Practical Significance 7.6 Sample Size for Hypothesis Tests 7.7 Point Estimates, Confidence, Prediction, and Tolerance Intervals 7.8 Tests for Means, Variances, and Proportions 7.9 Analysis of Variance 7.10 Chi-Square Goodness-of-Fit and Tests of Independence 7.11 Types of Risk and Failure Mode and Effects Analysis 7.12 Gap Analysis and Root Cause Analysis 7.13 Waste Analysis: The Seven Classic Wastes and Resource Under-Utilization
8 Chapter 8: Improve Phase
8.1 Design of Experiments: Objectives, Terminology, and Effects 8.2 DOE Design Principles: Randomization, Blocking, Replication, and Resolution 8.3 Planning and Evaluating Designed Experiments 8.4 One-Factor Experiments: Completely Randomized, Randomized Block, and Latin Square Designs 8.5 Full Factorial Experiments and Design Selection 8.6 Two-Level Fractional Factorial Experiments and Confounding 8.7 Response Surface Methodology and Optimization 8.8 Waste Elimination: Pull Systems, Kanban, 5S, and Poka-Yoke 8.9 Cycle-Time Reduction: Continuous Flow, SMED, and Heijunka 8.10 Kaizen, Kaizen Blitz, Theory of Constraints, and OEE 8.11 Implementation Planning, Piloting, and Solution Selection
9 Chapter 9: Control Phase
9.1 SPC Objectives, Variable Selection, and Rational Subgrouping 9.2 Control Charts for Variables Data 9.3 Control Charts for Attributes Data 9.4 Short-Run SPC and Moving Average Charts 9.5 Control Chart Analysis: Common Cause, Special Cause, and Run Rules 9.6 Total Productive Maintenance and Visual Controls 9.7 Measurement System Reanalysis 9.8 Control Plan Development and Process Owner Handoff 9.9 Lessons Learned, Documentation, and Training for Sustainment 9.10 Ongoing Evaluation of the Improved Process
10 Chapter 10: Design for Six Sigma (DFSS)
10.1 DFSS Frameworks: DMADV, DMADOV, and Design Transfer 10.2 Design for X (DFX) 10.3 Robust Design, Parameter Design, and Verification 10.4 Tolerance Design and Statistical Tolerancing
4.3 Team Success Factors and Ground Rules
Key Takeaways Explain This Topic AI
The four success elements named in the Body of Knowledge are management support, clear goals, ground rules, and timelines.
Each element maps to a checkable artifact: a signed charter, a quantified goal statement, a written ground-rules list, and a toll-gate schedule with dates.
Ground rules must be written by the team rather than issued to it, and must include an enforcement mechanism.
A goal is clear only when it names the metric, the baseline, the target, and the date.
Absent management support shows as unfunded solutions and unattended toll gates, not as spoken opposition.
Last updated: August 2026
Four elements, four artifacts
Success element Artifact that proves it exists Characteristic failure if missing
Management support Charter signed by a sponsor with authority over the whole process, with named resources and a funding band Solutions identified but never implemented
Clear goals A goal statement naming metric, baseline, target, and date Endless analysis; scope creep; disputed closure
Ground rules A written, team-authored list with an enforcement mechanism Meetings dominated by two voices; decisions revisited
- Timelines Toll-gate schedule with dates and deliverables Perpetual Measure phase
- Treat these as a checklist for the first two weeks. If any artifact does not exist, the team does not
have that element regardless of what anyone says.
Management support
Support is a behaviour, not a statement. The observable tests:
Has the sponsor signed the charter , and does the sponsor's authority cover every function the
process crosses?
Are named resources -- Black Belt hours, SME hours, data access -- written into the charter and
agreed by the members' managers?
Is there a pre-agreed funding band for implementation, so the solution does not queue for a
capital cycle after the analysis is complete?
Does the sponsor attend toll gates, and are the meetings held on schedule?
A sponsor who endorses the project publicly but never attends a toll gate has withdrawn support in
the only currency that counts.
Clear goals
A goal is clear when four elements are present: Goal = metric + baseline + target + date \text{Goal} = \text{metric} + \text{baseline} + \text{target} + \text{date} Goal = metric + baseline + target + date
Weak : "Improve invoice accuracy." Clear : "Reduce the invoice error rate on first submission from 4.7% (Jan-Jun baseline, 18,400
- invoices) to 1.5% by 30 November."
- The clear version does three jobs at once: it defines what data must be collected, it defines when
the project is finished, and it prevents the argument at closure about whether the goal was met.
- Goal-setting mechanics are treated fully in the Define chapter under SMART objectives; here the point
- is that goal clarity is a team success factor , because ambiguity about the target is what
produces endless analysis.
Ground rules
Ground rules are the team's own operating agreement. Two properties make them work:
Authored by the team. Rules issued to a team are ignored; rules the team wrote are enforced by
the team. Spend twenty minutes on this in the kickoff.
Enforced by an explicit mechanism. Name who calls a breach and what happens. Usually the
facilitator calls it, in the moment, without escalation.
A workable starting set:
Start and end on time; the meeting ends at the stated time even if the agenda is unfinished.
One conversation at a time; no side discussions.
Pre-work is mandatory; a member who has not done it does not vote on that item.
Data beats opinion; a claim about the process must be accompanied by evidence or logged as a
hypothesis to test.
Disagree in the room, align outside it -- once a decision is recorded, the team speaks with one
voice.
Silence is not consent; the facilitator will ask each member directly before recording a decision.
Actions have an owner and a due date, or they are not actions.
- The two rules that most reliably change team behaviour are "data beats opinion" and "silence is
- not consent" . The first converts arguments into experiments; the second is the antidote to
groupthink and to the phenomenon of decisions reversing themselves in the corridor afterwards.
Timelines
A DMAIC project without dates does not finish; it fades. The minimum artifact is a toll-gate schedule:
- Toll gate Deliverable Typical elapsed
- Define Signed charter, SIPOC, VOC-to-CTQ translation, project plan Week 2-3
- Measure Validated measurement system, baseline capability, data collection complete Week 6-9
- Analyze Root causes confirmed statistically, hypothesis tests documented Week 11-14
- Improve Solutions piloted, results verified, implementation plan approved Week 16-20
- Control Control plan in place, process owner accepted, benefits validated by finance Week 20-24
- Two disciplines make the schedule real. Toll gates are decisions, not presentations : the sponsor
- either approves the phase, sends it back with specific gaps, or kills the project. And the Measure
- phase gets a hard date , because it is where projects stall -- there is always more data to collect,
and the honest question is whether more data would change the decision.
Diagnosing a struggling team
- Symptom Most likely missing element
- Analysis is thorough but nothing has been implemented Management support (funding, authority)
- The team cannot agree whether it is finished Clear goals
- Two members speak for 80% of every meeting Ground rules
- The Measure phase has run for four months Timelines
- Decisions are reversed between meetings Ground rules (silence is not consent)