Aging Work in Progress: The Report That Replaces Standup

Introduction

Every flow metric in common use has the same limitation: it describes work that is already finished. Cycle time, throughput, flow efficiency, the whole set. They are excellent for telling you whether last month was better than the month before, and completely useless for telling you what to do before lunch.

There is one exception, it is barely covered anywhere, and it is the most actionable number on a board. Work item age asks a different question: not how long finished items took, but how long the unfinished ones have already been open.

That single change of tense is what makes it useful. You cannot do anything about an item that took four weeks last March. You can do something about the one that has been open for nine days and nobody has mentioned.

What Is Work Item Age?

Work item age is the elapsed time since an item started, measured on items that have not finished yet. An item started nine days ago and still in progress has an age of nine days. When it finishes, its age becomes its cycle time and it stops being an aging item.

The metric is per item, not an average. An average age tells you almost nothing; the list of items sorted by age, longest first, tells you what to do today.

Why It Beats Cycle Time for Daily Decisions

Cycle time is a lagging indicator, and lagging indicators cannot be managed. By the time an item shows up in your cycle time distribution as a forty-day outlier, the forty days have been spent. The report tells you that something went wrong a month ago and gives you no lever.

Age is a leading indicator of the same thing. On day nine of what will eventually be a forty-day item, the item is already visibly abnormal, and thirty-one of those days have not happened yet. Nothing else on the flow metrics guide gives you that.

The comparison you need to make it meaningful comes from your own history. Pull the 85th percentile of your cycle time over the last quarter, and call that your line. If most items finish within eleven days, then an item that has been open for nine is approaching abnormal and one open for fourteen already is. No judgement required, no asking anyone whether they are on track.

Running a Standup From the Aging List

The standard standup walks the people: three questions each, round the circle, fifteen minutes and a lot of status narration for an audience that mostly does not need it. Its structural problem is that it surfaces what people did rather than what is stuck, and the person whose item has been quietly rotting for nine days is often the least likely to raise it.

Walk the aging list instead, longest-open first, and stop at the first three.

This inverts the meeting in a useful way. Items that are moving normally are never discussed, which is correct, because there is nothing to decide about them. The meeting is exactly as long as the number of genuinely stuck things, which on a good week is zero and the standup takes ninety seconds. Nobody has to perform productivity, and the oldest item cannot hide.

It also removes the most common objection to dropping standups altogether, which is that problems would go unnoticed. They go unnoticed with standups too; the aging list is what actually catches them. See the meeting tax and the weekly review system.

The Three Actions for an Aging Item

When an item crosses the line, there are exactly three legitimate outcomes. Naming them in advance is what stops the conversation from becoming a status update.

Unblock it

Something external is holding it: a review, a decision, a client response, an environment. The action is on someone other than the assignee, and the point of surfacing it is to move that action. Most aging items are this, and most of them have been waiting on something that would take ten minutes to resolve if anyone asked.

Split it

The item is too big. It was always too big, and it has been in progress for two weeks because it is really five items wearing a trenchcoat. Splitting it does not make the work smaller, but it makes progress visible and it gets part of the value shipped. See breaking work into tasks.

Kill it

The least used and often the right one. The item has aged because nobody actually wants it enough to finish it, which is information. An item that has been open for three weeks with no external blocker is telling you its true priority, whatever the priority field says. Closing it costs nothing and frees a WIP slot. See WIP limits.

The one illegitimate outcome is "keep going". If an item crosses the line and the answer is that it is fine and will be done soon, either the line is wrong or the answer is. Both happen; neither is resolved by moving on.

How FlowBoard Shows This

FlowBoard tracks work item age on in-progress items and surfaces the ones that have been open longest, which is the view this article is about. Because it is derived from status transitions, there is nothing to configure and no way for an item to look fresher than it is.

The related view worth pairing with it is the personal queue, which answers the individual version of the same question. See a personal task queue across projects.

What to Do This Week

Sort your in-progress items by how long they have been open and look at the top three. You will almost certainly find at least one that nobody has thought about in a week, and it will almost certainly be blocked on something small.

Do that every morning for two weeks in place of standup. Then read cycle time vs lead time to set your line properly, and WIP limits, which is the structural fix for a board that keeps producing aging items.