Study guide

3.2 Benchmarking Types and Performance Goal Setting

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.2 Benchmarking Types and Performance Goal Setting

Key Takeaways Explain This Topic AI

ASQ names four benchmarking types: best practices, competitive, collaborative, and breakthrough.

Competitive benchmarking compares against direct rivals and yields relative position; collaborative benchmarking exchanges data with willing partners, often outside the industry.

Breakthrough benchmarking looks outside the industry for a radically different process model rather than an incremental performance gap.

A benchmark converts into a project only after it is normalized to comparable units and paired with a measured internal baseline.

The classic benchmarking cycle is plan, collect, analyze the gap, set goals, adapt and implement, then re-measure.

Last updated: August 2026

  • What benchmarking is for
  • Benchmarking is the structured comparison of your process performance and practices against a

reference, in order to set a defensible performance goal and to learn how the reference achieves it.

  • The second half matters more than the first. A gap number tells you that a 4-day cycle time is
  • possible; only the practice study tells you that it is achieved by removing a batch approval step you

still run.

ASQ tests this topic at the Apply level: given a situation, choose the benchmarking type and

translate the result into measures and goals.

The four types named in the Body of Knowledge

Type Comparison target What it produces Typical limitation

Best practices Recognized leaders in a specific practice, wherever they are A documented method known to work Practice may not transfer to your constraints

Competitive Direct competitors in the same market Relative market position on cost, quality, delivery Data is hard to obtain and often estimated

Collaborative Willing partners exchanging data, often through a consortium or industry group Verified, normalized, comparable metrics Restricted to what partners agree to share

Breakthrough Radically different process models, usually outside your industry Step-change redesign ideas High adaptation cost; often needs DFSS rather than DMAIC

  • Some organizations also use internal benchmarking -- comparison between plants, shifts, or
  • business units of the same company. It is the cheapest and fastest source of comparable data because
  • definitions and systems already match, and it is often the right first step before paying for

external studies. Its ceiling is that it can only reveal the best you already do somewhere.

Choosing a type

Need to know whether you are losing orders on price or lead time? Competitive.

Need a proven method for a specific practice such as changeover reduction? Best practices.

Need trustworthy, normalized numbers across a peer group? Collaborative.

Current process architecture is at its limit and incremental gains are exhausted? Breakthrough.

  • The classic breakthrough example is the pit-stop study: hospitals redesigned intensive-care handovers
  • by studying motorsport pit crews, not other hospitals. Nothing about a competitive benchmark would

have produced that design.

The benchmarking execution cycle

Plan. Identify the process to benchmark, the specific metrics, and the operational definitions.

Decide the type and the partners.

Collect. Gather internal baseline data first. Then gather partner data through published

sources, consortium reports, site visits, or structured interviews.

Analyze the gap. Normalize both sides to comparable units and quantify the difference. Then

investigate the practice difference that explains it.

Set goals. Convert the gap into a target with a date, and decide how much of the gap this

project will close.

Adapt and implement. Adapt rather than copy: the partner's constraints are not yours.

Re-measure. Benchmarks age. A target set against a competitor's 2023 performance is a target

against a moving reference.

  • Normalization: where benchmarking studies fail
  • Raw comparisons mislead unless both sides are expressed in the same denominators. The three

normalizations that matter most:

Scope : does the partner's "order cycle time" start at order receipt or at credit approval?

Volume and mix : cost per unit at 10,000 units/month is not comparable to cost per unit at

400 units/month, and a high-mix line cannot be compared with a single-product line.

Accounting basis : fully loaded labour rate versus direct rate can change a cost benchmark by

more than the gap you are trying to close.

Write the operational definition for every benchmarked metric before you collect anything. If the

definition cannot be matched, the metric cannot be benchmarked.

Turning a benchmark into project measures and goals

A benchmark becomes usable only through an explicit chain: Gap = Internal baseline − Benchmark reference \text{Gap} = \text{Internal baseline} - \text{Benchmark reference} Gap = Internal baseline − Benchmark reference

  • Then decide the closure fraction . Committing to close 100% of a gap against a best-in-class
  • reference in one project is usually a charter written to fail. A common convention is to target 50%

to 70% of the gap in the first project and to re-benchmark afterwards.

  • Worked example. A claims operation measures mean cycle time of 11.4 days. A collaborative benchmark
  • across eight insurers, normalized to the same start and stop events, gives a median of 6.2 days and a

first-quartile value of 4.1 days.

Gap to median: 11.4 − 6.2 = 5.2 11.4 - 6.2 = 5.2 11.4 − 6.2 = 5.2 days.

Gap to first quartile: 11.4 − 4.1 = 7.3 11.4 - 4.1 = 7.3 11.4 − 4.1 = 7.3 days.

Charter goal at 60% of the median gap: 11.4 − ( 0.60 × 5.2 ) = 8.3 11.4 - (0.60 \times 5.2) = 8.3 11.4 − ( 0.60 × 5.2 ) = 8.3 days.

  • The practice study then explains the gap: benchmark partners auto-adjudicate low-value claims below a
  • threshold, while this operation routes everything to a human adjuster. That practice, not the number,

is what the Improve phase acts on.

  • Ethics and legal limits
  • Competitive benchmarking must not become information exchange that restrains trade. Do not share or
  • solicit current or future pricing, costs that reveal pricing, capacity plans, or customer allocation
  • with a competitor. Most consortia route data through a neutral third party that returns only
  • aggregated, anonymized results for exactly this reason. Where a benchmarking code of conduct exists,

follow it: confidentiality, reciprocity, and use of data only for the stated purpose.