Study guide

Organizational Drivers, KPIs & Scorecards

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

Organizational Drivers, KPIs & Scorecards

Key Takeaways Explain This Topic AI

Core organizational drivers include profit, market share, customer satisfaction, efficiency, and competitive differentiation—Six Sigma projects should move at least one deliberately.

KPIs are quantifiable process or outcome measures used to manage performance; each needs an operational definition, owner, and review cadence.

Scorecards (including balanced scorecards) organize metrics across perspectives so leaders do not optimize finance alone.

Metrics cascade from strategy to process to project so Green Belt Y’s and consequential measures stay visible on operational reviews.

Good metric systems avoid vanity counts, conflicting incentives, and lagging-only views; mix leading and lagging indicators.

Last updated: July 2026

Organizational Drivers, KPIs & Scorecards

Quick Answer: Organizational drivers—profit, market share, customer satisfaction, efficiency, and differentiation—explain why leaders fund improvement. KPIs quantify those drivers at process and outcome levels; scorecards organize KPIs so strategy cascades into daily management. Green Belts should map project metrics onto that cascade so DMAIC results are visible and sustained.

Organizational Drivers Green Belts Must Recognize

A driver is a high-level force that shapes strategy and resource allocation. CSSGB I.A.3 expects familiarity with common drivers and how projects support them.

Driver What it means Example process metrics a project might move

Profit / financial return Revenue growth, margin, cost reduction, CoPQ Cost per claim, scrap $, warranty cost, overtime

Market share Relative volume or revenue in a defined market Win rate, on-time launch, defect escapes that trigger churn

Customer satisfaction (CSAT) Perceived value, loyalty, complaint experience NPS/CSAT scores, complaint rate, first-contact resolution, OTIF

Efficiency / productivity Output per input; speed and resource use Cycle time, throughput, labor hours per unit, first-pass yield

Differentiation Unique quality, service, innovation, or brand promise Capability indices on CTQs, premium feature reliability, service SLAs

These drivers interact. A project that cuts cost (profit/efficiency) by slowing response time may damage CSAT and share. That is why consequential metrics and multi-perspective scorecards matter.

Worked example — regional bank: Leadership’s annual drivers include (1) improve non-interest expense ratio and (2) raise retail CSAT. A Green Belt project on mortgage application rework supports both if it reduces rework labor (efficiency/profit) and shortens applicant wait time (CSAT). Framing the charter against both drivers increases Champion support.

KPIs: Making Drivers Measurable

A key performance indicator (KPI) is a quantifiable measure used to evaluate success against an objective. Not every number is a KPI—vanity metrics (raw page views, total meetings held) rarely drive decisions. Strong KPIs share these traits:

Linked to a driver or strategy theme — You can explain “so what?” in one sentence.

Operational definition — Numerator, denominator, inclusion/exclusion rules, data source, and unit.

Owner and cadence — Someone reviews it on a known schedule and can act.

Actionable — Movement implies a process response, not just a report.

Balanced with related measures — Prevents gaming a single number.

Leading vs. lagging indicators

  • Type Definition Example
  • Lagging Outcome after the fact Monthly profit, quarterly CSAT, annual market share

Leading Predictive or in-process signal First-pass yield this week, quote cycle time, training completion, control-chart alarms

Green Belt projects often improve leading process indicators that eventually move lagging enterprise results. In Control, leading indicators (SPC on a CTQ, audit compliance %) keep the lagging KPI from sliding backward.

  • Common KPI families in Six Sigma environments
  • Quality: DPMO, FPY, scrap rate, complaint ppm, capability (Pp/Ppk)
  • Speed: Lead time, cycle time, queue time, on-time delivery %
  • Cost: CoPQ, cost per transaction, inventory turns, overtime hours
  • Customer: CSAT/NPS, retention, service-level attainment
  • Safety/compliance: Incident rate, audit findings, CAPA closure time

Choose the fewest KPIs that still protect the system. A project dashboard with fifteen similar charts dilutes attention; three to five well-defined metrics usually suffice for a Green Belt scope.

Scorecards and How Metrics Cascade

A scorecard is a structured set of measures used to manage performance. The classic balanced scorecard (Kaplan & Norton) groups metrics into perspectives such as financial, customer, internal process, and learning/growth so leaders do not manage by income statement alone. Many organizations use simplified ops scorecards or strategy maps with the same idea: multiple perspectives, cascaded targets, color-coded status.

  • Cascade model Strategy / drivers
  • → Enterprise scorecard KPIs
  • → Business unit / plant scorecards
  • → Process owner KPIs
  • → Project primary & consequential metrics
  • → Control plan checks & SPC

Rules of a healthy cascade:

Traceability — Each lower metric maps to a higher objective (even if not 1:1).

Consistency of definitions — “On-time” means the same thing on the plant board and in the project charter.

Increasing operational detail downward — Enterprise sees margin; process sees changeover minutes and defect codes.

Ownership at each level — Belts improve processes; process owners sustain KPIs; executives set direction.

Review rhythm — Daily/weekly process huddles; monthly ops reviews; quarterly strategy checks.

Worked example — cascade for order accuracy:

  • Level Metric Target
  • Enterprise driver Customer loyalty / CSAT Top-quartile CSAT
  • Enterprise KPI Perfect order rate ≥ 96%
  • DC scorecard Lines shipped without error ≥ 99.2%
  • Process KPI Pick accuracy ≥ 99.5%
  • Green Belt project Y Mis-picks per 1,000 lines (Zone B) From 12 to ≤4 in 16 weeks
  • Control plan Zone B audit sample + scanner compliance Daily checks; react if 2 consecutive days above limit

When the project succeeds, the process KPI and eventually the perfect-order enterprise metric should move. If they do not, either the project Y was poorly linked, the operational definition differed, or other processes offset the gain—valuable learning for Analyze and for portfolio management.

Using Drivers and Scorecards in DMAIC

  • DMAIC phase Metric discipline
  • Define Name the driver, scorecard KPI, primary Y, and consequential metrics in the charter
  • Measure Baseline Y with MSA; confirm data matches scorecard definitions
  • Analyze Stratify defects against KPI categories leadership already uses
  • Improve Predict impact on scorecard KPIs; pilot with both primary and consequential metrics
  • Control Hand metrics to the process owner’s scorecard; set response plans for KPI breaches

Financial translation: Many deployments require a benefits worksheet (hard savings, soft savings, cost avoidance). Profit as a driver becomes concrete when finance agrees on the CoPQ formula—for example, rework hours × fully burdened rate + scrap material + expedited freight. Green Belts should not invent finance rules; they should use the organization’s accepted benefit methodology so scorecard claims survive audit.

  • Pitfalls That Break Metric Systems
  • Metric proliferation — Too many red/yellow/green boxes; nothing is “key.”

Conflicting incentives — Purchasing rewarded only for unit price while quality is measured separately with no shared total cost metric.

Lagging-only scorecards — Leaders see last quarter’s damage too late to act.

Gaming — Teams redefine “defect” or cherry-pick samples to paint green.

Orphan project metrics — Project Y never appears on any ongoing scorecard, so Control dies after celebration.

Ignoring differentiation — Pure cost projects that erode the brand attributes customers pay for.

Green Belt Checklist for Drivers, KPIs, and Scorecards

Can I name the organizational driver(s) this project supports?

Is my primary metric already on (or clearly feeding) a process or BU scorecard?

Do I have operational definitions aligned with how the scorecard is calculated?

Have I set consequential KPIs for customer, safety, cost, or speed trade-offs?

Will the process owner continue reviewing these metrics after project closure?

Do leading indicators exist so we detect slippage before lagging KPIs tank?

If you can answer yes across that list, your Six Sigma work is wired into how the organization actually steers—not just into a belt certification binder.