Study guide
3.1 Impact of Six Sigma Projects on Customers, Suppliers, and Stakeholders
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
3.1 Impact of Six Sigma Projects on Customers, Suppliers, and Stakeholders
Key Takeaways Explain This Topic AI
A process change propagates to customers, suppliers, internal downstream processes, support functions, and regulators.
Tightening an internal tolerance without notifying the supplier converts your improvement into their non-conformance.
Customers can be harmed by improvements that change lead time predictability, packaging, documentation, or minimum order quantity.
A stakeholder impact table in the charter forces the team to state the expected effect and the risk for each affected party.
In regulated environments a process change triggers change control and possible customer or regulatory notification, and that lead time belongs in the project plan from Define.
Last updated: August 2026
- Impact propagates in every direction
- A Six Sigma project changes a process, and processes sit inside a network. The Body of Knowledge asks
- Black Belts to describe that propagation at the Understand level, but the practical requirement is
harder: predict it before it happens and design for it.
Stakeholder Typical positive impact Typical negative impact if unmanaged
External customers Fewer defects, shorter and more predictable lead time, lower cost Changed packaging or documentation; changed minimum order quantity; a transition period with mixed old and new product
Suppliers Clearer requirements, more stable demand signal, longer-term relationship Tightened tolerances imposed without notice; smaller more frequent orders; new inspection or certification burden
Internal downstream processes Better inputs, less rework, less firefighting New handling requirements; different arrival pattern; retraining they did not request
Internal upstream processes Clearer specification of what is needed New data collection duties; changed schedule
Support functions Fewer escalations and corrective actions New maintenance intervals, new calibrations, new system changes, new reports
Operators in scope Less rework, less frustration, safer work Changed standard work; loss of familiar workarounds; perceived job risk
Regulators and certification bodies Better documented, more capable processes An unnotified change to a validated process
Suppliers are inside the system
The most common and most damaging propagation failure is treating a supplier as external to the project.
A team tightens an incoming dimensional tolerance from ± 0.15 \pm 0.15 ± 0.15 mm to ± 0.08 \pm 0.08 ± 0.08 mm to raise downstream
- assembly yield. Internally the project succeeds. At the supplier, a process with a Cpk of 1.4 against the
- old tolerance now has a Cpk of 0.75, so their scrap rate rises from near zero to several percent. Within
- two months the cost arrives back as a price increase, a delivery shortfall, or an incoming quality
problem, and the net effect on the enterprise is negative.
The rule: any change to a requirement that a supplier must meet is a supplier project as well as
yours. Practically that means:
Share the capability data and the reason for the change, not just the new number.
Confirm the supplier's capability against the proposed requirement before committing to it.
Consider whether the assembly can be made robust to the existing tolerance instead -- parameter design
is often cheaper than buying tighter components.
Agree the transition: effective date, existing stock disposition, first-article requirements.
- The same logic runs the other way for demand: a project that reduces batch size improves your flow and
- converts the supplier's steady monthly order into weekly orders, which may raise their setup cost. That
is a legitimate change but it must be negotiated, not imposed.
Customers can be harmed by improvements
Improvements that look unambiguously good internally can still create customer impact:
Change Unintended customer impact
Shorter lead time Customer planning systems and safety stock were tuned to the old lead time; a change in variability matters more than a change in mean
- Reduced packaging material Handling or storage at the customer changes; their automation may not accept it
- Consolidated shipments Fewer deliveries per week disrupts a customer running to a daily schedule
- Changed component supplier Requires customer requalification in regulated or safety-critical applications
- Revised documentation format Customer receiving systems and their audit records must be updated
- The test is simple and often skipped: would the customer notice this change, and would they need to do
anything about it? If yes, they must be told before it happens, not discovered afterwards.
The stakeholder impact table
Build it in Define, alongside the SIPOC, and revisit it at every toll gate.
Stakeholder Internal / external Current experience Expected impact Risk Mitigation Owner
Assembly cell 2 Internal Receives 4% of kits short Complete kits; new pick sequence Operators must learn a new layout Standard work plus 2-week hypercare Cell supervisor
Moulding supplier External Ships to ± 0.15 \pm 0.15 ± 0.15 mm Requirement tightens to ± 0.10 \pm 0.10 ± 0.10 mm Their Cpk falls below 1.0 Joint capability study before commitment Supply quality engineer
Fleet customers External 6-day lead time 3-day lead time Batch reduction may raise unit price Model total cost with the customer Account manager
Field service Internal Handles miswired-unit rework Far fewer callouts Loses visibility of failure modes Share the new defect data monthly Service manager
Notified body External Process validated in 2024 Process parameter change Requires change control and possible notification Regulatory review in Analyze Regulatory affairs
- The rows that carry a risk entry are the ones worth reviewing with the sponsor. The row types most
- often missing are the internal downstream process that absorbs the change without being asked, and the
support function that inherits a new recurring obligation.
- Regulated environments
- Where the process is validated -- medical devices, pharmaceuticals, aerospace, food, automotive safety --
- a process change is not merely an engineering decision. It triggers formal change control , may
- require revalidation , and in some cases requires customer or regulatory notification before
implementation. Those steps have lead times measured in weeks or months.
The failure mode is discovering this in the Improve phase, when the solution is designed and the sponsor
expects implementation. Regulatory and change-control lead times belong in the project plan from Define , and the regulatory function belongs on the stakeholder list from the first charter review.
Measuring the impact
Where impact is expected, measure it rather than assuming. Two mechanisms:
Consequential metrics in the project's measure set, so degradation elsewhere is visible while the
primary metric improves.
- A short post-implementation check with each affected stakeholder , at 30 and 90 days, asking
- specifically what changed for them. Suppliers and internal downstream processes rarely volunteer that a
change hurt them; they absorb it and the cost surfaces later as something else.