OPEXSTUDIO
OPEX learning notes / System chapters

Lean Flow: Improve Lead Time and System Performance

Explain how customer need, reliable work and release decisions form one delivery system. The labelled map shows Customer need, See the whole route, Set the pace, Connect the work, Reliable execution, Constraint focus, Measure the result, Learn and adjust.
AI-generated system teaching illustration. Follow the steps below, then try the practice question. View full size ↗
← All lessons and training aids

Lean flow follows work from customer need to delivery, including the time it spends waiting. Use this chapter when local productivity gains are not improving the whole process. Connect demand, process timing, work in progress and constraints before choosing a change to test.

Fictional teaching examples and AI-generated illustrations. Proposed changes and goals are not achieved results. Use the written instructions and check local conditions before applying a method.

Published by OPEX Studio, a Prometheus Platforms product. Read the method sources and their scope.

On this lesson
Teaching view 1 of 3

Connect demand, flow and the system constraint

Begin with required good output and the route that delivers it. A fast local step can still create waiting or excess WIP elsewhere. Relate demand to available working time, then choose how adjacent processes connect. Reliable methods and quality support this connection. In parallel, test what limits the system goal; a large queue alone does not prove the constraint. Align release and supporting work to that evidence. Check delivery, quality, WIP and workload together before expanding a change. Lean flow questions and TOC constraint questions can support the same investigation while retaining their distinct controls.

Follow the method

  1. Customer need: Required good output and timing
  2. See the whole route: Work, waiting and information
  3. Set the pace: Takt and a realistic release rhythm
  4. Connect the work: Flow, bounded FIFO or replenishment pull
  5. Reliable execution: Standard work, ready resources and quality
  6. Constraint focus: Protect the limiting system capability
  7. Measure the result: Delivery, WIP, quality and workload
  8. Learn and adjust: Test the whole-system effect

Read the example carefully

Takt is a demand reference; it is not a measured cycle time.

Flow, FIFO and supermarket pull require different operating conditions.

The constraint hypothesis requires route and operating-state evidence, not queue size alone.

Try it before revealing the answer

A team proposes speeding an upstream step while downstream work waits for missing information. Where does the map send the team first?

Reveal the answer and reasoning

Observe the complete route and the cause of downstream waiting. Test the constraint hypothesis and information readiness before assuming that upstream speed will improve delivery.

Teaching view 2 of 3

Pull signals, replenishment and a levelled release

Distinguish work movement from the signals that authorize withdrawal and replenishment. The labelled map shows Customer consumption, Withdrawal signal, Supermarket, Downstream use, Production signal, Upstream production, Replenish stock, Levelled release, Reliable conditions.
AI-generated system teaching illustration. Follow the steps below, then try the practice question. View full size ↗

Two kanban signals authorize different actions. A withdrawal signal permits movement of the specified item; a production signal permits its replacement. Keep the physical item route visually separate from the information route. Replenishment stock and signal quantities depend on actual demand, replenishment time, variation and policy; this overview prescribes no count. A levelled production release can organize mix and pitch where the process has the necessary capability. It does not mean every arriving order is produced immediately or that changeovers disappear. Quality at source, reliable replenishment and safe changeover improvement make smaller controlled releases more practical. Investigate missing or late signals rather than silently producing extra stock.

Follow the method

  1. Customer consumption: Actual need at the downstream process
  2. Withdrawal signal: Authorize the specified movement
  3. Supermarket: Controlled stock with clear identity
  4. Downstream use: Receive and use the required item
  5. Production signal: Authorize replacement of what was withdrawn
  6. Upstream production: Make the specified replacement
  7. Replenish stock: Restore the authorized item and quantity
  8. Levelled release: Manage mix and pitch where feasible
  9. Reliable conditions: Quality, changeover capability and replenishment time

Read the example carefully

Withdrawal authorizes movement; production kanban authorizes replacement production.

Pitch combines takt with a chosen pack quantity; a levelled mix requires feasibility checks.

Stock and signal quantities need local evidence; the drawing prescribes no universal number.

Try it before revealing the answer

A downstream team needs material and sends a withdrawal signal. Does that signal alone authorize an upstream operator to produce any convenient batch?

Reveal the answer and reasoning

No. The withdrawal signal authorizes the specified movement. Upstream production follows the appropriate production authorization, identity and quantity. Investigate a missing signal instead of substituting an unapproved batch.

Teaching view 3 of 3

Focus the constraint and control work release

Connect constraint evidence, useful capacity, protected commitments and release discipline. The labelled map shows System goal, Constraint evidence, Exploit, Subordinate, Drum, Buffer, Rope, Review and elevate, Reidentify.
AI-generated system teaching illustration. Follow the steps below, then try the practice question. View full size ↗

Begin with the system goal and test what limits it. Protect useful existing capacity before assuming that investment is the first answer. Align upstream release, supporting work and local rules with that decision. In a drum-buffer-rope design, the drum provides the controlling schedule, the buffer protects a commitment and the rope controls release. Buffers do not justify arbitrary excess WIP or unsafe acceleration. Review actual disruption and delivery evidence to improve reliability. If further capacity remains necessary, evaluate elevation with the whole-system effect in view. Reidentify the current constraint after change; the previously slowest operation may no longer deserve the same priority.

Follow the method

  1. System goal: Demand for useful completed work
  2. Constraint evidence: Observe route, states and policies
  3. Exploit: Protect useful existing capability
  4. Subordinate: Align other work and local rules
  5. Drum: Schedule the controlling operation
  6. Buffer: Protect the commitment against disruption
  7. Rope: Release work to the agreed rule
  8. Review and elevate: Add capability if still needed
  9. Reidentify: Avoid inertia after improvement

Read the example carefully

DBR elements serve distinct functions: schedule, protection and release.

Buffer response requires a declared local policy; no universal color thresholds are supplied.

Exploitation and subordination may change the constraint before investment is needed.

Try it before revealing the answer

An upstream machine is idle while the controlling operation is fully supplied. A supervisor wants to release more work to improve local utilization. What should be checked?

Reveal the answer and reasoning

Check the drum schedule, authorized release rule, buffer condition and actual system demand. Extra upstream work may add WIP without improving delivery. Local utilization alone does not establish a valid release.

Build on reliable methods

Sources and further reading

  • Toyota Production System ↗

    TPS purpose, people, jidoka and synchronized Just-in-Time

    Method reference; original OPEX scenario and diagram are synthetic teaching content, not source case results.
  • LEI: Supplement to Learning to See ↗

    FIFO work release and bounded queues in service workflows

    Method reference; original OPEX scenario and diagram are synthetic teaching content, not source case results.
  • LEI: Supermarket ↗

    Predetermined stock locations and consumption-triggered replenishment

    Method reference; original OPEX scenario and diagram are synthetic teaching content, not source case results.
  • LEI: Takt Time ↗

    Demand-paced time; page retrieved initially, subsequent request timed out

    Method reference; original OPEX scenario and diagram are synthetic teaching content, not source case results.
  • TOCICO: Introduction to TOC ↗

    Define system goal/metrics, constraints and rules before intervention; public synopsis only

    Public course synopsis only; no claim to have viewed restricted course content.
  • TOCICO: Process of Ongoing Improvement ↗

    Five focusing steps connect applications and complement other improvement approaches; public synopsis only

    Public course synopsis only; no claim to have viewed restricted course content.
  • LEI: Kanban ↗

    Production and withdrawal signals authorize different actions

    Method reference; original OPEX scenario and diagram are synthetic teaching content, not source case results.
  • LEI: Heijunka Box ↗

    Mix/volume leveling, pitch = takt × pack quantity

    Method reference; original OPEX scenario and diagram are synthetic teaching content, not source case results.
  • LEI: Single Minute Exchange of Die ↗

    Separate internal/external setup then convert and improve

    Method reference; original OPEX scenario and diagram are synthetic teaching content, not source case results.
  • TOCICO: Five Focusing Steps, 2013 ↗

    Identify, exploit, subordinate, elevate, repeat without inertia

    Method reference; original OPEX scenario and diagram are synthetic teaching content, not source case results.
  • Goldratt Japan: Drum Buffer Rope ↗

    Constraint schedule, protection and release control; English synthesis from Japanese primary text

    Method reference; original OPEX scenario and diagram are synthetic teaching content, not source case results.
  • TOCICO: Buffer Management ↗

    Buffer management and recurring red-zone instability; indexed conference text

    Method reference; original OPEX scenario and diagram are synthetic teaching content, not source case results.
Put this lesson to work

Start with the resource for this topic.

Read online without signing in, or take this lesson into your next team conversation.

Topic pack · 18 pages · Reviewed teaching edition.

Explore the full workbooks and facilitator collection
Free learning resources

Resources for a wider learning programme

Read the lessons online or use these PDFs to prepare, practise and review with your team. No sign-in needed.

Facilitators and team leads

Facilitator guide

Case objectives, demonstration plans, debriefs, common mistakes and application checks across all 81 workplace cases and method lessons.

Download Facilitator guide PDF · 166 pages · 65.1 MB
Learners and improvement teams

Learner workbook

Printable case worksheets, blank observation records and five calculation exercises; answers are separate.

Download Learner workbook PDF · 169 pages · 10.7 MB
Learners after practice and facilitators

Answer key and coaching notes

Reasoned sample responses, worked calculations and coaching guidance; fictional examples are clearly labelled.

Download Answer key and coaching notes PDF · 105 pages · 8.5 MB
Practitioners and facilitators seeking detailed worked methods

Method and application reference

The native method mechanisms and worked applications for all 68 detailed lessons, in a separate bookmarked portrait reference.

Download Method and application reference PDF · 141 pages · 10.2 MB
Self-study learners and workshop groups

Illustrated systems atlas

Five illustrated system chapters: 15 Flare concept maps and 26 original workplace teaching cards, with links to all 81 supporting cases and method lessons.

Download Illustrated systems atlas PDF · 69 pages · 55.8 MB
Connect the methods

Practise the methods in this system.

  • Explain how customer need, reliable work and release decisions form one delivery system.
  • Distinguish work movement from the signals that authorize withdrawal and replenishment.
  • Connect constraint evidence, useful capacity, protected commitments and release discipline.
Explore 33 more connected methods
  • TPS: people, quality and synchronized flow

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Muda, mura and muri reinforce each other

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Batch transfer versus one-piece flow

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Production and withdrawal kanban

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Office pull: capacity, blocked work and aging

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Heijunka mix and pitch release

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Standardized work: sequence, takt and standard WIP

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Manual, walking and machine time

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Yamazumi: movable elements and constraints

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • SMED: externalize safely, verify first good output

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Replenishment stock: lead time and uncertainty

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • PFEP to point-of-use replenishment

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • TOC five focusing steps

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Drum-buffer-rope: schedule, protect, release

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Buffer management: priorities and recurring causes

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Throughput versus local utilization

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Critical chain: dependencies, resources and buffers

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Lean and TOC: complementary questions, distinct controls

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Shorten the handoffs

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Give the request a clear next step

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Keep the assembly line ready for the next frame

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • A clearer start for every cut order

    Primary teaching mechanism belongs to lean flow and system performance. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Jidoka and andon: detect, respond, verify restart

    Primary teaching mechanism belongs to quality control and dependable evidence. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Poka-yoke: prevention versus detection

    Primary teaching mechanism belongs to quality control and dependable evidence. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Make tomorrow ready

    Primary teaching mechanism belongs to leadership and daily learning. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Shine and sustain: evidence over time

    Primary teaching mechanism belongs to equipment wellness and oee. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Operator care and specialist maintenance

    Primary teaching mechanism belongs to equipment wellness and oee. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Planned maintenance: criticality to verified return

    Primary teaching mechanism belongs to equipment wellness and oee. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • OEE loss waterfall with denominator discipline

    Primary teaching mechanism belongs to equipment wellness and oee. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Quality maintenance: control conditions, not just inspect output

    Primary teaching mechanism belongs to equipment wellness and oee. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Find it. Use it. Reset it.

    Primary teaching mechanism belongs to equipment wellness and oee. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • A tool room ready for the next job

    Primary teaching mechanism belongs to equipment wellness and oee. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Give the press area a clear reset

    Primary teaching mechanism belongs to equipment wellness and oee. Supporting links identify application dependencies; they do not make the methods interchangeable.

Explore all chapters and detailed lessons →

Apply the learning to your own work

Ask OPEX Guide how to apply this learning to your situation. Describe the expected condition, the gap and the evidence you have. Review its suggestions with the people doing the work before deciding on a change.

Explore your question with OPEX Guide →