Value stream identification, mapping, and management

Fulfilling a password reset and launching a brand-new digital product both begin as demand and end as delivered value, yet they take very different routes through the organization, and each of those routes is a value stream. A value stream is the end-to-end series of steps that turns one particular demand into value for a consumer, assembled from the same eight value chain activities (discover, design, acquire, build, transition, operate, deliver, support) arranged for that one scenario. The whole domain rests on holding a three-way distinction: the value chain is the reusable operating model, a value stream is one situation-specific path through it, and a process is a defined set of steps used inside the activities. The trap the exam sets is to blur a value stream with the value chain, or to confuse this domain with the 'value streams and processes' dimension from the Four Dimensions: that dimension is one lens applied to every product, whereas this domain is about mapping and improving one specific stream.

Three subtopics take the domain in order. Key Concepts of Value Stream Mapping and Management defines the vocabulary: what a value stream is, the difference between a core value stream (one that delivers to an external consumer) and an enabling value stream (one that delivers to an internal recipient so the core streams can run), value stream mapping versus value stream management, and complexity thinking. Application of Value Streams puts streams to work, showing that you optimize each workflow for its own complexity rather than with one uniform method, standardizing and automating predictable steps while leaving room for experimentation and feedback in uncertain ones, which is why an organization runs many separately-tuned streams at once. Purpose of Value Stream Mapping and Management closes the loop by explaining why you bother: to make the flow of value visible, expose waits, handoffs, and waste, and continually improve how work moves from demand to delivery. Reach for the first for a definition, the second for how a workflow is optimized, and the third for the purpose of mapping or the elements of a value stream map.

Two defaults win most questions in this domain. First, drawing a value stream map is never the goal; improving the flow of value is, so when one option treats the map as the finished deliverable and another treats it as the input to ongoing management and improvement, prefer the latter. Second, mapping produces a point-in-time snapshot while management is the continuous work built on it, so an item asking what keeps a stream improving over time wants management, not another map. For the core-versus-enabling split, use the recipient test: value that reaches an external consumer directly is a core stream, and value delivered to an internal recipient to support the core streams is enabling. This is why the domain sits close to continual improvement, since its whole point is turning a vague sense that work is slow into specific, evidence-based improvement targets.