Lean Gold key terms

Any capability or feature a customer is willing to pay for because it meets a real need at the right time and price. Everything else performed in a process is a candidate for elimination.

Value specified from the external customer's perspective rather than from internal convenience or habit. It anchors improvement work, because teams routinely mistake internal activity for customer value.

The complete sequence of actions, both value-adding and non-value-adding, required to move a product or service from concept or order through delivery to the customer.

A paper-and-pencil visualization of material and information flow across a value stream, showing process boxes, inventories, cycle times, and delays so improvement opportunities become visible and quantified.

A map drawn from direct observation of how the value stream operates today, including real queues, delays, and rework. It establishes the baseline against which future improvement is measured.

A target map describing how the value stream should flow after planned improvements, with specific kaizen bursts assigned. It converts analysis into an actionable, time-phased improvement plan.

Value-adding time divided by total lead time, expressed as a percentage. Low percentages reveal large hidden queues, making it a compact measure of how much of a process is genuinely productive.

A relationship stating that average work-in-process equals throughput multiplied by average lead time. It lets teams predict how reducing inventory or arrivals shortens waiting time without simulation.

The total elapsed time from when a customer requests something until it is delivered. It is measured from the customer's clock, not from when work actually starts.

The time a process step takes to complete one unit of work from start to finish of that step. Comparing cycle time to takt time shows whether capacity matches demand.

Available production or service time divided by customer demand for the same period. It sets the heartbeat a process must match so output aligns with what customers actually require.

The constraint step whose capacity limits total output of the value stream. Improving anything other than the bottleneck usually increases inventory rather than throughput.

Any activity that consumes resources without creating value for the customer. It is the primary target of lean improvement, addressed by eliminating, simplifying, or combining the activity.

A checklist of common non-value-adding categories: defects, overproduction, waiting, non-utilized talent, transportation, inventory, motion, and extra processing. Teams use it to spot waste systematically rather than by intuition.

Unevenness or variability in demand, workload, or process output. Smoothing flow and leveling work reduces mura, which in turn prevents the bursts of waste that variability creates.

Overburden placed on people, equipment, or systems beyond reasonable capacity. It causes errors, burnout, and breakdowns, so lean design aims for workloads that are sustainable over time.

Producing more, earlier, or faster than the next process or customer needs. It is often called the worst waste because it hides other problems and generates excess inventory, transport, and defects.

Work that has been started but not yet delivered, such as queued files, stocked parts, or backlog. It ties up capital, lengthens lead time, and conceals quality problems until late.

Unnecessary movement of people, such as walking, reaching, or searching for tools and information. It adds fatigue and time without adding value, and is often fixable with workplace organization.

Doing more work than the customer requires, such as redundant approvals, duplicate data entry, or unnecessary formatting. It survives because internal rules, not customer needs, often drive it.

Continuous, incremental improvement made by the people who do the work, often through small experiments rather than large projects. It builds problem-solving capability and sustains gains over time.

A focused, time-boxed workshop, typically a few days, in which a team analyzes a specific process and implements improvements immediately. It delivers fast results but needs follow-up to hold gains.

A disciplined improvement loop of plan, do, check, and act. Each pass tests a hypothesis on a small scale, compares results with expectations, and standardizes what worked.

A structured method that captures a problem, current condition, root cause, countermeasures, and plan on a single large sheet. The format forces clear thinking and enables coaching through dialogue.

A systematic effort to identify why a problem occurs, rather than treating its symptoms. Common techniques include the five whys and cause-and-effect diagrams, followed by verification of the suspected cause.

A questioning technique that repeatedly asks why a problem occurred until the underlying systemic cause is reached. It works best when each answer is checked against evidence at the actual workplace.

A workplace organization method with five steps: sort, set in order, shine, standardize, and sustain. It removes clutter, makes abnormalities obvious, and provides a foundation for standardized work.

A documented, currently best-known sequence of steps, takt time, and required inventory for a process. It is the baseline that makes deviation visible and enables controlled improvement.

A device or design feature that prevents an error from being made or makes it immediately obvious. It builds quality into the process instead of relying on inspection or operator vigilance.

The principle of stopping the process automatically or by operator action when an abnormality occurs, so defects are not passed downstream. It separates human work from machine monitoring and protects flow.

A visual signal, such as a light or board, that shows process status and calls for help when an abnormality appears. It supports fast response and makes problems visible to everyone.

Producing and delivering only what is needed, when it is needed, in the quantity needed. It depends on leveled demand, stable quality, and reliable suppliers to work without buffers.

A flow design in which downstream demand triggers upstream replenishment, rather than upstream pushing output forward on a schedule. It caps inventory and exposes problems quickly.

A signaling mechanism, often a card or electronic flag, that authorizes replenishment or the next step of work. It makes work-in-process limits explicit and self-regulating.

Leveling the type and volume of work over time so the process experiences a smooth, predictable load. It reduces mura and allows smaller buffers, shorter lead times, and steadier quality.

The actual place where work is done and value is created. Going to gemba means observing real conditions and talking with the people doing the work before drawing conclusions.

A documented routine of daily and weekly leadership behaviors, such as layered checks and coaching conversations, that sustains lean gains. It shifts leaders from firefighting toward process confirmation.

A routine of short team meetings, visual boards, and escalation paths that surfaces problems and tracks performance every day. It keeps improvement tied to real operating results.

Using displays, markings, and indicators so that normal versus abnormal conditions are understood at a glance. It reduces reliance on reports and speeds up response at the point of work.

A core lean principle holding that improvement comes from engaging and developing the people closest to the work, not from treating them as interchangeable resources. It underpins sustainable change.

Shared habits and beliefs in which problems are surfaced without blame, experiments are expected, and leaders coach rather than command. It determines whether tools produce lasting results.

A strategy deployment process that cascades a few breakthrough objectives into measurable targets and actions at each level, with regular review cycles. It aligns improvement work with organizational priorities.

A management approach that identifies the system constraint, exploits it, subordinates other steps to it, elevates it, and repeats. It focuses improvement where it actually increases throughput.