Every ticket on your board has an age. Almost no team tracks it, and it is usually the single most useful number you are ignoring.
Here is the pattern I have watched play out for two decades. A stand-up runs its usual lap. Six people say what they did yesterday and what they will do today. Everyone sounds busy. The board looks healthy because cards are moving. Two weeks later the release slips, and when you finally trace the delay back, it lands on one card that entered “In Progress” eleven days earlier and quietly sat there while the daily conversation flowed right past it every single morning.
That card was never the topic of a stand-up. Nobody lied. Nobody slacked. The meeting simply asked the wrong question.
What “work item age” actually measures
Work item age is the elapsed time between when a piece of work started and right now. If a card moved into “In Progress” on the first of the month and today is the tenth, its age is ten days. Every open item has one, and it grows every day until the item is finished. The definition is boring; the implication is not.
Most teams measure cycle time (how long finished work took) and throughput (how many items completed in a period). Those numbers are real and worth having. They are also autopsies. They tell you about work that is already done, which means by the time a bad cycle time shows up in your report, the damage is spent. You cannot change the past.
Work item age is different because it deals with the present. It is the only common flow metric that describes work still in your hands, work you can still act on. The team at 55 Degrees, which builds tooling around these metrics, puts it bluntly: if you can only measure and manage one thing, make it work item age. It is a leading indicator sitting in a field of lagging ones.
Why “what are you working on” hides the problem
The standard stand-up prompt is some version of “what are you working on.” It surfaces activity. What it does not surface is stalled work, because a stalled card usually has someone’s name on it and that person can honestly say they are “still working on it” for the fifth day running without anyone registering that five days have passed.
Aging work rarely announces itself. It bounces between a developer, QA, and product, technically owned at every step, never actually finished. Requirements turn out to be fuzzier than they looked. A dependency slips. Someone gets pulled onto an incident. Each individual delay is defensible. Stacked together across a card that nobody is watching by elapsed time, they turn a two-day task into a two-week one, and the person reporting on it each morning is often the last to notice because they are inside it.
There is a real cost to that drift beyond the calendar. A card that lingers loses context. The person who wrote the requirement has moved on mentally. Assumptions go stale. The longer something sits, the more likely it comes back with bugs and rework attached, which is its own delivery tax that most teams never put a number on. Work that sits too long does not fix itself. It rots.
The better question is “what’s not moving”
The fix is not a new tool. It is a different question and thirty seconds of preparation.
Before your next stand-up, sort the board by age instead of by column. Put the oldest in-progress item at the top. Then open the meeting with “what’s not moving” rather than “what’s everyone doing.” Walk the board oldest-first. The card that has been open longest gets the conversation, not the card whose owner happens to be the most articulate that morning.
This inverts the usual dynamic. A normal stand-up rewards visible activity, which is exactly the work least in need of attention. Walking oldest-first forces the meeting onto the items actually at risk. You will find that the oldest card is almost never the one people volunteer to talk about, which is the whole point.
You can make this sharper with a threshold. Decide what “too old” means for your team. If most of your work finishes in five days or less, then anything sitting at four days is amber and anything at five-plus is red. Some teams color the board this way so the aging items are visually loud. In flow language this threshold is a service level expectation: a promise about how long work should take, which then gives “old” a definition instead of a vibe. When a card crosses it, that is not a status update, that is a trigger to intervene: swarm it, split it, unblock it, or make an explicit decision to kill it.
Old work is also risky work
There is a second reason to hunt aging items, and it comes from a completely different body of research. The DORA program, the multi-year study behind the book Accelerate by Nicole Forsgren, Jez Humble, and Gene Kim, found that the highest-performing engineering organizations ship in small batches, frequently, and that small batch size correlates with both faster delivery and lower change failure rates. Elite teams deploy on demand and keep change failure rates in the 0 to 15 percent range.
A card that has aged is, by definition, a bigger batch than it should be. It has accumulated more changes, more assumptions, and more surface area than the small, fast increment DORA says is safest. So the oldest item on your board is not just the slowest, it is frequently the riskiest thing you are about to ship. Age and risk travel together. Managing one manages the other.
This connects to why chronic multitasking quietly destroys delivery: the more items a team keeps in flight at once, the older every one of them gets, because attention is finite and gets sliced thinner across every open card. Limiting how much work is open at any moment is the same lever as keeping work young. They are two views of the same discipline.
What this costs to run
Close to nothing, which is the argument for it.
Stand-ups are already expensive. One widely cited compilation of meeting research found that only about 12 percent of meetings finish inside their planned fifteen minutes, that the average stand-up drifts to double its intended length, and that people lose roughly twenty-three minutes of focus getting back to real work afterward. You are paying for this meeting every day whether or not it surfaces anything useful. Changing the sort order and the opening question costs no additional time. It just redirects the time you are already spending toward the work that is actually in trouble.
I ran an operations queue for years where the daily review had quietly become a recitation of the newest, most exciting tickets. The genuinely stuck items, the ones a customer was waiting on, were old and boring and never came up. The day we started reading the queue oldest-first, three tickets that had been open for over a week surfaced in the first ninety seconds. Two of them were blocked on a decision nobody had made because nobody had noticed a decision was needed. That is the failure mode work item age catches. Not laziness. Invisibility.
Try it this week
Pick your busiest team’s board. Before the next stand-up, sort by how long each in-progress item has been open. Read the top three out loud and ask, for each one, what would have to happen for it to finish today. Do that for a week and watch which cards keep reappearing at the top. Those are your real constraints, and they were on the board the whole time. You just were not looking at the board that way.
Your dashboard already knows the oldest ticket. The only question is whether your stand-up does.
Related reading: why the 90 percent done trap swallows delivery timelines and how to run a delivery confidence check before risks turn into missed dates.