Stale Cards First: Using Task Age to Find Stuck Work Early
Most task boards show what work exists and where it sits, but they rarely show how long it has been sitting there. A card that moved into the In Progress column three weeks ago looks the same as one that moved yesterday unless someone reads the history. Card age is a simple signal that can reveal stalled work long before a deadline makes the stall obvious. This article covers a method for using age as a triage question, the reasoning behind it, and a short checklist a busy team can run without adding any new tools or ceremony.
Why age is a different signal than status
A column tells you the stage a task is in. Age tells you how long it has been in that stage, and that duration is often more informative than the stage itself. A card in Review for two days is normal in many teams. The same card in Review for twelve days suggests a question has gone unanswered, a reviewer is overloaded, or the work is waiting on a decision nobody has named.
Age matters most when a task has no visible blocker. Teams tend to mark a card blocked only when someone knows what is blocking it. Many stalls happen quietly: the owner is waiting for a reply, the reviewer assumed someone else would pick it up, or the scope shifted and nobody updated the card. Age surfaces these cases because the card simply stops moving while the calendar keeps going.
A triage method built on age bands
Rather than reviewing every card every day, group active cards into rough age bands. A useful starting split is cards that moved within the last two working days, cards that have been in their current column for three to six days, and cards that have been there for more than a week. The exact thresholds should match your team's normal cycle time. A team that ships one feature per month needs wider bands than a team that closes support requests within a day.
The point of the bands is to decide where attention goes. Recent cards rarely need intervention. Cards in the middle band deserve a one-line check: is the next step clear, and who owns it? Cards in the oldest band deserve a direct conversation, because their age almost always means something is wrong with the work itself, its ownership, or its scope.
Questions to ask when a card is old
When a card crosses into the oldest band, resist the urge to simply ask for an update. A status request usually produces a reassuring answer that changes nothing. Instead, ask questions that force a concrete next action. What is the single next step? Who is responsible for taking it? What would need to be true for the card to move this week? If the answer to the last question is unclear, the card may be too large or too vague to finish, and splitting it is often the real fix.
It also helps to ask whether the card still matters. Age sometimes reveals work that was overtaken by events. If the original reason for the task has changed, the honest move is to close it, park it with a stated reason, or rewrite it so it reflects current goals. A stale card that everyone quietly ignores is worse than an explicitly dropped one, because it keeps consuming attention in standups and reviews.
A short checklist for a weekly age review
A weekly age review can fit into a fifteen-minute slot. Start by scanning each active column and noting any card older than your team's threshold for that stage. Then, for each flagged card, answer three things in writing on the card itself: the next concrete action, the named owner, and the date by which that action should happen. If a card cannot produce those three answers, mark it for splitting or closure.
Keep the review about the work rather than the people. A card that has been waiting on a reviewer for nine days is a signal about the review step, and the useful response is to change how reviews get assigned, not to question someone's effort. Over several weeks, patterns appear: certain columns accumulate age, certain owners carry long-running cards, or certain request types always stall. Those patterns point to structural fixes, such as adding an explicit review owner or limiting how many cards can sit in one column at once.
Finally, be honest about what age cannot tell you. A long-running card may be deliberately paused because the team chose to wait for a dependency, and that is a legitimate decision. The goal is not to shrink every age number to zero but to make sure every old card has a reason someone can state out loud. Used this way, card age turns a passive board into a prompt for the conversations that keep busy teams moving.