VSM Foundation key terms

The sequence of activities an organization performs to deliver a product or service to a customer, from the moment a need is recognized until value is realized.

A management approach originating in manufacturing that emphasizes maximizing customer value while minimizing waste, and underpins modern value stream practice.

The manufacturing system developed at Toyota that introduced just-in-time flow, jidoka, and continuous improvement, and heavily influenced value stream thinking.

A visual technique that charts the steps, queues, and information flows required to deliver a product, revealing where time and effort are wasted.

A value stream map documenting how work actually flows today, including delays and rework, serving as the baseline for improvement.

A value stream map describing the intended improved flow after removing identified waste, used to guide and prioritize change efforts.

The total elapsed time from when a customer request or work item enters the value stream until it is delivered and accepted.

The portion of lead time during which work is actively being performed on an item rather than waiting in a queue.

The ratio of active process time to total lead time, expressed as a percentage, indicating how much of the wait is value-adding work.

A mathematical relationship stating that average work in progress equals throughput multiplied by average lead time for a stable system.

The rate at which a value stream delivers completed, accepted items over a given period, such as items per week.

Items that have entered the value stream but are not yet complete, including those actively worked and those waiting in queues.

The elapsed time an item spends waiting between process steps rather than being actively worked on, a major contributor to long lead times.

Any activity or delay that consumes resources without adding value for the customer, such as waiting, rework, or unnecessary handoffs.

A role accountable for the end-to-end flow of a value stream, coordinating across teams and removing impediments rather than managing people directly.

The person ultimately responsible for the outcomes, economics, and continuous improvement of a value stream across its full lifecycle.

A cultural and technical movement that unites software development and operations to shorten delivery cycles and improve reliability through shared ownership and automation.

The connected set of tools used across a value stream, such as planning, source control, build, test, deployment, and monitoring systems.

The ability to follow a work item, commit, or change through every stage and tool in the value stream, linking intent to deployment and outcome.

The practice of connecting tools so data and events flow automatically between them, reducing manual handoffs and keeping status consistent.

A practice where software is kept in a deployable state at all times, enabling frequent, low-risk releases through automated build and test pipelines.

An automated sequence of build, test, and release stages that moves a change from commit toward production, providing fast feedback at each stage.

The interconnected set of value streams within an organization, showing how streams depend on and feed one another rather than operating in isolation.

A value stream that delivers ongoing service to existing customers, focused on sustaining and improving steady-state operations.

A value stream concerned with creating new products or capabilities, moving from concept through delivery to the customer.

The activity of discovering and defining the value streams in an organization by tracing how customer value actually flows.

The recipient of the value produced by a stream, whether external end users or internal teams that depend on its output.

The smooth, uninterrupted movement of work through a value stream with minimal waiting, rework, or handoffs between stages.

The stage in a value stream with the least capacity, which constrains overall throughput and determines the pace of the whole stream.

Any factor that limits a value stream from achieving higher throughput or better outcomes, often but not always a capacity bottleneck.

An improvement approach holding that systems are limited by a few constraints, which should be identified, exploited, and elevated in sequence.

A Japanese term for continuous, incremental improvement, applied in value streams through small, frequent changes made by the people doing the work.

An ongoing practice of measuring, inspecting, and adjusting a value stream so it steadily improves in flow, quality, and customer outcomes.

A recurring cadence in which teams review value stream metrics and outcomes, then adjust plans and processes based on what they learn.

Quantitative measures of a stream's performance, such as lead time, throughput, and flow efficiency, used to guide improvement decisions.

A cap on how many items may be in progress at a stage, used to reduce queues, shorten lead times, and expose bottlenecks.

The deliberate, staged transformation of a value stream's structure, tooling, and measures over time to improve flow and customer outcomes.

Structuring teams and reporting lines so they align with end-to-end value streams rather than functional silos or technology layers.

An organizational or technical boundary that isolates a group or system, causing handoffs, delays, and loss of end-to-end visibility.