Lean Six Sigma: How the Methods Work Together

Lean Six Sigma combines two ways of studying work. Lean asks how a process creates what the customer needs and where work gets stuck or wasted. Six Sigma asks why the process varies and how defects occur. The methods can complement each other without being the same thing. A course or certificate does not guarantee a job or higher pay.

Use the problem to choose the tools. A long queue may need a flow study. Inconsistent results may need more measurement and cause analysis. When both are present, a combined project can address them in sequence. A Lean Six Sigma course or belt is still a provider-specific award, with its own assessment and entry rules.

What Lean Six Sigma combines

The Lean Enterprise Institute's definition centres Lean on creating needed value with fewer resources and less waste. The starting point is the work and the customer need. It is not simply asking staff to work faster.

ASQ's Six Sigma reference explains an evidence-based approach to variation and defects. A team needs a clear definition of the problem and data that can test possible causes. Statistical tools serve that question; using a chart does not by itself make the analysis useful.

Combined work can so ask two distinct questions about one process. Is the route through the work sensible? Are the outputs consistent with the requirement? The answers can point to different causes and actions.

Think of a service request that waits for approval and then comes back with missing details. Do not assume the waiting time and missing details are the same defect. A team should define them separately before choosing a tool or claiming progress.

Flow, waste and variation

Flow describes how a case, item or request moves through the process. Waiting, unnecessary transfers and rework can interrupt it. A process map can show where those events occur. But it needs to describe what actually happens instead of the ideal procedure.

Variation describes differences between results. Requests might take different amounts of time, or staff might apply different checks. The team needs to decide which differences matter and how to measure them. Not every difference is harmful.

The table is a way to frame a study. It is not a rule that Lean uses no data or Six Sigma ignores flow. Both need knowledge of the work. Keep the question clear so the tool does not become the purpose of the project.

A worked illustrative process

Imagine an office processing equipment requests. A request goes from the employee to a supervisor, then to administration and purchasing. Some cases wait between steps, while others return because details are missing.

Employee request → supervisor check → administration review → purchasing action.

Missing information ↶ returns to the employee. Waiting can occur before each review.

First, walk through real cases with the staff who do the work. Ask which details each step needs and why it exists. A policy may require approval, while a duplicate transcription step may have no clear purpose. The team should check instead of assume.

Next, agree where the process starts and ends. If one person measures from the first draft and another from approval, their times cannot be compared fairly. Define a complete request too. A case should not become a defect only because one reviewer prefers a different format.

The Lean question is whether the handoffs and waiting are necessary. The Six Sigma question is whether certain case conditions are linked to missing details or variable completion. The team might discover that different request types need different instructions. That remains a hypothesis until the records and work observations support it.

An initial trial could simplify one handoff or clarify one input rule. Do not make every possible change at once if doing so prevents the team from learning which one helped. Record the same measures before and during the trial, including any unwanted effect on accuracy or staff workload.

The result of the example is a plan for investigation, not a claimed improvement. There is no invented saving, defect reduction or completion-time gain. A real project needs its own baseline and comparison before making those statements.

Where DMAIC fits

DMAIC is the Define, Measure, Analyze, Improve and Control sequence commonly used for an existing process. It can organise a combined project as long as the team keeps the evidence rules clear. The Six Sigma introduction explains each phase in more detail.

In Define, name the customer need and process boundary. A team may begin with a flow complaint but discover that it has not agreed what a successful result means. That agreement comes before a large data collection exercise.

In Measure, capture the current work under stable definitions. Record missing data instead of filling gaps with guessed times. Observe handoffs and collect output checks as appropriate. The measurement plan should fit the question, not simply collect every available field.

In Analyze, compare plausible causes with evidence. A queue might reflect batch approval, uneven demand or a missing input. Those explanations imply different actions. The team should avoid blaming a person when the process design creates the same problem repeatedly.

In Improve, test a suitable change. In Control, name the owner, standard work and follow-up check. A new process map is not a control plan unless someone knows how to keep it current and respond when the work drifts.

What to do when the data is weak

If timestamps are missing or definitions differ, begin by fixing the measurement method. You may still observe the workflow and list the measurements you still need. Do not turn a small set of inconsistent records into a precise statistical conclusion.

A useful beginner contribution is often to make the data collection clearer. Write a simple definition, try it on a few sample cases for practice, then discuss the real collection method with the process owner. Any live use must follow the workplace's data and access rules.

Team and belt responsibilities

The process owner understands what must keep working after the project ends. Team members bring knowledge of the daily tasks. An analyst or experienced improvement lead can help choose methods and check assumptions. A sponsor can resolve scope and resource decisions.

Belt titles often describe training or responsibility. But they do not create a universal project structure. A Yellow Belt may help gather consistent data. A Green Belt may lead a bounded project. Check the workplace's expectations and the issuer's award rules separately.

For example, ASQ CSSGB requires three years of relevant full-time paid work and offers no education waiver. A beginner-friendly course with no admission prerequisite does not remove that requirement. Source: ASQ Green Belt requirements, Checked November 2026.

Access to a project also matters. A learner can study a hypothetical example at home. But a real improvement project needs a process owner, usable data and permission to test changes. A course certificate alone does not prove those conditions existed.

Keep two measures from becoming one vague goal

For the sample request, waiting time and completeness should remain separate measures. A request can be complete and still wait. It can also move quickly while missing a necessary item. Keeping both visible helps the team see whether a proposed change merely moves the problem to another step.

Use a common case identifier and collection point if the workplace permits that approach. The exact live data method needs the process owner's agreement. The purpose is a traceable comparison, not collecting more personal details than the task needs.

Choose methods or training

Start with the process question if you are solving a work problem. Identify the user need, current workflow and evidence gap. You may need a simple process observation before you need an advanced statistical tool.

Start with the award if you are choosing a credential. The certification comparison names different issuers and award types. The training comparison compares ways to learn, including the limits of an introductory course.

Lean Six Sigma is most useful as a combined set of questions about real work. Choose a method because it fits the problem, then choose training that develops the skills you lack. Return to the Six Sigma guide for the broader sequence and terminology.