Lean Six Sigma: Stop Waste, Reduce Variation, Improve Flow

1. Why Improvement Needs a System

Most people think improvement is mainly about trying harder. But in real processes, effort alone usually doesn’t fix the root problem. One person works faster, another double-checks more carefully, a manager adds a rule — and yet the same delays, errors, and rework keep showing up.

That is because most process problems are system problems, not just people problems.

Think of it like preparing a meal in a hawker centre in Singapore. If the queue is long, you would not assume the customers are the problem. You would look at the flow: how orders are taken, how ingredients are staged, how the cook moves, how handoffs happen, and where waiting piles up. The result comes from the design of the whole system, not from one heroic person trying harder for one busy hour.

Lean Six Sigma starts from that same idea:

• Lean asks: What is unnecessary?
• Six Sigma asks: What is too variable?
• Together, they ask: How do we make the process work better, reliably, and with less waste?

By the end of this course, you will be able to explain to someone why improvement is not just about fixing people, adding effort, or writing more rules — it is about changing the system that produces the result.

That is the anchor for everything that follows:

Better outcomes come from better process design.

Once you see that, Lean Six Sigma stops feeling like a toolbox of buzzwords and starts making sense as a way of thinking about work, variation, and waste.

And that shift matters, because it changes the question from “Who made the mistake?” to “What in the system made the mistake likely?”

That is where real improvement begins.

2. The Two Core Ideas: Lean and Six Sigma

Remember earlier when we said improvement is really about changing the system that produces the result? Lean Six Sigma is built on two different but connected questions.

Lean asks: How do we remove waste?

Six Sigma asks: How do we reduce variation?

Those two ideas sound simple, but they point at two different kinds of trouble in a process.

1) Lean: Remove What Does Not Add Value

Lean is about waste — anything that uses time, effort, space, or attention without making the outcome better for the customer.

A process can look busy and still be wasteful. That is an important first principle.

The core idea

If a step does not help transform the input into something the customer actually values, it is a candidate for removal, reduction, or redesign.

A simple analogy

Think of packing a bag before leaving home. You do not want to carry ten items if only four are useful. Extra items slow you down, take up space, and make it harder to find what matters.

That is Lean in action: less carrying, less searching, less waiting, more flow.

What counts as waste?

Not just obvious trash. Waste can look like:

• waiting for approval
• moving things around unnecessarily
• doing work twice
• storing information in too many places
• overproducing something before it is needed
• making people ask the same question repeatedly

These are all different shapes of the same problem: effort that does not move the process forward.

Why Lean matters

Without Lean thinking, a process often becomes heavier over time. New checks are added. New forms appear. New handoffs are created. Each one may seem small, but together they create drag.

Remember earlier when we said system problems need system solutions? Waste is often what happens when a system has grown by adding layers instead of by simplifying flow.

2) Six Sigma: Reduce Variation

If Lean is about removing waste, Six Sigma is about making the process consistent.

Variation means the same process gives different results at different times, or from different people, or in different conditions.

The core idea

A good process should not behave like a coin toss. It should produce the same kind of result again and again.

A simple analogy

Imagine making coffee. If one cup tastes great, another tastes weak, and a third tastes bitter, the problem is not just taste — it is inconsistency.

You may have the right ingredients, but if the grind, water, or timing changes too much, the result changes too much.

That is what variation does in work processes too. It makes outcomes less predictable.

Why variation is a problem

Variation creates:

• defects
• rework
• confusion
• delays
• extra checking
• loss of trust in the process

When people cannot predict what will happen, they compensate by adding buffers, double-checks, and workarounds. Ironically, that often creates even more waste.

This is the same idea showing up again: instability in the process creates extra effort elsewhere.

What Six Sigma is trying to do

Six Sigma is trying to understand and reduce the sources of inconsistency so the process performs reliably.

It is not just about making things “good once.” It is about making them good repeatedly.

3) The Difference Between Waste and Variation

These two ideas are related, but not identical.

A process can have waste without much variation. And it can have variation without much waste. But in real life, they often feed each other.

A useful way to think about it

Lean is like cleaning up the path. Six Sigma is like making the path stable.

If the path is cluttered, people move slowly. If the path keeps shifting, people move carefully and uneasily.

A good process needs both: clear flow and reliable performance.

4) Why the Two Ideas Belong Together

Lean alone can make a process faster, but not necessarily more reliable. Six Sigma alone can make a process more consistent, but not necessarily simpler or faster.

That is why the two ideas work best together.

• Lean helps you remove friction.
• Six Sigma helps you reduce defects and inconsistency.

Together, they answer a bigger question:

How do we make work move smoothly and produce dependable results?

That question is the heart of Lean Six Sigma.

Another analogy

Think of a classroom system.

• Lean would ask: Are there unnecessary delays, repeated explanations, or confusing handoffs?
• Six Sigma would ask: Are students getting different instructions from different people, causing inconsistent results?

Both matter. If you only speed things up, you may spread confusion faster. If you only standardize confusion, you may preserve a bad process more efficiently.

That is why the combined view is so powerful: it avoids the trap of improving one part while damaging another.

5) The Hidden Assumption Behind Both

There is one more deep idea here.

Lean and Six Sigma both assume that variation and waste are not random fate. They usually come from how the process is designed.

That means improvement is not mainly about blaming people for what happened. It is about asking:

• Where is time being lost?
• Where is the process unstable?
• What forces are creating the problem repeatedly?

This is the same system-thinking we started with in Section 1. The new layer is that now you can name the two main forces you are looking for:

• Waste = unnecessary effort
• Variation = inconsistent results

If you remember only one thing from this section, remember this:

Lean removes what does not help. Six Sigma reduces what does not stay consistent.

When you combine them, you get a powerful way to think about improvement: not just faster work, but better-designed work.

And that is what makes Lean Six Sigma more than a method. It becomes a way to see how processes really behave.

3. How the Ideas Work Together in Real Processes

Remember earlier when we separated waste and variation? That distinction matters, but in real processes they rarely stay separate for long.

In the real world, they feed each other.

A process with waste often creates variation. A process with variation often creates more waste. And once both are present, the system starts to feel harder than it should.

That is the deeper reason Lean Six Sigma exists as a combined approach.

Lean clears the path. Six Sigma steadies the path.

Once you see that, the whole method becomes easier to understand.

When Waste Creates Variation

Imagine a process with too many handoffs.

Every handoff is a chance for something to be misunderstood, delayed, or done differently. One person assumes the next person knows the context. The next person interprets the request slightly differently. A small detail gets lost. Now the result is not just slower — it becomes less consistent.

That is how waste turns into variation.

Why this happens

Extra steps do not just add time. They add:

• more chances for misunderstanding
• more opportunities for delay
• more room for different interpretations
• more dependence on memory and judgment

The more a process relies on human guesswork, the more it varies.

So a process can look “organized” because it has many steps, but if those steps create confusion, the system is actually unstable.

This is the same idea showing up again: more activity is not the same as better design.

When Variation Creates Waste

Now flip the direction.

Suppose a process gives inconsistent results. Sometimes the output is correct. Sometimes it needs correction. Sometimes it is rejected. Sometimes someone must verify it again.

That inconsistency forces the system to add protection.

So people create:

• double checks
• approval layers
• backup records
• extra emails
• contingency time
• rework loops

These are all forms of waste, but they are usually added for a reason: to defend against unpredictability.

So variation creates waste by making people build safety nets.

A process that is unreliable tends to attract layers of compensation. Over time, the system gets heavier and slower because people no longer trust it to behave the same way twice.

The Loop That Keeps Processes Sluggish

This is the trap many organizations fall into:

1. A process has inconsistency.
2. People add checks to protect against mistakes.
3. The process becomes slower and more complex.
4. Complexity creates more chances for error.
5. More errors lead to more checks.

Now the system is stuck in a self-reinforcing loop.

At that point, people may say, “We need more discipline,” or “We need to be more careful.” But often the real problem is that the process itself has become too complicated and too unstable.

That is why Lean Six Sigma is not just about efficiency or quality in isolation. It is about breaking that loop.

A Simple Mental Model: Flow and Stability

A helpful way to connect everything so far is to think of every process as having two jobs:

Lean improves flow. Six Sigma improves stability.

Both are necessary because a process can be fast but unreliable, or reliable but slow.

If a process has flow but not stability

It moves quickly, but the result changes too much. That means speed is being wasted on rework, correction, or doubt.

If a process has stability but not flow

It may be consistent, but it is full of delays, layers, or unnecessary effort. That means reliability is being paid for with too much time and energy.

A good process needs both:

• smooth movement
• predictable output

That pairing is the heart of Lean Six Sigma.

A Real Example: Singapore Service Process

Let’s make this concrete with a familiar example.

Imagine a customer service desk in Singapore handling public-facing requests. The team receives forms, checks documents, routes requests, and updates customers.

At first glance, the process may seem fine. But then you notice two things:

• some requests sit waiting because the paperwork is incomplete
• some requests get handled differently depending on who receives them

Now both problems are present.

Where Lean helps

Lean asks: Why are requests waiting?

Maybe the form asks for unnecessary information. Maybe the routing is not clear. Maybe the same details are entered into multiple systems. Those are waste problems.

Where Six Sigma helps

Six Sigma asks: Why are similar requests getting different outcomes?

Maybe staff interpret the guidelines differently. Maybe the checks are not standardized. Maybe the data fields mean different things to different people. Those are variation problems.

If you fix only the waiting, but the outcomes still differ, the process is still fragile. If you fix only the inconsistency, but the process still has too many delays, the process still feels painful.

The real gain comes when both are improved together.

A process that is both lean and stable becomes easier to trust.

And once people trust a process, they stop building workarounds around it.

Why Trust Matters So Much

This is one of the less obvious but most important ideas in Lean Six Sigma.

People do not just respond to the process itself. They respond to how much they trust the process.

If a process is unreliable, people compensate:

• they keep their own notes
• they double-check everything
• they ask for approvals earlier than necessary
• they hold extra buffer time
• they avoid depending on the system

Those behaviors are understandable, but they also create more waste.

So trust is not a soft, emotional extra. It is a process outcome.

A stable process reduces the need for defensive behavior. A simpler process reduces the need for recovery behavior.

That is how Lean Six Sigma changes work beyond the visible metrics.

Why Improvement Often Fails When It Targets Only One Side

Many improvement efforts fail because they solve the wrong half of the problem.

Common mistake 1: Speeding up a broken process

If you accelerate a process that is unstable, you may simply produce defects faster.

Common mistake 2: Adding controls to a bloated process

If you add more checks to a process already full of waste, you may make it more reliable but also more painful to use.

Common mistake 3: Treating symptoms instead of design

If people keep fixing isolated incidents without changing the process, the same issues return in different forms.

Remember Section 1: the system shapes the result. Here we can add: the system also shapes the type of problem you see.

Sometimes the visible problem is delay. Sometimes it is error. Often, it is both.

What Lean Six Sigma Is Really Asking

At this point, the logic should be coming together.

Lean Six Sigma is not just asking, “How do we improve this?”

It is asking two linked questions:

1. What is making the process heavier than it needs to be?
2. What is making the process behave inconsistently?

Those questions are powerful because they do not blame people first. They look for design causes.

And once you start seeing processes this way, you begin to notice patterns everywhere:

• repeated approvals that do not improve the outcome
• unclear standards that create uneven results
• workarounds that hide instability
• delays that are actually the symptom of earlier confusion

That is the “aha” moment: what looked like separate problems are often different expressions of the same broken system.

The Big Connection

Let’s pull the thread tight.

• Waste means effort that does not add value.
• Variation means the process does not behave consistently.
• Waste makes processes slower, more confusing, and more fragile.
• Variation makes people add checks, buffers, and workarounds.
• Those workarounds create even more waste.

So Lean Six Sigma is not two unrelated tools. It is a way of seeing the same process from two angles:

• one angle asks where the drag is
• the other asks where the inconsistency is

Together, they reveal the shape of the system.

And that is why this matters in practice.

When you understand both, you stop asking only, “How do we make this faster?” You start asking, “What would make this smoother and more reliable at the same time?”

That question is what prepares you for the final part of the course — the part where we turn understanding into a practical way to think about improvement without losing sight of the system.

4. From Learner to Problem-Solver

You have now built the core mental model.

That is a bigger shift than it may feel like in the moment. You did not just learn a few terms — you learned how to see a process. That is what separates memorizing Lean Six Sigma from actually understanding it.

What you can now see

You can look at a process and ask better questions:

• Is there waste here?
• Is there variation here?
• Are we making work heavier, or less consistent, or both?

That is real progress. Because once you can ask those questions, you are no longer guessing. You are diagnosing.

Remember how we started: improvement is usually not about trying harder. It is about changing the system. Now that idea should feel natural, not abstract. Lean showed you how to spot unnecessary drag. Six Sigma showed you how to spot inconsistency. And when the two interact, you can see why processes become slow, fragile, and frustrating.

The identity shift

You now think like someone who looks beyond symptoms.

Instead of seeing:

• a late task, you see a flow problem
• a defect, you see a variation problem
• a workaround, you see a trust problem in the system

That is a different kind of thinking. It is calmer, clearer, and more useful.

What this unlocks

This understanding lets you explain improvement simply:

Lean Six Sigma helps a process move with less waste and perform with less variation.

That one sentence is now more than a definition. It is a lens.

So if someone asks you what Lean Six Sigma is really about, you can answer without sounding mechanical. You can say it is about designing work so it flows better, behaves more consistently, and depends less on heroics.

That means you are already able to speak about this like a problem-solver, not just a student.

Keep this final idea

The next time you notice a messy process, do not start with blame. Start with curiosity. Ask what is unnecessary, what is unstable, and what in the system is producing the same result again and again.

That question is where improvement begins.

And now, you know how to ask it.