Kanban metrics are the small set of numbers that tell you whether work is actually flowing through your board or just sitting on it. The four that matter are work in progress (how many things are active), cycle time (how long an active item takes), throughput (how many items finish per week), and work item age (how long something has been sitting unfinished). You don't need all four on day one, and you don't need a dashboard for most of them.
Most explanations of kanban metrics are written for a team already running a reporting tool, and they hand you all four metrics plus a formula in one list. That's the wrong order to learn them in. This post covers what each metric means, which one to start with on a plain board, and where a chart genuinely earns its place.
What are the four core kanban metrics?
Work in progress (WIP) is a count: how many cards are currently active, meaning started but not finished. Backlog and Done don't count. If your board has a WIP limit on a column, this is the number that limit caps. Cycle time is how long a single card spends active, from the moment it enters "Doing" (or whatever your first active column is called) to the moment it's finished. It's measured in the clock, so a card that sits untouched for two days still has that time counted. Throughput is a rate: how many cards finish per week (or per day, if your team ships that often). It answers "how much are we actually completing," which is a different question from how busy the board looks. Work item age applies only to cards still in progress: how long has this one been active so far. It becomes cycle time the moment the card finishes. Of the four, this is the one worth checking most often, because it's the only one that can warn you about a stuck card before it's a finished (or abandoned) one.Which metric should you track first?
Start with work item age. Once a week, scan every card in an active column and ask how long it's been there. A card that's older than the rest is either genuinely large or quietly stuck, and both are worth a conversation before the card finishes.
Add cycle time next, once age has become a habit. You'll already have the start dates from tracking age; cycle time is just what those numbers become once a card is done. A useful early question is whether your cycle times cluster together or spread wide. A wide spread usually means some cards are a different kind of work wearing the same card shape, and splitting that work out helps more than any chart will.
Throughput comes third, and only needs a weekly count: how many cards moved to Done this week versus last week. Add work in progress last, as a limit rather than a report. It's the one metric that changes team behavior directly, so it's worth waiting until the other three have told you where the board actually gets stuck. Our guide to WIP limits covers how to pick a starting number once you're at that point. For a small team's whole board, not just this one habit, see our overview of simple project management.
Do you need a cumulative flow diagram?
A cumulative flow diagram (CFD) is a stacked area chart, one band per column, showing how many cards sat in each stage of the workflow on any given day. Reading one is a genuine skill: a widening "in progress" band means work is arriving faster than it's finishing, and the vertical distance between two bands on a given day is roughly your work in progress for that stage.
The honest answer is that most small teams don't need one. A CFD earns its place once you have enough throughput and enough history that eyeballing the board stops being reliable, usually somewhere past ten or so cards moving through per week. Below that, the same information is visible by looking at the board and asking which column has more cards in it than last Monday. If you do reach for a CFD, Wikipedia's overview is a clear, vendor-neutral explanation of how to read the bands.
What is Little's Law in kanban?
Little's Law states the relationship between the three flow metrics: cycle time equals work in progress divided by throughput. Push more work in progress through the same throughput and cycle time goes up. Raise throughput without raising WIP and cycle time comes down. It's less a formula to calculate by hand and more a reminder of why WIP limits work: capping WIP is the one lever a team can pull directly, and the other two follow from it. The formal version comes from queueing theory, not kanban specifically, which is why it applies to any process with items entering and leaving a queue.
How do you track kanban metrics without a dashboard?
For a solo board or a small team, all four numbers exist without any add-on:
- Work item age: look at each active card and check when it was moved into the column. EasyKanban shows the move date on every card, so this is a glance, not a report.
- Cycle time: once a card reaches Done, subtract the date it started from the date it finished.
- Throughput: count how many cards reached Done this week. A five-column board with a Done column makes this a count, not a query.
- Work in progress: count what's in your active columns right now. This is also the number a WIP limit caps, once you set one.
None of this needs a spreadsheet formula or a paid reporting tier. It needs a weekly five-minute look at the board, which is the same habit kanban for developers recommends for sprint retros, applied to a board of any kind.
Can an AI assistant track these metrics for you?
If your board is connected through EasyKanban's MCP server, an assistant like Claude can already answer "what's overdue" or "what's still in progress" by reading the board directly, without you opening a dashboard. The same question extended to "how many cards did we finish this week" or "which card has been sitting the longest" is the same kind of read, just counted differently. It won't replace deciding what a wide cycle-time spread means, but it removes the five minutes of manually counting cards that the section above describes.
Frequently asked questions
What is a good cycle time for a kanban card?
There's no universal number. What matters is consistency: track your own cycle times for a few weeks and use that range as your baseline. A card taking noticeably longer than your own recent average is the signal worth acting on, not a comparison to another team's number.
What is the difference between cycle time and lead time?
Cycle time starts when work actually begins on a card. Lead time starts earlier, when the request or idea first entered the system, including any time it waited in a backlog. Lead time tells the requester how long they waited; cycle time tells the team how long active work took.
How often should you check kanban metrics?
Work item age is worth a quick look weekly, since it catches a stuck card early. Cycle time and throughput are more useful reviewed every two to four weeks, since a single week of data is usually too noisy to act on.
Do I need special software to track kanban metrics?
No, for the first three metrics. Work item age, cycle time, and throughput can all be read directly off a board that shows move dates, which is a count and a subtraction, not a report. A cumulative flow diagram is the one exception, since it needs historical daily snapshots to draw.
What's the single most useful kanban metric to start with?
Work item age. It's the only one of the four that can flag a problem while the card is still in progress, rather than after it's already finished or been abandoned.
Related reading
Most boards don't need a metrics dashboard to start. They need one number checked once a week, and work item age is the one to pick.