Work in Progress (WIP)
Work in progress (WIP) is every unit that has started but is not yet finished — parts on the line, jobs in a queue, and tickets waiting between steps. In a Lean system the goal is to keep WIP low and visible, because unfinished work ties up cash, hides problems, and stretches lead time.
Little’s Law states the relationship clearly: average lead time equals WIP divided by throughput.
What counts as WIP
Count any work that has left raw-material stores and has not reached finished-goods or the customer. That includes:
- Parts sitting in a basket between machines.
- A batch that is half stamped and waiting for the next setup.
- Repair loops, rework cages, and “hold for quality” racks — they are still WIP.
- In services: tickets in a backlog after intake, claims waiting on a review, or patients waiting between process steps.
Raw material that has not been released, and finished goods already transferred to the warehouse, are inventory too, but they are usually tracked separately from shop-floor WIP.
Why high WIP hurts
- Lead time grows. Little’s Law is not a slogan. If Northriver’s assemble cell completes 40 hinge sets per day and 400 sets are sitting in queues, average lead time is ten days, even if each set is only touched for a few minutes. See touch time for the difference between work time and waiting time.
- Cash is tied up. Every unfinished part is purchased material and labor that cannot be invoiced yet.
- Quality problems hide. A bad stamp may sit for days before assembly finds it, so the process keeps making the same defect.
- Space and handling grow. Piles need racks, forklift moves, and counts — a form of waste.
- Priority fights start. When everything is in process, everything is urgent, and expedites become the unofficial scheduling system.
How to lower WIP without starving the line
The aim is a cap that is low enough to surface problems and high enough that stations are not idle from ordinary variation. Practical moves:
- Make WIP visible. Mark floor squares, use labeled totes, or post a simple board so anyone can see when a queue is over its cap. That is the same idea as a visual factory.
- Pull, don’t push. A downstream station withdraws work only when it has an empty slot. Kanban or a two-bin system is a common way to enforce the cap. Just-in-time is the broader policy of producing only what the next step needs.
- Reduce batch size and changeover. Large batches are a WIP decision dressed up as efficiency. Shorter setups let you run smaller lots.
- Balance the line and fix the constraint. WIP collects in front of the slowest step. Improving that step, or protecting it with a small, intentional buffer, is more useful than adding unofficial piles everywhere.
- Stop starting, start finishing. In office work, a WIP limit on “active” tickets (a Kanban column limit) often cuts lead time faster than adding people.
A value-stream map is the usual place to see WIP count, wait time, and process time on one picture. Basic Lean Six Sigma metrics then track WIP, throughput, and lead time as the cap changes.
A quick Northriver example
Suppose stamp, assemble, and pack can each finish 40 hinge sets a day, but unofficial racks hold 200 sets before assembly. Throughput cannot exceed 40 a day, so Little’s Law says those 200 sets alone add five days of lead time. If the team caps the rack at 40 sets and keeps throughput at 40 a day, those five days drop to one — without changing the machining time of a hinge.
Exam notes
IASSC and ASQ questions often ask you to recognize WIP as inventory between process steps, to name space, cash, obsolescence, and hidden defects as reasons to reduce it, and to apply Little’s Law (lead time = WIP ÷ throughput) with consistent units. Do not confuse WIP with finished-goods inventory or with cycle time.
Frequently asked questions
Is WIP the same as inventory?
WIP is a type of inventory: work that has started and is not finished. Inventory also includes raw material and finished goods. Lean treats all three as something to keep under control, but WIP is the pile that most directly stretches shop-floor lead time.
Does cutting WIP always raise throughput?
No. Throughput is limited by the constraint. Cutting WIP shortens lead time and exposes problems. If you cut the buffer in front of the constraint too far, throughput can fall. Set the cap with the constraint in mind.
How is WIP different from touch time?
Touch time is how long a unit is actually being worked on. WIP is how many units are in the system. High WIP usually means most of a unit’s lead time is waiting, not touching.
See also: touch time, value-stream mapping, Lean Six Sigma metrics, and the eight wastes.
Related line-balancing and flow topics in this guide: work in queue, the theory of constraints, Yamazumi charts, and production line balancing.
Related guides
Last updated: · Published by Lean Six Sigma Training Guide (sixsigmatrainingfree.com) · How this guide is written