A weekly completion report can look healthy while one important task sits unfinished for weeks. The completed items are visible in the average; the stalled item has not yet entered that calculation.
Work item age brings that unfinished work into the conversation. It measures elapsed time from the agreed start of an item to the current date. Cycle time, by contrast, requires a finish.
The Kanban Guide defines these as separate flow metrics and makes their meaning depend on the team’s definition of when work starts and finishes.
Use a consistent starting point
Suppose an item entered active work on Monday and is still open on Friday. Its age concerns the time since Monday, even if it moved from drafting to review on Wednesday. Resetting the clock at every column would answer a different question.
Agree whether the team’s display uses calendar days or another clearly defined convention. Keep stage-level waiting time separately if it helps; do not silently substitute it for the age of the whole item.
Ask what the age is telling you
An old item is a reason to investigate, not proof that its owner is working slowly. It may be waiting for an external answer, missing acceptance criteria, or competing with too many newly started tasks.
At a short review, pick an ageing item and ask: what prevents its next useful step, who can remove that obstacle, and when will we check again? Compare it with genuinely comparable work rather than treating every task as the same size.
A team might discover that three requests all await the same approval. Helping with that shared constraint may be more useful than asking each assignee for a faster update.
Keep the measure tied to a decision. A colourful ageing chart that nobody acts on adds reporting work; a consistent age signal can draw attention to a delay while there is still time to change its outcome.