Study guide
1.5 Other Process Improvement & Quality Methods, and When to Choose Six Sigma
CSSC Certified Six Sigma Green Belt Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Six Sigma Overview & Exam Fundamentals
1.1 CSSC Certification Overview, Exam Structure & Body of Knowledge 1.2 History & Evolution of Six Sigma 1.3 Six Sigma Organizational Roles & Belts Hierarchy 1.4 The DMAIC Methodology Architecture vs. DMADV / DFSS 1.5 Other Process Improvement & Quality Methods, and When to Choose Six Sigma
2 Chapter 2: Quality Fundamentals & Defect Metrics
2.1 Critical to Quality (CTQ) Characteristics & VOC Translation 2.2 Defect Metrics: DPU, DPO, DPMO, & the 1.5-Sigma Shift 2.3 First Time Yield (FTY) & Rolled Throughput Yield (RTY) 2.4 Cost of Quality (COQ) & Cost of Poor Quality (COPQ)
3 Chapter 3: Lean Principles & Waste Elimination
3.1 Foundations of Lean & The Toyota Production System (TPS) 3.2 The Eight Wastes: CSSC's Seven Muda, TIMWOODS, and Muri/Mura 3.3 The 5S Visual Workplace Methodology 3.4 Value Stream Mapping (VSM), Cycle Time & Takt Time
4 Chapter 4: Project Selection & Team Management
4.1 Six Sigma Project Selection & Business Case Development 4.2 Project Charter Architecture 4.3 Stakeholder Management & Communication Planning 4.4 Team Dynamics & Tuckman's Team Development Stages 4.5 The 15-Point Project Viability Model & Process-Level Selection
5 Chapter 5: Define Phase & Process Mapping
5.1 High-Level Process Mapping with SIPOC 5.2 Flowcharts, Swimlane Diagrams & Process Value Analysis 5.3 Quality Function Deployment (QFD) & The House of Quality 5.4 Critical to Quality (CTQ) Flowdown & Operational Definitions 5.5 The CSSC Define Toolset: Ground Rules, In/Out of the Box, Is–Is Not & Tollgate Checklists
6 Chapter 6: Measure Phase & Measurement Systems
6.1 Data Types: Continuous (Variable) vs. Discrete (Attribute) Data 6.2 Data Collection Planning & Sampling Strategies 6.3 Measurement System Analysis (MSA) Foundations & Calibration 6.4 Variable & Attribute Gage R&R Studies
7 Chapter 7: Analyze Phase & Root Cause Analysis
7.1 Qualitative Root Cause Tools: 5 Whys & Cause-and-Effect (Fishbone) Diagrams 7.2 Failure Mode and Effects Analysis (FMEA) & RPN Calculation 7.3 Pareto Analysis & The 80/20 Rule 7.4 Graphical Data Exploration: Histograms, Box Plots, & Multi-Vari Charts 7.5 The Root Cause Verification Matrix
8 Chapter 8: Descriptive Statistics & Distributions
8.1 Measures of Central Tendency & Dispersion 8.2 The Normal Distribution & The Empirical Rule (68-95-99.7) 8.3 Standard Normal Distribution, Z-Scores & Probability Calculations 8.4 Common Non-Normal Distributions: Binomial, Poisson & Chi-Square
9 Chapter 9: Inferential Statistics & Hypothesis Testing
9.1 Fundamentals of Hypothesis Testing: Null vs. Alternative, Alpha & Beta Risks 9.2 One-Sample and Two-Sample t-Tests for Means 9.3 Paired t-Tests & Non-Parametric Alternatives 9.4 Analysis of Variance (One-Way & Two-Way ANOVA) & Chi-Square Contingency Tests 9.5 Sample Size Determination for Hypothesis Tests
10 Chapter 10: Correlation, Regression, & Experimentation
10.1 Linear Correlation & Pearson's Correlation Coefficient (r) 10.2 Simple Linear Regression & Coefficient of Determination (R^2) 10.3 Introduction to Design of Experiments (DOE) & Factorial Designs 10.4 Analyzing Experimental Results: Main Effects & Interaction Plots
11 Chapter 11: Improve Phase & Solution Implementation
11.1 Brainstorming, Creative Thinking & Solution Selection Matrices 11.2 Piloting Solutions & Conducting Risk Assessments 11.3 Implementation Planning & Change Management (ADKAR) 11.4 Mistake-Proofing (Poka-Yoke) & Standard Work
12 Chapter 12: Control Phase, SPC, & Process Capability
12.1 Statistical Process Control (SPC) & Shewhart Control Rules 12.2 Variable Control Charts: I-MR, X-bar & R, X-bar & S 12.3 Attribute Control Charts: p, np, c, and u Charts 12.4 Process Capability & Performance Indices: Cp, Cpk, Pp, Ppk 12.5 Communicating Statistical Results to Business Audiences
1.5 Other Process Improvement & Quality Methods, and When to Choose Six Sigma
Key Takeaways Explain This Topic AI
CSSC Green Belt Body of Knowledge Chapter 3 covers six named alternatives to Six Sigma: Lean Process Management, Total Quality Management, Business Process Reengineering, Rummler-Brache, Scrum, and the Customer Experience Management Method, plus JumpStart.
Business Process Reengineering seeks radical, enterprise-scale redesign of mostly technical processes, in direct contrast to the incremental improvement pursued by Six Sigma, Lean, and TQM.
The Rummler-Brache Nine Boxes Model crosses three performance levels (performer, process, organization) with three dimensions (management, design, goals).
JumpStart resolves a problem in a single multi-hour session with no statistical verification, so CSSC warns against using it alone for enterprise-wide, high-cost, or regulated processes.
CSSC gives four conditions that favor Six Sigma over the alternatives: facing the unknown, widespread and undefined problems, complex multi-variable problems, and costs closely tied to the process.
Last updated: September 2026
1.5 Other Process Improvement & Quality Methods, and When to Choose Six Sigma
Why this section exists: Chapter 3 of the CSSC Green Belt manual is pure comparative literacy, and it is the chapter self-study candidates most often skim. Under Path 2 it carries its own 10–15 question exam; under Path 1 its share of the 100 items is the same as any other chapter's. The material is also practical: the manual's stated reason for teaching it is that "you will need to communicate with leadership and business partners who are more familiar with other methods," and "the ability to frame Six Sigma concepts in a more global quality management approach can help you win support for your own projects."
Why a Green Belt Needs a Map of the Alternatives
Every successful business is trying to do the same thing — serve customers something they need while making as much profit as possible — so it is unsurprising that a century of methodologies converged on overlapping tools. Some of these methods, such as Lean and JumpStart, add value inside a Six Sigma approach. Others run alongside a Six Sigma project, driven by outside resources. And a few compete with Six Sigma for the same budget.
The exam tests three things about each method: what it optimizes for, whether it is incremental or radical, and where it sits relative to Six Sigma.
- The Six Named Programs
- 1. Lean Process Management
Lean began as a manufacturing waste-reduction concept but applies to any process that moves or creates goods or services — including virtual and digital workflows. Like Six Sigma, it is continuous rather than event-based, and it supplies waste-removal tools for daily control. Its signature continuous-improvement tool is Kaizen , Japanese for roughly "change for the better"; in a Kaizen environment every change must either eliminate waste or create more customer value.
Lean can be deployed inside a project or in daily production, and it is more a culture of quality than a single quality event. The CSSC manual is explicit that because Lean fits Six Sigma so well, it treats Lean as part of the Six Sigma methodology throughout the book — which is why "Lean Six Sigma" is the common branding.
2. Total Quality Management (TQM)
TQM was one of the first formal quality methods enacted in US business . Developed in the 1950s , it did not become popular with American companies until the 1980s . It became so fashionable that it turned into something of a workforce joke — much effort and expense spent on quality without an equal benefit. Jack Welch at GE held exactly that view before adopting Six Sigma.
Results depended heavily on implementation and organizational culture, and TQM variants remain in use today. Where it worked, organizations reported improved employee engagement and morale, reduced production costs, decreased cycle times, and more satisfied customers. Its central requirement is a strict quality commitment at all levels of the organization, especially among leaders . TQM's limitations are what pushed thinkers toward business process reengineering.
3. Business Process Reengineering (BPR)
BPR — also called business process redesign — is the one method on this list that is not incremental . Six Sigma, Lean, and TQM all pursue continuous change toward a model of perfection (zero waste for Lean, statistical 6σ for Six Sigma, a self-defined standard for TQM). BPR instead pursues radical change across an entire organization or process architecture .
BPR is most often concerned with technical processes : systems, software, data storage, cloud and web processes, and computer-based workflows. That technical density forces heavy reliance on inside resources (programming, integration, troubleshooting) and outside resources (BPR consultants, contract developers, software vendors). BPR initiatives are therefore costly , and organizations typically launch one only when they expect exponential gain or have concluded that current processes are obsolete or badly broken .
BPR has no defined principle set comparable to DMAIC, but projects generally run planning → design → implementation . Planning uses process mapping and process architecture to capture the enterprise current state. Design validates proposed solutions and begins building tools (technical teams often adopt Scrum at this point). Implementation carries a rigorous change-management and testing procedure: sandbox testing, quality-assurance testing, beta testing by experienced subject-matter experts in a limited live environment, a phased enterprise rollout with technical resources on call, and finally conversion to regular function.
4. Rummler-Brache
Pioneered in the 1980s by Geary Rummler and Alan Brache , this method blended Lean and Six Sigma elements. Its foundational component is the Nine Boxes Model , a 3 × 3 matrix crossing three performance levels with three dimensions :
Management Design Goals
Performer Feedback, consequences, and rewards Tools, training, and job documentation Performance metrics and requirements at an individual level
Process Who owns the process and how they might improve it Design of the process, work space, or system Requirements of the business and the customer
Organization Overall leadership culture and performance-evaluation requirements Org charts and process architecture Operating plans and top-level metrics
Rummler-Brache runs in six phases : improvement planning; definition; analysis and design; implementation; management of process; and processes turned over to daily teams.
5. Scrum
Scrum is a project development method specific to Agile programming work in technical departments , used to create new technical products or integrate new development on existing ones within a short window. Scrum projects commonly run two to four weeks — traditionally a very tight programming timeline. It arose because development teams needed to meet continuous demand from other departments without expanding headcount or hours.
Scrum has three phases :
The pregame — teams analyze available data and business requirements and translate business and process concepts into technical concepts to form the product or upgrade concept.
The game — development proceeds through sprints , smaller sequential development phases, each usually reviewed and validated before the next begins. Validating during development produces working product faster.
The postgame — quality assurance, testing, and change-management procedures prepare the product for release.
Scrum matters to a Green Belt because most modern improvement projects need a technical resource; while the Six Sigma team validates and measures, the technical department may be running Scrum simultaneously to deliver the improvement by deadline.
6. The Customer Experience Management Method (CEM)
Like Rummler-Brache, CEM was created by process-improvement consultants to serve organizations outside manufacturing . It combines process-improvement tools with customer relations management, was developed in the 1990s by the Virgin Group , and stayed popular through the 1990s and early 2000s.
CEM takes an outside-in approach: it starts from what the customer wants and asks how each process serves that need. Every process — even one with no direct customer contact — is defined in customer terms. Shipping is easy to frame that way (on time, accurate, affordably priced). In-house HR is harder, but employee morale and functionality directly affect how those employees serve customers. The diagnostic that follows is sharp: if an organization cannot link a process to the customer, it must ask whether the process is necessary or broken.
Like Six Sigma, CEM is data-heavy — customer feedback must be collected and analyzed. Its advantage is enterprise-wide customer-facing tactics producing large gains in satisfaction, loyalty, and spending. Its disadvantage is that traditionally inward-facing departments such as human resources, legal, and accounting struggle with customer-focused cultural change.
JumpStart: The Single-Session Method
JumpStart differs from everything above: it is a fast-paced method for identifying problems and solutions in a single session . It can be run inside almost any other method to spark discussion or surface candidate solutions, and it works as a management tool for teams that have no project resources at all.
How it runs. A leader identifies an area of concern or opportunity and assembles employees believed to have relevant insight. JumpStart usually does not work to define the problem — the group is close enough to already know what is wrong. Instead the group spends several hours brainstorming root causes and possible solutions. Six Sigma tools travel well into a JumpStart session: fishbone diagrams and solutions selection matrices can validate assumptions using only the knowledge in the room plus quick research.
Benefit: small-scale solutions get created and implemented quickly, often resolving the problem the same day, and the session surfaces issues that deserve a full project.
Limitation — and the exam's favorite angle: JumpStart performs no rigorous verification or statistical analysis . Changes are made on a wait-and-see basis. CSSC states that is safe for many inner-team changes but often dangerous for department- or enterprise-wide processes, and for processes tied to regulatory or compliance rules . Teams should not use JumpStart alone for sweeping changes or for processes that could seriously affect customer experience or the bottom line.
Method Selection at a Glance
- Method Optimizes For Change Style Relationship to Six Sigma
- Lean Waste elimination, customer value Incremental, continuous (Kaizen) Treated by CSSC as part of Six Sigma
- TQM Organization-wide quality commitment Incremental, culture-led Historical predecessor
- BPR Radical redesign of technical architecture Radical, one-shot Alternative when processes are obsolete
Rummler-Brache Aligning performer, process, and organization Incremental, six-phase Hybrid that borrowed from Lean and Six Sigma
- Scrum Fast technical product delivery Iterative sprints Complementary — often runs in parallel
- CEM Aligning every process to customer satisfaction Incremental, outside-in Alternative for non-manufacturing
- JumpStart Same-day problem resolution Single session Complementary — a tool inside other methods
- When to Choose Six Sigma
The manual gives four conditions. Expect at least one scenario item that describes a situation and asks which method fits.
When facing the unknown. Six Sigma is designed so a project can begin even when the cause of the problem is unknown — sometimes the team is not even sure what the exact problem is, only that some metric is not performing. An organization suffering a profit drop that has not corrected itself over several consecutive quarters can start a Six Sigma project to seek causes, prioritize them, and work toward solutions.
When problems are widespread and not defined. A wide, poorly bounded problem causes loosely managed projects to escalate in scope until they become unmanageable, and no problem is ever completely solved. Six Sigma includes controls for avoiding scope creep so teams make incremental improvements that steadily improve a process over time.
When solving complex problems. With many variables it is hard to know how to approach a solution, let alone define and measure success. Statistical analysis and process control let teams handle enormous data volumes and many variables, distilling complex ideas into specific hypotheses, premises, and conclusions through analysis and graphical representation.
When costs are closely tied to processes. Because statistical process control produces more accurate assumptions than almost any other method, Six Sigma suits situations tightly linked to revenue or cost. When one tiny change can mean millions of dollars, assumptions must be validated with an extremely small margin of error — something guesswork, basic research, and even years of experience cannot deliver.
Realistic Exam Scenario
A regional insurer's claims platform is fifteen years old, runs on an unsupported database, and cannot be extended without breaking downstream integrations. Leadership wants the whole claims architecture replaced within eighteen months.
A Green Belt asked to "run a Six Sigma project on it" should recognize the mismatch. The process is not being improved — it is being replaced wholesale , the work is overwhelmingly technical, and the organization has already judged the current process obsolete. That is textbook BPR territory, and the development work inside it will likely run on Scrum . Six Sigma still has a role: measuring the current baseline so the new architecture's benefit can be proven, and applying DMADV rather than DMAIC if a designed solution is needed. Recommending DMAIC here would be the wrong answer.
Common Exam Traps
Trap 1: Calling BPR incremental. Every other method on the list pursues continuous improvement. BPR is the radical outlier. If a stem contains "radical," "enterprise-wide redesign," or "obsolete processes," the answer is BPR.
Trap 2: Attributing CEM to manufacturing. CEM was created for organizations outside manufacturing and was developed by the Virgin Group in the 1990s.
Trap 3: Treating JumpStart as a lightweight DMAIC. JumpStart does no statistical verification and does not define the problem. It is unsuitable alone for regulated or enterprise-scale change.
Trap 4: Dating TQM to the 1980s. TQM was developed in the 1950s ; the 1980s is when it became popular in the United States.
Trap 5: Reversing the Nine Boxes axes. Levels are performer, process, organization. Dimensions are management, design, goals.