Project management · Practical guide

Kanban Metrics: WIP, Throughput, Cycle Time and Work Item Age

By My First Task editorial team

Updated

The short answer

Four useful Kanban flow measures are work in progress, throughput, cycle time and work item age. Together they show how much work is active, how much finishes, how long finished work took and how long unfinished work has been active.

How to approach the work

Define the workflow boundaries before measuring anything. Throughput counts finished items per unit of time; cycle time measures started-to-finished elapsed time; age measures started-to-now time for unfinished work. Counts are most useful when work items are reasonably comparable. Metrics should prompt a discussion about flow and bottlenecks, not become targets that encourage splitting or closing tasks just to improve a number.

A practical sequence

  1. Define exactly when an item starts and finishes.
  2. Count active items for work in progress.
  3. Count completed items in a stated period for throughput.
  4. Measure elapsed time for completed items as cycle time.
  5. Review the oldest unfinished items and their blockers.
  6. Use several measures together before changing a workflow policy.

Illustrative scenario · not customer research

Worked example

A workflow finishes fifteen items over five working days: observed throughput is three items per working day. The completed items have sixty combined calendar cycle-days, giving a mean of four calendar days. Those units should not be mixed uncritically in Little's Law: use a common time basis before applying it. Meanwhile, an unfinished task that started seven days ago may deserve review even when the average completed-item cycle time looks healthy.

Common mistakes to avoid

  • Mixing calendar-day durations with working-day throughput.
  • Treating throughput as a measure of delivered value.
  • Ignoring old unfinished items because completed work looks fast.

Try the method with your own inputs

Questions answered

What is work item age?
It is elapsed time since an unfinished item crossed the agreed start boundary. Unlike cycle time, it concerns work that has not finished yet.
Can throughput improve while value falls?
Yes. Finishing many low-value or artificially split items can raise throughput without helping the goal. Review outcomes and work quality alongside counts.
Which metric is most important?
Use the metric that answers the current question, then cross-check the others. A single number cannot explain an entire workflow.

Apply it in a shared workspace

Keep the agreed owner, completion criteria and important decisions with the work. Explore the relevant My First Task feature.

Research context is available in our source library. The worked example above is an editorial illustration.

Continue learning

Method references

Turn the plan into shared work

Give each next action an owner, a completion condition and a realistic date. My First Task brings tasks, boards, project workflows and issue tracking into one workspace.