Book summary · Quality and Six Sigma · Intermediate
The Six Sigma Way: summary and review
How GE, Motorola, and Other Top Companies Are Honing Their Performance
By Peter S. Pande, Robert P. Neuman and Roland R. Cavanagh. First published 2000.
The short answer
The Six Sigma Way is a deployment guide for executives and program leaders, written in 2000 when GE and Motorola were the reference cases. Its argument is that Six Sigma works as a management system built on customer-defined quality, fact-based decisions, process ownership and a project structure with trained roles, not as a statistics course. It gives a five-step roadmap for rolling that system out and says little about analysis tools. Read it to design or audit a program. Skip it to learn capability studies or hypothesis tests.
Read it if
- You run a plant or quality function and corporate has handed you a Six Sigma mandate, or an existing program has stalled.
- You need to explain to executives how projects, trained roles, metrics and reviews fit together, with examples beyond manufacturing.
Skip it if
- You want to learn how to run a capability study, gauge study or hypothesis test. This is not a tool manual.
- Your problem is lead time, WIP or changeover. A flow or lean book will serve you better.
When it pays off: Before you charter a first wave of projects, or when a program is running but projects are not tied to a customer complaint or a cost line. Read it with the stalled program in front of you.
The core ideas, in plain language
- 1
Six themes make one system
The book frames Six Sigma as six habits of a company: focus on the customer, decisions from data, work managed as processes, acting before problems arrive, collaboration across departments, and a drive for perfection that tolerates the failures experiments bring. The tools sit inside that frame.
- 2
A roadmap comes before projects
The authors' own sequence is to identify core processes and key customers, define what customers require, measure current performance, prioritize and analyze and carry out improvements, then spread and integrate the system. Projects come out of the first three steps instead of from whoever complains loudest.
- 3
Start where customer and profit meet
Summaries of the book say it begins with customer-facing processes that generate profit, and its examples include service work as well as plants. In a plant, that points you at order-to-ship and final quality before any internal sub-process nobody outside sees.
- 4
Leadership work comes first
The opening parts cover why Six Sigma stuck where Total Quality did not, then readiness, project selection and leadership training, before the improvement steps. Most deployments add Champions, Master Black Belts, Black Belts and Green Belts, so the book is as much about who owns a project as how to run it.
- 5
Payback is a multi-year claim
Summaries report the authors' view that long-term commitment and top management support pay back in profit over several years, not in the first months. Treat that as the authors' claim, not a benchmark for your site.
The book's roadmap, before and around projects
- 1
Identify core processes and key customers
- 2
Define what customers require
- 3
Measure current performance
- 4
Prioritize, analyze and improve
The projects. - 5
Spread and integrate the system
How to use it on Monday morning
Putting The Six Sigma Way to work, step by step
- 1
Draw one process on one page
Pick one process that touches a customer and a cost line, such as final inspection through shipping. Put an operator, an inspector and a planner in a room for an hour and write a SIPOC: suppliers, inputs, steps, outputs, customers. - 2
Write the customer requirement as a number
Pull the last 90 days of complaints, returns and nonconformance reports. Turn the top two causes into measurable requirements, for example a dimension and tolerance or a delivery window, so the project has something to be measured against. - 3
Check the gauge, then count
Run a gauge R&R before you trust a baseline: 10 parts, 2 or 3 appraisers, 2 or 3 trials, about half a day. Then tally defects on a check sheet for a week and post first-pass yield and defects per million from the counts. Leave a sigma level off the board. - 4
Charter one project
Write a one-page charter: problem, baseline, goal, scope, team and dates. Get a named sponsor to sign it by Friday. One chartered project with a sponsor tells you more about your readiness than a training plan.
What to be careful about
The evidence is company-reported
GE announced $350 million in Six Sigma savings in 1998, a figure that fed the book's era. Against that, a Fortune analysis found 91% of 58 large adopters trailing the S&P 500, but it came from Qualpro, which sells a competing method. Both sides of the evidence are interested.
The sigma label rests on a contested assumption
The 3.4 defects per million figure assumes a 1.5 sigma drift in the process mean. Statistician Donald Wheeler has called that shift arbitrary. If your team reports sigma levels, expect pushback from SPC people; report yield and control charts instead.
Narrow fit outside defect reduction
Joseph Juran judged Six Sigma a basic version of quality improvement with little new in it. BusinessWeek reported that it stifled creativity at 3M and was removed from the research function, and Fortune described it as built to fix an existing process. A defender, Michael Marx, says 3M's problem was cultural, not methodological.
Dry, and light on technique
Reader reviews on Goodreads call it dry and textbook-like, with little advanced technical detail. The tools live in a separate companion, The Six Sigma Way Team Fieldbook (McGraw-Hill, 2001).
The Six Sigma Way compared with Lean Six Sigma: Combining Six Sigma Quality with Lean Speed
Judging by its stated aim of combining Six Sigma quality with lean speed, George's book is the better pick if your plant hurts from lead time, WIP and changeovers as much as from defects. Choose Pande, Neuman and Cavanagh when the open question is how to set up, staff and govern a program.
What to read next
- Understanding VariationWheeler, the critic of the 1.5 sigma shift, teaches control charts, which is the grounding the sigma-level convention skips.
- The Six Sigma Handbook (Thomas Pyzdek)A tools reference for the analysis the Pande book leaves out.
- The GoalIf defects are under control and shipments still lag, the constraint view explains why.
Same topic (quality and six sigma): Out of the Crisis, Zero Quality Control, Understanding Variation, Lean Six Sigma.
Tools and templates on LeanSuite that go with it
- SIPOC diagramStep one of the roadmap: one page that shows the process and its customer.Open
- Defect check sheetGives the week-long baseline count that every later claim depends on.Open
- Gage R&R study sheetChecks that the measurement can support the baseline before projects start.Open
- Pareto chartRanks defect types so the first project goes after the biggest one.Open
- DMAIC project charterThe one-page charter and sponsor sign-off for a first project.Open
Book details
| Title | The Six Sigma Way: How GE, Motorola, and Other Top Companies Are Honing Their Performance |
|---|---|
| Author | Peter S. Pande, Robert P. Neuman and Roland R. Cavanagh |
| First published | 2000. First edition: McGraw-Hill, 27 April 2000 (ISBN 978-0-07-135806-4). The edition cited here is the 2014 second edition, retitled with the subtitle How to Maximize the Impact of Your Change and Improvement Efforts. |
| Edition shown | Second edition, print (publisher lists 17 December 2013), McGraw-Hill Education, 2014 |
| ISBN-13 | 978-0071497329 |
| Pages | 427 |
Details checked against public records on 7 October 2026. Other editions have other ISBNs. We carry no affiliate links.
FAQ
Questions about The Six Sigma Way
Yes for program design and governance, no for technique. It explains how customer requirements, projects and trained roles fit together, and the second edition adds 14 years of lessons. Its case evidence dates from the GE era, so weigh it as a playbook rather than proof.
The 2014 second edition, ISBN 9780071497329. It keeps the original argument and adds lessons from 14 years of use, myths, newer cases (Adobe, Macy's, Starwood) and decision maps. The 2000 first edition has a different subtitle and leans on GE and Motorola.
Not in depth. Reader reviews call it dry and light on advanced technical detail, and the tools sit in a separate companion fieldbook. Use it to decide what to improve and who owns it, then pick a handbook for the analysis.
It is a management book with manufacturing and service examples. Its advice to start with customer-facing, profit-generating processes works on a plant floor, but lead time and WIP get little attention.
More lean books
- The Machine That Changed the World
- Lean Thinking
- Lean Production Simplified
- Toyota Production System
- Workplace Management
- The Toyota Way
- Kaizen: The Key to Japan's Competitive Success
- Gemba Kaizen
- Managing to Learn
- Understanding A3 Thinking
- Toyota Kata
- Learning to See
- Making Materials Flow
- Creating Level Pull
- Value Stream Mapping
- Creating a Lean Culture
- The Lean Manager
- Gemba Walks
- Introduction to TPM
- Out of the Crisis
- Zero Quality Control
- Understanding Variation
- Lean Six Sigma
- The Goal
- Getting the Right Things Done
- Hoshin Kanri for the Lean Enterprise
- A Revolution in Manufacturing
- Factory Physics
Back to the lean books hub for reading paths and filters.
Rather see it on your own problem?
Bring the problem you are stuck on, and we will show you on a call how LeanSuite handles it.

