Key Concepts Quick Review

When “good work” still feels chaotic

You’re a Yellow Belt on a small improvement team. The supervisor says, “We need faster turnaround,” the frontline says, “We’re drowning in rework,” and a customer email complains, “It’s inconsistent.” Everyone is pointing at a different problem, and every fix idea sounds reasonable—but the results don’t stick.

This is exactly where Lean Six Sigma concepts earn their keep: they give you shared definitions and a common way to think about performance. When the team agrees on what “waste,” “variation,” “defect,” and “value” really mean, conversations get clearer and decisions get easier. A quick review now helps you spot patterns faster and avoid the most common beginner mistakes.

This lesson refreshes the key ideas you’ll keep using in every project conversation, even before you touch any tools.

The handful of terms that make Lean Six Sigma “click”

Lean Six Sigma blends two complementary lenses:

• Lean focuses on speed and flow by removing work that doesn’t create value.

• Six Sigma focuses on quality and consistency by reducing variation and defects.

A simple way to remember it: Lean asks, “Are we doing work we shouldn’t be doing?” and Six Sigma asks, “Are we doing the work reliably the same way every time?” Most real problems have both elements: delays often come from rework (quality) and from handoffs/queues (flow).

These core definitions prevent teams from talking past each other:

• Value: what the customer is willing to pay for (or what meets the customer’s need in a time-sensitive, compliant way in internal services).

• Waste: effort that consumes resources but doesn’t create customer value.

• Variation: inconsistency in how a process performs or how outputs look (time, errors, outcomes).

• Defect: an output that fails a requirement (a “CTQ,” or critical-to-quality need).

• Process: a repeatable set of steps that turns inputs into outputs; if performance is predictable, it’s usually because the process is stable.

Keep one principle in mind: you don’t improve results by telling people to “try harder.” You improve results by improving the process the work flows through.

The essential ideas, with the nuance beginners often miss

Customer value and CTQs: the target you’re actually aiming at

“Improve the process” is only meaningful if you know what “good” looks like. In Lean Six Sigma, that “good” is expressed as customer requirements, often translated into CTQs (Critical to Quality characteristics). A CTQ is a measurable requirement that defines whether an output is acceptable—accuracy, completeness, cycle time, on-time delivery, safety criteria, and so on. Even in internal processes, you still have a “customer”: the next step in the workflow, another department, or an external end user.

A practical way to think about CTQs is that they turn opinions into observable checks. “Fast service” becomes “answered within 30 seconds.” “Correct order” becomes “no missing items and matches the ticket.” “Easy to understand” becomes “uses the approved template and includes required fields.” When teams skip this translation, they often improve something that feels better internally but doesn’t move what the customer experiences.

Best practice is to define CTQs at the right “altitude.” Too high-level (“be excellent”) can’t be measured; too low-level (“use font size 12”) may become compliance theater without improving the output. A good CTQ balances measurability and meaning: it should be easy to verify and tightly connected to value. One common misconception is that CTQs only apply to external customers; in reality, internal CTQs often drive major gains because they reduce rework and handoff confusion.

Common pitfalls show up quickly. Teams sometimes pick a metric they already have (like “number of tasks completed”) rather than one that reflects value (like “first-pass accuracy” or “time to resolution”). Another pitfall is confusing a goal with a requirement: “reduce cycle time by 20%” is a target; “complete within 2 business days” is a requirement. Getting clear on CTQs keeps improvement work honest and prevents “success” metrics that don’t matter.

Waste vs. value-added work: why speed improves when you remove friction

Lean defines value-added work as the work that changes the product or service in a way the customer cares about, is done right the first time, and is something the customer would be willing to pay for (or would insist must happen). Everything else is either non-value-added but necessary (like regulatory steps) or pure waste (like searching for information). In many service and administrative processes, truly value-added time is a surprisingly small fraction of total lead time because so much time is spent waiting, clarifying, correcting, and handing off.

A helpful way to see waste is to focus on where work stops flowing. Queues, inbox backlogs, approval bottlenecks, and “waiting for a response” are often bigger drivers of delay than the actual task time. Rework is another major hidden factory: each correction loop consumes capacity and creates more waiting for everyone. When you remove waste, you don’t merely “go faster”—you free up time and attention so the process becomes easier to execute consistently.

Best practices here start with observation and specificity. Identify waste in terms of concrete behaviors: “printing and re-keying data,” “searching multiple systems,” “asking the customer for missing info,” “waiting for a signature,” “batching requests until Friday.” Then connect each to a cause: unclear standards, too many handoffs, poor system design, uneven workload, or ambiguous requirements. Lean improvements are strongest when they reduce touches, delays, and handbacks instead of just pressuring people to work quicker.

A frequent misconception is that Lean equals “cutting people” or “working harder.” Lean is about designing the work so the same people can create more value with less frustration. Another pitfall is labeling everything as waste and trying to remove necessary controls; in regulated or safety-critical environments, some non-value-added steps are still essential. The goal is to remove waste first, then streamline what must remain.

Variation and defects: why the same process gives different outcomes

Six Sigma shines a light on variation: the same process, with the same intent, produces different results depending on who does it, when it’s done, or what inputs arrive. Variation shows up as fluctuating cycle times, inconsistent accuracy, uneven customer experience, and “sometimes it works, sometimes it doesn’t.” A key beginner insight: variation is a process property, not a personality trait. If outcomes depend on which employee happens to handle the case, the process is likely underdefined, overloaded, or full of hidden decision points.

Defects are outputs that don’t meet requirements. In service work, defects often look like missing information, incorrect entries, wrong routing, unclear communication, or incomplete resolution. Defects create rework, and rework worsens queues, and queues increase waiting time—so variation and waste reinforce each other. That’s why Lean and Six Sigma are so often used together: reducing defects stabilizes flow, and improving flow makes it easier to do quality work.

Best practices for thinking about variation start with separating two ideas: common-cause variation (the natural fluctuation of a stable process) and special-cause variation (a signal that something unusual happened—system outage, new policy, staffing shock). Beginners often chase special causes with expensive fixes or, conversely, react to normal fluctuation as if it were a crisis. A stable process can still be “bad,” but if it’s stable you can improve it systematically; if it’s unstable you need to understand what’s creating the swings.

Misconceptions are common here. One is that “zero defects” is always realistic; in many processes, the practical aim is to reduce defects to a level aligned with risk and cost. Another misconception is that variation is solved only by training. Training helps, but if the process design forces workarounds (unclear inputs, conflicting systems, ambiguous approvals), training alone won’t hold the gains. Last, teams sometimes measure what’s easy (like volume) rather than what reflects variation (like spread in cycle time, percent complete-and-accurate, or rework rate).

Lean vs. Six Sigma: choosing the right lens (and when to use both)

Lean and Six Sigma can feel like competing methods, but they usually answer different questions about the same problem. Lean is strongest when delays are driven by handoffs, batching, and waiting—when the system is full of “stops.” Six Sigma is strongest when outcomes are inconsistent—when customers experience defects or when performance swings day to day. Many projects start with one lens and naturally incorporate the other as root causes become clearer.

Use this comparison to quickly sense which approach is leading your thinking:

A useful practical mindset is: start where the pain is most visible, then validate with data. If customers are angry about errors, lead with quality and defect prevention. If customers are angry about delays, lead with flow—while still protecting quality so you don’t create a rework spiral.

Two grounded examples of how these concepts show up at Yellow Belt level

Example 1: A clinic’s patient check-in delays (flow problem with a quality trap)

Imagine a clinic where patients arrive on time but the waiting room backs up every morning. Staff report they’re “busy the whole time,” yet the line grows. A quick Lean lens asks: where is time spent waiting versus being processed? You map the high-level steps: arrival, form completion, insurance verification, copay collection, registration, and handoff to nursing.

Step-by-step, you notice two major wastes. First, batching: insurance verification is done in chunks “when there’s time,” so early patients wait for a batch to finish. Second, searching and re-entry: staff type the same demographics into two systems. Those create long lead time without creating value. Lean improvements might include doing verification in a simple first-in-first-out sequence, and creating a standard handoff so the second system pulls data once instead of re-keying.

Now the quality trap: when you push for speed, staff may skip asking for a secondary contact number or miss an allergy question—creating downstream defects that cause nurse callbacks and appointment delays later. That’s where CTQs keep you honest. If a CTQ is “patient record complete for triage,” then the improvement must protect completeness while reducing waiting. The impact is usually twofold: shorter morning queues and fewer downstream corrections, but the limitation is that system integration may require IT support—some fixes aren’t purely procedural.

Example 2: Order fulfillment rework in a small warehouse (defects driving delay)

A small warehouse ships parts to internal technicians. The complaint isn’t just speed—it’s “the kit is often wrong.” Technicians waste time returning for missing items, and the warehouse gets interrupted constantly. A Six Sigma lens starts by defining the CTQ: “kit is complete and correct on first delivery.” A defect is any missing part, wrong quantity, wrong version, or incorrect labeling.

Step-by-step, you track where defects originate. You find variation in picking: some pickers rely on memory, others follow the ticket; some substitute parts when stock is low without noting it. You also find inconsistent input quality: work orders sometimes omit a part revision level. The fix focus becomes stabilizing the process: standard pick lists with revision control, a clear rule for substitutions, and a simple check that confirms completeness before staging.

Once defects reduce, Lean benefits show up naturally. Fewer callbacks mean fewer interruptions, which reduces queueing at the pick station and helps cycle time stabilize. The impact is improved first-pass yield and smoother daily workload; the limitation is that adding a check step can initially feel “slower” until rework drops enough to offset it. This is a classic Lean Six Sigma dynamic: a small amount of prevention time can eliminate a large amount of correction time.

A clear mental checklist to carry forward

Lean Six Sigma can feel like a lot of vocabulary, but the working logic is simple:

• Start with customer value and turn it into CTQs you can verify.

• See delays through a Lean lens: where is work waiting, repeating, or being handed off?

• See inconsistency through a Six Sigma lens: where does variation create defects and rework?

• Remember the reinforcing loop: defects create rework, rework creates queues, queues create delay.

This sets you up perfectly for DMAIC and Tools Recap [25 minutes].