Study guide

Gap Analysis

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

Gap Analysis

Key Takeaways Explain This Topic AI

Gap analysis compares current performance to a predefined future-state target using agreed metrics so the team can size the problem and prioritize Analyze work.

A performance gap is Target − Current (or Current − Target when lower is better); always state the unit, time window, and data source with the number.

Build gap analysis from a clear Y metric, a validated baseline, a documented future-state goal, and stratification so you know where the gap is largest.

Gap analysis identifies and quantifies what must close; it does not by itself prove root causes—use root-cause tools next.

CSSGB Analyze items often test whether you can read a gap scenario, choose the right metric comparison, and avoid treating the gap statement as a solution.

Last updated: July 2026

Gap Analysis

Quick Answer: Gap analysis compares current-state performance to a predefined future-state (or customer/specification) target using agreed metrics . The gap is the numeric difference the DMAIC project must close—not a solution list and not a root cause by itself.

Why Gap Analysis Belongs in Analyze

By Analyze, Measure has usually given you a baseline Y and a sense of variation. Gap analysis turns that baseline into a decision-grade delta : How far are we from the goal? Where is the shortfall worst? How large must Improve be to matter?

ASQ’s CSSGB BoK places gap analysis at IV.C.1 (Analyze) : you analyze scenarios to identify performance gaps—not merely write a charter slogan. Use data, clear metrics, and current-vs-future comparison, then interpret what the gap implies for prioritization.

Current State vs Future State

  • Element Meaning Green Belt practice
  • Current state How the process performs now Validated Measure baseline (mean, median, rate, cycle time, etc.)
  • Future state The predefined project target Spec limit, VOC CTQ, management goal, or charter primary metric
  • Gap Difference that must close Target − Current (higher is better); Current − Target (lower is better)
  • Metric Unit and definition of Y Same definition, window, and inclusion rules on both sides

Higher is better: First-pass yield baseline 92% ; goal 98% . Gap = 6 percentage points .

Lower is better: Mean quote cycle time 4.8 days ; goal 2.0 days . Gap = 2.8 days .

Never mix definitions: “orders with no rework” vs “orders with no customer complaint” are different Y’s. A gap on mismatched definitions is fiction.

Predefined Metrics—Not Gut Feel

Fix metrics before storytelling:

Primary Y from the charter (plus consequential metrics if needed).

Operational definition — what counts as a defect, cycle, or complete order.

Time window and stratification — e.g., last 90 days by plant, product, shift, channel.

Baseline method — mean, median, proportion, DPMO, or capability—consistent with Measure.

Future-state source — customer CTQ, regulatory limit, management stretch, or benchmark documented with the sponsor.

If the target was never predefined, you are inventing a goal under pressure. Reset the goal with the sponsor, then measure the delta.

How to Run Gap Analysis

Confirm Y and goal from the charter after Measure still makes sense.

Refresh current state with the baseline or a stable updated window; note sample size and dates.

Compute the gap in the correct direction and unit.

Stratify by product, site, shift, failure mode, or segment. One overall number often hides a small high-gap stratum and a large low-gap stratum.

Translate into focused problem statements (“Plant B is 11 points below target; Plant A is 1 point below”).

Size opportunity when useful—annual units, CoPQ, or hours—so prioritization is business-real.

Hand off to root-cause tools. Fishbone, 5 Whys, fault trees, and data analysis explain why ; gap analysis only sizes the shortfall.

Worked Scenario — Claims Lead Time

Primary metric: median end-to-end lead time (submit → paid/denied), lower is better.

  • Slice Current median (days) Future-state target Gap (days) Volume share
  • Simple claims 3.1 2.0 1.1 55%
  • Complex claims 12.4 5.0 7.4 30%
  • Appeals 18.0 10.0 8.0 15%
  • Overall 7.2 4.0 3.2 100%

Interpretation: Overall gap is 3.2 days , but complex + appeals dominate the absolute shortfall. Chasing only high-volume simple claims may close little of the blended gap. Analyze should prioritize drivers of long complex and appeal paths while still watching simple-claim waste. When useful, convert the gap into annual claim-days or CoPQ so sponsors see why the stratified focus is not “ignoring” simple claims.

Exam Patterns and Pitfalls

Common patterns use the same skill— same metric, two states, quantified difference, stratified insight —whether the Y is capability vs. spec, on-time or AHT service levels, scrap/CoPQ, or DPMO/sigma goals.

Avoid:

Treating “we need new software” as a gap (that is a solution guess).

Moving the future-state target to erase bad news.

Aspirational targets with no sponsor ownership.

Omitting the direction of better when reporting the number.

Skipping stratification so one plant or SKU hides inside an enterprise blend.

Treating gap size as root cause—causes, tests, and controls still follow.

DMAIC fit: Define states the goal; Measure locks current state; Analyze quantifies and stratifies the gap then hands off to RCA; Improve must close a material share of the gap; Control watches whether it stays closed.

Expect items that compute Target vs. Current, choose the right comparison, size shortfalls with stratification, and refuse to confuse a gap statement with a root cause or Improve action. On scenario questions, first name the metric and direction of better, then compute or select the gap, then decide what to stratify next. Measure the distance to the goal first, then dig for why.