Lesson 1: What Six Sigma is, where it came from, and who does what

This course builds toward the IASSC Certified Lean Six Sigma exams, in three tiers: Yellow Belt first, then Green Belt, then Black Belt. Each tier is graded against the International Association for Six Sigma Certification's own published Body of Knowledge for that belt, and each ends with a practice exam matched to the real one's length, time limit, and 70 percent pass mark. This first lesson covers the opening section of the Yellow Belt Body of Knowledge: what Six Sigma actually means, where it came from, what a project is supposed to produce, and who holds which role on one.

What "Six Sigma" means

The name has two layers. Statistically, sigma is the Greek letter used for standard deviation, a measure of how spread out a process's output is around its average. A process with six sigma capability, meaning the specification limits sit six standard deviations from the process mean, produces about 3.4 defects for every million opportunities over the long run, by the standard convention that a process mean drifts by as much as 1.5 standard deviations over time (with no drift allowed, six standard deviations would mean only about two defects per billion, one beyond each limit). That is an extremely tight level of consistency. In practice, "Six Sigma" is used more broadly than that one statistic: it names a data-driven methodology for reducing variation and eliminating defects in any process, built around a structured project cycle, most commonly DMAIC: Define, Measure, Analyze, Improve, Control. Every lesson in this Yellow Belt tier maps to one letter of that acronym.

Where it came from

Six Sigma originated at Motorola in the 1980s, credited to engineer Bill Smith, as a response to unacceptable variation in manufacturing quality. Motorola reported that its use of the methodology saved the company billions of dollars over the following decade. The approach reached much wider adoption in the 1990s after General Electric, under CEO Jack Welch, adopted it company-wide and publicized the financial results. Over time, Six Sigma's statistical, defect-reduction focus was merged with Lean manufacturing's focus on eliminating waste and speeding up flow, producing the combined discipline this course teaches: Lean Six Sigma, covered starting in Lesson 4.

What a Lean Six Sigma project is supposed to deliver

A Lean Six Sigma project is not finished when a team has an idea for how to fix something. It is finished when it has produced a specific, documented set of deliverables: a clearly defined problem and goal statement, data showing the process's current performance, an identified and verified root cause, an implemented improvement, measured results showing the improvement held, and a control plan that keeps the gain from eroding after the project team moves on. A project that stops at "we think we fixed it" without measured, sustained results is not a completed Six Sigma project by this standard.

The core problem-solving strategy: Y = f(x)

Six Sigma frames every problem using one simple equation: Y is a function of X, written Y = f(x). Y is the output that matters, the result a customer or the business cares about, such as a defect rate, a cycle time, or a cost. The X's are the inputs and process variables that drive that output. The entire DMAIC cycle is, at bottom, a disciplined search for the vital few X's that actually control Y, so that a team stops guessing at solutions and instead changes the specific inputs that the data shows are driving the result. A team that manages the X's controls the Y; a team that only watches the Y after the fact is managing the past, not the process.

Voice of the Customer, Voice of the Business, Voice of the Employee

Before a project defines what "good" looks like, it has to know whose definition of good it is using. Three voices are gathered and reconciled:

• Voice of the Customer (VOC), what the end user of the process or product actually needs and values, gathered through surveys, interviews, complaints, and direct observation.
• Voice of the Business (VOB), what the organization needs from the process financially and strategically, such as cost, throughput, and risk.
• Voice of the Employee (VOE), what the people who run the process day to day know about where it breaks down, which is often the most accurate and most overlooked source of all three.

A project charter that reflects only one of these three voices, usually VOB because it is the easiest to measure, tends to produce a fix that looks good on a spreadsheet and fails in practice.

Six Sigma roles and responsibilities

Six Sigma organizes its practitioners into a belt hierarchy borrowed from martial arts ranking, each with a distinct scope of responsibility:

• Executive Leadership / Champion: sets strategic direction, selects and sponsors projects, removes organizational barriers, and is ultimately accountable for results.
• Master Black Belt: an expert-level, typically full-time practitioner who trains and coaches Black Belts and Green Belts and advises leadership on where to point projects.
• Black Belt: typically leads complex projects full time, deeply trained in the statistical tools used in the Analyze and Improve phases.
• Green Belt: leads or supports projects as part of their regular job rather than full time, trained in the core DMAIC tool set.
• Yellow Belt: has foundational awareness of Six Sigma concepts and vocabulary and typically participates on a project team rather than leading one, which is the level this first tier of the course targets.
• Process Owner: the person who owns the process being improved on an ongoing basis and who inherits the control plan once the project team disbands.

Understanding this hierarchy matters beyond the exam: it tells a Yellow Belt what to expect from a project, who to escalate a blocked issue to, and whose sign-off actually closes a project out.