Most manufacturers already run a quality programme. Far fewer run one that changes a decision outside the quality department. The method is rarely what fails: the tools are well documented, they can be taught inside a week, and the statistics behind them have not moved in decades. Containment is what fails. A programme owned by a function stays inside that function.
A quality programme that lives inside the quality function is a reporting exercise, and Lean Six Sigma produces savings only when the operating structure changes to carry it.
What Lean Six Sigma Combines, and Why the Two Halves Are Different
Lean Six Sigma is one name for two methods developed separately to attack different failure modes. Six Sigma came out of process statistics and targets inconsistency. Lean came out of production flow and targets waste. Treating them as one blurred idea is the most common reason a programme drifts.
Six Sigma Attacks Variation
Six Sigma is a data-driven approach to reducing process variation, and its unit of work is the defect. A process that holds an acceptable average while swinging widely around it is still failing, because the units at the edges of the distribution are the ones that come back from the field.
The Six Sigma approach to quality management runs through a five-phase cycle: Define, Measure, Analyse, Improve, and Control (DMAIC). It states the problem against the customer requirement it breaks, establishes a baseline, isolates root cause rather than correlation, changes the process, then holds the gain with monitoring that outlives the project team. The sequence does not permit a solution before a measurement.
Lean Attacks Waste
Lean targets activity that consumes resource without adding value to the customer, categorised through eight recognised forms of waste: defects, overproduction, waiting, non-utilised talent, transportation, inventory, motion, and extra processing (DOWNTIME). Most never reach a financial report as a line item.
The distinction is clean. Six Sigma makes a process consistent. Lean makes it lighter. A manufacturer that only reduces variation ends up with a stable process that still costs too much to run, which is why the combination is what produces consistent output at a lower cost of quality.
The Principles That Decide Whether a Programme Holds
The five principles read better as operating constraints than as a values statement, because each has a specific failure mode attached. This is where the question of why Lean Six Sigma is important to an engineering organisation gets its answer: the organisation already has data and process discipline, and still loses yield to problems that no single function owns.
- Define value from the customer's position: name who the output serves, or teams optimise a step nobody needed.
- Map the process and expose the waste: value stream mapping makes the flow visible, and bottlenecks are rarely where the organisation assumes.
- Reduce variation with data, not judgement: control charts and root cause analysis separate normal variation from a real signal, which is the difference between a fix and a reaction.
- Involve the people who run the process: operators and engineers hold failure knowledge that never reaches a report, and excluding them produces solutions the line rejects.
- Sustain the change through control: the Control phase is where most programmes quietly fail, because gains that nobody monitors regress within a quarter.
The 5 C's, Where the Principles Meet the Floor
The 5 C's are the workplace-organisation layer of the method, a British-usage variant of 5S: Clear Out, Configure, Clean and Check, Conformity, and Custom and Practice.
Read quickly, they look like housekeeping. On an electronics line they are quality controls first: component staging decides whether the correct reel reaches the correct feeder, and electrostatic discharge (ESD) discipline decides whether latent damage leaves the building inside a board that passed test.
This is the layer an auditor sees first, and it predicts defect rates more reliably than the quality manual does.
The Organisational Structure: Champions, Sponsors, and Belts
Lean Six Sigma is deployed through named roles with defined authority, and the authority is the part most organisations underestimate. Training produces people who hold a method. Sponsorship is what lets them use it. Without senior management behind the programme, belts stall at the first decision that sits above their own remit.
- Senior management: sets direction, funds training, and makes improvement a business objective rather than a departmental initiative.
- Champion: owns the programme at leadership level, selects the project portfolio, and clears obstacles a belt cannot clear alone.
- Sponsor: owns a specific project, holds the budget and the process, and is accountable for the result being adopted.
- Green Belt: applies the tools within their own function, runs projects alongside a day job, and delivers most of a programme's volume.
- Black Belt: works on improvement full time, leads cross-functional projects with wider scope, and coaches Green Belts.
- Master Black Belt: guides deployment across the organisation, mentors Black Belts, and manages the portfolio against business priorities.
Progression runs through that structure. A Green Belt who has delivered moves to Black Belt with further training and larger-scope projects, which is how an organisation builds internal capability instead of renting it.
Hard Savings, Soft Savings, and the Point at Which It Becomes Culture
Finance treats the two categories differently, and a programme that blurs them loses credibility quickly. Hard savings land in the accounts: scrap reduction, rework hours removed, first-pass yield, and inventory carrying cost. Soft savings change capacity rather than cash: cycle time, line capacity released, and engineering hours recovered from firefighting. Only one survives an audit, so presenting the second as the first is how a programme loses its sponsor.
The method becomes cultural when teams run the cycle without a project charter prompting them, which is what a learning organisation means in practice.
Applied across an end-to-end supply chain, the method governs supplier quality data, inbound inventory policy, and production planning, rather than the assembly step alone. Variation control at line level is what makes adaptive manufacturing lines viable for high-mix, low-volume production, because changeover only stays cheap when the process behind it is stable. The same logic runs backwards into New Product Introduction (NPI): the cheapest defect is the one designed out before production begins, and a tailored NPI process removes it where a change still costs an afternoon. For hardware that ships into a fleet, the same defect surfaces later as warranty returns and asset downtime.
Where Lean Six Sigma Sits in an Electronics Manufacturing Partnership
Quality is an organisational property before it is a process specification, which is why the discipline a manufacturing partner already runs matters more than the one it offers to adopt. PCI is an electronics manufacturing services (EMS) provider with over 50 years of experience, and Kaizen and Lean Six Sigma sit inside its manufacturing discipline rather than alongside it:
- Design for manufacture involvement: engineering engaged while the design is still changeable, so producibility problems are removed rather than managed.
- Supplier-managed inventory and just-in-time supply: material flow controlled against the build schedule, where Lean removes the buffer that hides other problems.
- High-mix low-volume production control: process stability held across frequent changeover, so variant complexity does not become variance.
- Testing and traceability: Failure Mode and Effects Analysis (FMEA), Production Part Approval Process (PPAP), and Ongoing Reliability Testing (ORT), with unit-level traceability.
The discipline is externally audited under ISO 9001, IATF 16949, and ISO 13485. Certification does not prove a culture exists, but it proves the control layer is inspected by somebody with no stake in the answer. A partner that already runs the method internally imports it into your programme instead of learning it on your build, and that extends to how you manage your supply chain, since supplier variation arrives at your line as your defect. If consistency and yield are the constraint, talk to PCI as your electronics manufacturing partner.
Frequently Asked Questions
What is the Six Sigma approach to quality management?
Six Sigma treats quality as a variation problem rather than an inspection problem. It uses a five-phase cycle, Define, Measure, Analyse, Improve, and Control, to move an issue from statement to sustained control. Measurement precedes any solution, root cause is isolated with data, and the gain is held by monitoring that continues after the project closes.
What are the 5 principles of Lean Six Sigma?
Define value from the customer's position, map the process to expose waste, reduce variation using data rather than judgement, involve the people who run the process, and sustain the change through control. Each is an operating constraint with its own failure mode. The last breaks most often, because gains that nobody monitors regress within a quarter.
What are the 5 C's in Lean Six Sigma?
Clear Out, Configure, Clean and Check, Conformity, and Custom and Practice, a British-usage variant of 5S. They govern how a workspace is organised and maintained. On an electronics line they function as quality controls: component staging, tool location, cleanliness, and electrostatic discharge handling all affect defect rates before any statistical tool is applied.
What is the main difference between Six Sigma and Lean Six Sigma?
Six Sigma reduces variation and defects through statistical analysis, working on the consistency of a process. Lean Six Sigma adds the Lean discipline of removing waste, which covers waiting, excess inventory, unnecessary movement, and overprocessing. Six Sigma makes a process consistent; Lean makes it lighter. The combined method addresses both, at a lower cost of quality.