Cycle time calculator.How long a card takes once it is started.
Count the cards currently in progress and how many the team finishes in a week. Little's Law turns that into the average time a card spends between start and done, and shows what has to change to hit a target.
Your numbers
2 weeks on the calendar. With 10 cards in progress and 5 finishing a week, each card waits or is worked on for about 10 days.
Cycle time from two numbers you already have
Cycle time is how long a piece of work takes from the moment someone starts it to the moment it is done. Measuring it directly means timestamping every card, which is worth doing, but Little's Law gives the average from two counts anyone can take today: how many cards are in progress and how many finish per week.
The identity is cycle time = WIP ÷ throughput. Ten cards in progress and five finishing a week means each card takes two weeks on average, whether or not it feels that way from the inside.
What the number tells you
If it is longer than stakeholders expect, the board is carrying too much. Most of that time is waiting, not working: cards sit in review, blocked, or parked behind something more urgent. The fastest fix is to stop starting and finish what is open.
What it does not tell you
The average hides the spread. Two teams with a ten-day average can have very different worst cases. Once the average is under control, look at the 85th percentile of individual card times, which is what the throughput forecast tool is built around.
Flow metric questions
What is Little’s Law?
For any stable process, average work in progress equals throughput multiplied by average cycle time. It holds regardless of what the work is, as long as the measurements cover the same period and use the same units.
The WIP limit and cycle time calculators are rearrangements of that identity.
Do I count blocked and waiting cards as work in progress?
Yes. Anything that has been started and is not yet done is in progress from the customer’s point of view, and it is the waiting time that inflates cycle time. Counting only cards someone is actively typing on gives a flattering but wrong answer.
How many weeks of data do I need?
Six to eight weeks is a reasonable minimum for an average. Fewer and a single good or bad week dominates. If the team or the way work is sliced changed recently, start counting from the change.
Where do I get throughput from Kanera?
The Work Done view lists completed cards by date for a board or a whole workspace. Table view can group by completion week and export the counts to Excel.
Measure it instead of
estimating it.
Kanera keeps a Work Done history and card-level activity, so throughput and cycle time come from what actually happened on the board.
No card required, 30-day Pro trial, free plan available after it