Designing and optimizing value streams

A value stream map of the current state is only the beginning. Its purpose is to help the organization design a better future state and move toward it. This lesson explains how to optimize value streams: removing waste, managing flow and bottlenecks, limiting work in progress, reducing handoffs and approvals, and automating where it helps. It also covers how to prioritize improvements, how to think about complexity, and how to measure whether the redesigned stream actually delivers more value.

From current state to future state

Optimization starts with the current-state map from lesson 8. The team asks: what would this value stream look like if it were designed to deliver value to the consumer as quickly and reliably as possible? The answer is a future-state map, showing fewer steps, shorter waits and higher %C&A. The future state is a target, not a promise. The organization moves toward it through a series of improvements, applying the guiding principle progress iteratively with feedback.

The ITIL guiding principles provide a useful checklist for optimization. Focus on value asks whether each step matters to the consumer. Start where you are asks what already works. Keep it simple and practical asks which steps can be removed. Optimize and automate asks, in that order, how to improve and then automate. Think and work holistically reminds the team that improving one step at the expense of others does not improve the stream.

Types of waste

Lean thinking identifies several types of waste that appear in service value streams as much as in factories. Recognizing them helps teams see opportunities they might otherwise accept as normal.

Bottlenecks and constraints

Every value stream has a constraint: the step with the lowest capacity relative to demand. Work piles up before it and flows freely after it. Improving any other step does not increase the throughput of the whole stream; it simply moves more work into the queue before the constraint. This idea, from the theory of constraints, is a powerful guide to where improvement effort should go.

Limiting work in progress

Little's Law, introduced in lesson 7, shows that for a given throughput, more work in progress means longer lead times. Many teams start too much work at once, believing it makes them productive. In practice, it increases waiting, context switching and the chance that urgent items get stuck behind half-finished ones. Limiting work in progress (WIP) is one of the simplest and most effective optimizations. Kanban boards with explicit WIP limits make the limit visible and encourage teams to finish work before starting more.

Reducing handoffs and approvals

Each handoff between teams adds a queue, a chance for misunderstanding and a loss of context. Approvals add similar delays and are often retained long after the risk they were meant to control has disappeared. Optimization asks, for each handoff, whether one cross-skilled team could perform both steps, and for each approval, whether the risk justifies it or whether a pre-authorized standard change, a policy or an automated check would be enough.

Automation

Automation can remove waiting and manual effort, but only after the stream has been simplified and optimized. Automating a wasteful step makes waste faster and harder to change. Good automation candidates are steps that are frequent, standardized, rule-based and error-prone when done by hand: account creation, software deployment, standard approvals based on clear rules, and notifications. ITIL-150 covers automation, DevOps and AI in more depth.

Prioritizing value stream improvements

A current-state map usually reveals more improvement opportunities than a team can pursue at once. Prioritization should consider the effect on lead time and %C&A, the effort required, and whether the improvement addresses the constraint. Cost of delay and WSJF, from lesson 2, work well here. Improving the constraint first usually gives the biggest gain; improvements elsewhere may wait until the constraint moves.

Complexity and experimentation

Published Version 5 course outlines mention complexity thinking alongside workflow optimization. Some value streams are simple and predictable: the same steps every time, with well-understood cause and effect. Others are complex: outcomes depend on many interacting factors and cannot be fully predicted. Simple streams can be optimized with standard procedures and automation. Complex streams benefit more from small experiments, fast feedback and adaptation. Recognizing which kind of stream you are dealing with helps choose the right approach.

Measuring the future state

Every improvement should be measured against the baseline from the current-state map. Useful measures include lead time, flow efficiency, rolled %C&A, throughput and consumer outcomes such as satisfaction or effort scores. Measuring both speed and quality guards against improvements that speed things up at the cost of more errors.

Public bodies in Canada increasingly publish service standards, for example the time to process an application, as required by the Treasury Board Policy on Service and Digital. Value stream optimization is one way departments work toward those published standards.

Sustaining the improved stream

Improvements to a value stream tend to fade unless they are sustained. People return to old habits, new approvals creep back in, and work in progress grows again. Sustaining the future state requires visible measures (for example, lead time and WIP displayed on a team board), regular reviews of the stream, and clear ownership. Many organizations appoint a value stream owner who is accountable for the end-to-end flow, not for any single team within it. The owner watches the measures, convenes the teams when performance slips and keeps the next round of improvement moving.