Study guide

Primary & Consequential Metrics

ASQ Certified Six Sigma Green Belt CSSGB

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

CSSGB Exam Facts & Logistics How to Study for an Open-Book ASQ Exam

2 Six Sigma Foundations

Value of Six Sigma & Quality Leaders Organizational Goals & Six Sigma Projects Organizational Drivers, KPIs & Scorecards

3 Lean Principles in the Organization

Lean Concepts Value Stream Mapping & Waste

4 Design for Six Sigma

DFSS Road Maps: DMADV & IDOV FMEA Basics & Risk Priority Number Design FMEA vs Process FMEA

5 Define: Project Identification

Project Selection & DMAIC Fit Process Elements & Boundaries Benchmarking Types SIPOC & Process Inputs/Outputs

6 Stakeholders & Voice of the Customer

Owners & Stakeholders Customer Identification Customer Data Collection CTQ, QFD & Kano

7 Project Management Core

Agile & Top-Down Project Methods Project Charter & Problem Statements Project Scope Tools Primary & Consequential Metrics

8 Planning, Risk & Closure

WBS, Gantt, CPM, PERT & Tollgates Project Documentation Project Risk Analysis & Management Project Closure & Lessons Learned

9 Management Tools & Business Results

Eight Management & Planning Tools DPU, RTY, CoPQ, DPMO & Sigma Level Organizational Communication

10 Team Dynamics & Performance

Team Stages & Negative Dynamics Six Sigma Roles & RACI Brainstorming, NGT & Multivoting Team Communication

11 Measure: Process & Probability

Process Maps & Documentation Basic Probability Concepts Central Limit Theorem

12 Distributions & Data Collection

Statistical Distributions Data Types & Measurement Scales Sampling & Data Collection Plans Descriptive Statistics

13 Graphical Methods & MSA

Graphical Methods Measurement System Analysis & Gage R&R Bias, Linearity, Stability & P/T

14 Process & Performance Capability

Process Performance vs Specifications Process Capability Studies Cp, Cpk, Pp, Ppk & Cpm Short-Term vs Long-Term Capability & Sigma Shift

15 Analyze: Exploratory Data Analysis

Multi-Vari Studies Correlation & Linear Regression

16 Hypothesis Testing

Hypothesis Testing Basics Tests for Means, Variances & Proportions

17 Gap & Root Cause Analysis

Gap Analysis Root Cause Analysis Tools

18 Design of Experiments

DoE Basic Terms Main Effects & Interaction Plots

19 Implementation Planning & Lean Tools

Implementation Planning & Pilots Waste Elimination Tools Cycle-Time Reduction & SMED Kaizen & Kaizen Blitz

20 Statistical Process Control

SPC Basics: Common vs Special Cause Rational Subgrouping Control Chart Selection & Construction

21 Sustaining Improvements & Lean Control

Control Plans Document Control, Training & Audits Plan-Do-Check-Act (PDCA) TPM & Visual Factory

Primary & Consequential Metrics

Key Takeaways Explain This Topic AI

The primary metric is the project Y—the measurable outcome the charter commits to improve, stated with baseline, target, and time frame.

Consequential (secondary/guardrail) metrics monitor unintended effects so gains on Y do not create new harm in cost, time, safety, quality, or customer experience.

Each consequential metric needs an operational definition, baseline, guardrail limit, review cadence, and response plan if breached.

Intentional trade-offs are acceptable only when documented and Champion-approved; silent degradation of guardrails is project failure.

Control plans must track both primary and consequential metrics; improving Y while breaking guardrails is not success.

Last updated: July 2026

Primary & Consequential Metrics

Quick Answer: A primary metric is the project Y you commit to improve (for example, reduce defects from 4.2% to ≤1.5%). Consequential metrics (also called secondary or guardrail metrics) monitor unintended effects so gains on Y do not create new harm—such as higher cost, longer cycle time, worse safety, or lower customer satisfaction.

Why Two Metric Classes Matter (BoK II.C.4)

ASQ’s CSSGB BoK requires Green Belts to apply primary and consequential metrics when managing projects. Optimization without guardrails is how teams “win” a local KPI while the system loses: scrap falls because inspectors wave product through; cycle time drops because incomplete work ships; cost falls because preventive maintenance is deferred.

Define-phase metric design answers:

  • What single outcome defines project success? → Primary metric
  • What must not degrade while we chase that outcome? → Consequential metrics
  • How will we operationally define, baseline, and track both? → Measurement plan hooks for Measure/Control
  • Primary Metrics (Project Y)

The primary metric is the performance measure named in the problem and goal statements. It should be:

  • Linked to CTQ / business case — Customer or enterprise care
  • Measurable — Operational definition, data source, frequency
  • Sensitive to the process in scope — The team can actually move it
  • Time-framed — Baseline window and goal date
  • Singular enough to prioritize — One primary Y (or a clearly ranked primary)
  • Common primary metric families
  • Family Examples Notes
  • Quality / defect FPY, DPMO, % defective, complaint rate Define defect clearly
  • Time Cycle time, lead time, OTIF, queue time Start/stop events matter
  • Cost Cost per unit, CoPQ, rework $, expedite $ Separate cost of poor quality from accounting noise
  • Safety Incident rate, near misses Often primary for EHS projects; else consequential
  • Service / VOC CSAT, NPS detractors, FCR Pair with operational process metrics when possible
  • Productivity Units per hour, utilization Watch for local efficiency vs. system flow
  • Example primary statements
  • “Reduce Line 2 defect rate from 3.8% to ≤1.0% by 15 October 2026.”
  • “Cut median claims cycle time from 14 days to ≤9 days within six months.”
  • “Improve first-contact resolution from 61% to ≥80% for Plan Renewal tickets.”

Notice the form: reduce/increase [metric] from [baseline] to [target] by [date] . That is the language of a primary metric commitment.

  • Primary metric pitfalls
  • Choosing a metric the team cannot influence (enterprise EBITDA as a Green Belt Y)
  • Using a lagging annual metric with no process leading indicator
  • Changing the operational definition mid-project to manufacture success
  • Tracking activity metrics as primary (“number of kaizens held”) instead of outcomes
  • Consequential Metrics (Guardrails)

Consequential metrics detect unintended consequences of improving the primary Y. They are not “nice to have dashboards.” They are constraints : the project is not successful if primary improves while consequential metrics breach agreed limits.

Typical consequential pairs

  • If primary is… Watch consequential… Why
  • Defect rate ↓ Unit cost, cycle time, throughput Extra inspection can hide true quality
  • Cycle time ↓ Completeness, accuracy, rework, safety Speed without quality ships defects
  • Cost ↓ Defects, OTIF, employee overtime, safety Starving process capability
  • Throughput ↑ WIP quality, scrap, changeover defects Push systems overload constraints
  • Customer satisfaction ↑ Cost-to-serve, handle time fairness Buying scores with unsustainable giveaways
  • Automation rate ↑ First-pass yield, exception backlog Bots create new failure modes

Example: Primary = reduce average handle time (AHT) from 8.5 to 6.5 minutes. Consequential = first-contact resolution ≥ baseline 72%, CSAT ≥ baseline 4.2/5, escalation rate ≤ baseline 11%. Without those guardrails, agents may rush callers and create callbacks—AHT “wins,” customer loses.

Setting consequential metric rules

For each consequential metric define:

  • Operational definition (same rigor as primary)
  • Baseline before Improve
  • Guardrail — e.g., “shall not worsen more than X%” or “remain ≥ baseline”
  • Review cadence — weekly during pilot; ongoing in Control
  • Response plan — what the team does if a guardrail trips

Some organizations call these secondary metrics . On the exam, focus on the idea: primary = intended improvement; consequential = unintended-effect monitor.

Balancing Trade-offs Explicitly

Not every trade-off is forbidden. Sometimes leadership accepts a temporary cost increase to cut defects. That is fine if stated in the charter :

Primary: FPY 88% → 96%

Consequential / negotiated: packaging material cost may rise up to +3% during pilot; beyond that requires Champion approval

Hard stop: recordable safety incidents must not increase at all

Documented trade-offs prevent arguments after the pilot when finance notices a cost bump the team silently chose.

Metrics Across DMAIC

  • Phase Primary metric use Consequential metric use
  • Define Name Y, baseline, goal; list guardrails Agree what “no harm” means
  • Measure Validate measurement system; refine baseline Baseline guardrails; ensure data exist
  • Analyze Relate Xs to Y Check that apparent Xs do not only move Y by harming guardrails
  • Improve Pilot shows Y movement Confirm guardrails hold under the new process
  • Control Control plan monitors Y Control plan also monitors consequential metrics

A Control plan that tracks only the primary metric is incomplete.

Worked Example — Order Defect Project

Primary: Reduce wrong-item shipped rate from 2.4% to ≤0.5% in 5 months for DC East e-commerce.

Consequential 1: Lines picked per hour ≥ 95% of baseline (avoid killing productivity with endless double-checks).

Consequential 2: On-time ship ≥ baseline 97% (quality fixes must not create late waves).

Consequential 3: Overtime hours ≤ baseline +5% during pilot only.

Improve implements barcode validation at pack. Pilot: wrong-item rate falls to 0.4%; pick rate dips 2% (within guardrail); OTIF holds; overtime +3%. Project proceeds. If wrong-item rate fell only because packers slowed to half speed, consequential metrics would have blocked a false “success.”

  • Common Metric Design Errors
  • Many primaries, no primary — Team cannot prioritize
  • No consequential metrics — Local optimization risk
  • Vanity metrics — Looks good in slides, unrelated to CTQ
  • Unbaselined guardrails — Cannot detect worsening
  • Conflicting incentives — Process owner bonus fights project Y
  • Wrong aggregation — Plant average hides the line you scoped
  • Gaming — Redefining defects midstream to hit the number
  • Green Belt Checklist
  • One clear primary Y with baseline, target, date, and operational definition
  • 2–4 consequential metrics with baselines and guardrail rules
  • Trade-offs negotiated and written when intentional
  • Data sources available for both classes before Measure deep-dives
  • Control plan includes both primary and consequential signals
  • Success definition: primary goal met and guardrails held (or approved exceptions)

When you can write “reduce defects by X” and name what must not get worse, you meet BoK II.C.4 at the Apply level—and you protect customers and the business from hollow wins.