The four numbers
- Lead time – from when a card is created (requested) to when it is done.
- Cycle time – from when work actually starts to when it is done.
- Throughput – how many cards are finished per week.
- Work in progress – how many cards are started but not finished right now.
Teams define the exact start and end points slightly differently. Pick a definition and stick to it; consistency matters more than precision.
How they connect
Little’s Law, from queueing theory, links them: average cycle time = average WIP ÷ average throughput. If you finish 5 cards a week and have 10 in progress, cards take about 2 weeks on average. Want faster? Either finish more per week (hard) or have less in progress (easy, and usually also raises throughput because there is less switching).
Measuring without a spreadsheet
- Throughput: filter for cards closed in the last week. Count them. Do this each Friday.
- WIP: count the cards in your active columns. CBSE.CLUB shows the count on each column.
- Cycle time: open a few recently closed cards; their history shows when they moved into progress and when they closed.
Write the three numbers in a recurring card or a team note each week. After a month you will see trends.
Cumulative flow diagrams
A cumulative flow diagram plots how many cards were in each stage over time. Widening bands mean work is piling up. They are useful for larger teams; small teams can usually see the same thing by glancing at the board.
Metrics to avoid
- Cards closed per person. It encourages splitting work into tiny cards and discourages helping others.
- Velocity across teams. Estimates are not comparable between teams.
- Utilisation. Keeping everyone 100% busy creates queues. Some slack is what makes flow possible.
Using metrics well
Look at them together, as a team, as a starting point for conversation: “Cycle time went up. What happened?” Never as a target for individuals. The moment a measure becomes a target, people optimise the number instead of the work.