How to Measure Work-in-Progress (WIP) the Right Way
Work-in-Progress (WIP) is the number of work items you’ve started but haven’t finished yet. Measuring WIP the right way makes flow visible, exposes bottlenecks early, and helps you finish more work with less stress.
What WIP is (simple definition)
WIP = anything started that is not done.
In practice, WIP includes tasks in “In Progress,” “Review,” “Waiting,” and any other state where work is open. The key is consistency: define what counts as “started” and what counts as “done” for your team.
Why measuring WIP matters
High WIP creates hidden costs:
- More context switching
- More waiting (queues grow)
- More rework (handoffs and partial work create errors)
- Longer lead times (customers wait longer)
Low, controlled WIP improves flow, predictability, and throughput.
The #1 mistake: counting “busyness” instead of WIP
Teams often measure utilization (how busy people are) and assume productivity improves. But WIP is about the system, not individual activity. You can be 100% busy and still deliver slowly if too many items are open at once.
Step 1: Choose your unit of WIP
Decide what you’re counting:
- Cards/tickets (best for most teams)
- Requests (service / ops teams)
- Deliverables (projects broken into outcomes)
Tip: If items vary wildly in size, WIP counts can mislead. Break large work into smaller items so WIP is meaningful.
Step 2: Define “started” and “done” (so your measurement is consistent)
Your WIP number is only useful if the definition is stable. Use simple rules like:
- Started: the item enters “In Progress” (someone is actively working on it)
- Done: the item meets the Definition of Done and exits the workflow
If “Review” is a major waiting area, include it in WIP. If “Blocked” exists, include it in WIP. WIP is not “work time”—it’s open work.
Step 3: Measure WIP in three practical ways
Method A: Snapshot WIP (fast and simple)
At a consistent time (daily or weekly), count how many items are currently open across your workflow. This is the easiest method for teams starting out.
- Daily snapshot: best if work changes quickly
- Weekly snapshot: best if work moves slower
Use this when you want a quick signal: is WIP rising, stable, or dropping?
Method B: Average WIP over time (more accurate)
Instead of one snapshot, measure WIP at the same time each day and compute the average for the week. This smooths out spikes and gives a better baseline.
Method C: WIP by stage (the most actionable)
Total WIP is useful, but the best insights come from stage-level WIP:
- WIP in In Progress
- WIP in Review
- WIP in Waiting/Blocked
Stage-level WIP tells you where work is getting stuck (and where to fix the system).
Step 4: Use a CFD to visualize WIP trends
A cumulative flow diagram (CFD) is one of the best tools for understanding WIP, flow stability, and bottlenecks. It shows how work accumulates in each stage over time.
If you’re new to CFDs, use How to Use CFD Charts (Cumulative Flow Diagram) to learn what to look for and how to interpret widening bands (a sign of growing queues and rising WIP).
Step 5: Pair WIP with the right metrics (not a dashboard of noise)
WIP becomes powerful when you pair it with a few flow metrics that explain what’s happening. A clean set to start with:
- WIP: how much work is open
- Throughput: how many items are finished per time period
- Lead time: how long it takes to deliver an item
If you want to avoid tracking metrics that don’t help decisions, use Kanban Metrics That Actually Matter (And Which Don’t).
Step 6: Use flow efficiency to see how much time is “real work” vs waiting
High WIP usually means more waiting. Flow efficiency helps you quantify it by showing how much time is active work versus time sitting in queues.
To calculate and interpret it in plain language, use Flow Efficiency Formula (Explained So Anyone Can Use It).
How to know if your WIP is “too high”
There’s no universal perfect number, but there are clear warning signs:
- Most items spend more time waiting than being worked
- Review or approvals are constantly overloaded
- People start work faster than the team finishes work
- Lead time is unpredictable (huge variation)
A practical rule: if WIP grows week over week, your system is starting more work than it can complete.
What to do after you measure WIP
Measurement is only useful if it drives action. Once you see your WIP patterns:
- Reduce active work: stop starting new work until the team finishes existing work
- Fix the bottleneck stage: wherever WIP piles up is your first target
- Improve policies: tighten “ready” criteria, define review SLAs, standardize handoffs
- Protect focus: fewer simultaneous items means faster completion
WIP measurement supports Lean transformation (when used the right way)
WIP is one of the clearest “system health” indicators in Lean. But it only works when teams treat it as a learning tool, not a weapon.
To understand the mindset difference between surface-level tools and real Lean adoption, read Lean Culture vs Lean Tools: What Actually Drives Change. If you want a broader Lean foundation, use Kaizen vs Lean: What’s the Difference? and The Complete Guide to Lean Transformation.
