Module 10 · Lesson 13 of 18

WIP and lead-time reduction

← Back to moduleBack to academy

Learning objectives

  • Apply Little's Law to link WIP, throughput and lead time.
  • Diagnose queue, batch and information delays that inflate WIP.
  • Cut WIP without starving downstream stations.

Problem and CTQ

Excess WIP hides defects, consumes cash and space, and extends lead time. Little's Law: WIP = throughput × lead time (with a defined boundary and status).

DMAIC path

  • Define system boundary and status (in-line, in-queue, in-repair).
  • Count WIP with timestamps and map queues, batch/release rules, imbalance, rework and information delays.
  • Quantify Process Cycle Efficiency (value-add time / total lead time).

Improvement choices

  • Smaller transfer batches, pull/WIP caps, pacemaker scheduling.
  • Flow cells, constraint management, FIFO lanes.
  • Rapid abnormal response so pulls are honoured.

Control plan

  • WIP units and WIP days, throughput, lead time, PCE, aging, starvation/blocking, FPY and OTD.

Garment-factory example

A sewing module holds 2,300 WIP against 900 units/day throughput = 2.55 days lead time. A WIP cap of 1,200 and 20-piece bundles cut lead time to 1.33 days with FPY unchanged.

Common mistakes

  • Cutting buffers abruptly without process stability.
  • Shifting inventory outside the measured boundary and calling it a WIP reduction.

Knowledge check

Pick one answer per question. Explanations appear after you submit.

  1. 1. For a stable process, halving WIP while keeping throughput constant:

  2. 2. A WIP reduction that only moves inventory to the warehouse is:

Author: Sanjeewa Dehiwalage · Last reviewed: 2026-07-21

Stay in touch

New chapters, delivered quietly.

A short note when a new story, reflection or milestone is added. No noise, no spam — unsubscribe with a single click.