Card Aging: Using Task Board Age Signals to Catch Work Before It Stalls
Most task boards show where work is, but very few show how long it has been there. A card in the In Progress column tells you its status; it does not tell you whether it arrived there yesterday or three weeks ago. For founders and busy teams, that missing dimension is often where problems hide. Card aging is the practice of paying attention to how long each item has sat in its current state, and treating that duration as a signal worth reviewing. This article explains how to think about card age, what questions to ask when a card looks old, and how to build a short routine that surfaces stalled work before a launch date or planning deadline forces the issue.
Why time-in-column matters more than status alone
A status column answers a narrow question: what stage is this work in? Time-in-column answers a different one: is this work still moving? Two cards can sit in the same column with identical labels and very different realities. One may have been touched daily and is simply large. The other may have been untouched since a planning meeting and has quietly stopped being anyone's real priority. Without any sense of duration, both look equally healthy.
Aging is useful because stalled work rarely announces itself. People mean to come back to a task, a dependency arrives late, or a question goes unanswered in a chat thread nobody checks. Each of these produces silence rather than an obvious failure. A card that has not moved in a week is often the first physical trace of that silence, which is why a simple age check can catch problems that status updates miss.
Defining a sensible age threshold for your team
There is no universal number that means a card is stale. A design exploration might reasonably sit in review for a week, while a bug fix that has sat untouched for two days may already be a concern. The useful approach is to set thresholds relative to the kind of work your team does and how often it normally ships. Look back over recently completed cards and note how long they typically spent in each column. That historical pattern gives you a baseline that reflects your actual throughput rather than an arbitrary rule.
Once you have a baseline, pick a single threshold per column rather than a complicated matrix. For example, you might decide that any card in progress for longer than the typical completion time for that kind of work gets flagged for review. Keep the rule simple enough that someone can apply it in a few seconds during a weekly check. A threshold nobody remembers is no threshold at all.
Questions to ask when a card looks old
An aged card is a prompt for a conversation, not a verdict. When you find one, ask the owner a few specific questions. Is the task still wanted? Priorities shift, and a card may represent a decision that no longer holds. Is it blocked? A hidden dependency, a missing decision, or a waiting handoff can freeze a card without anyone recording it. Is it too large? A card that has aged may simply need to be split into smaller pieces that can finish independently. Is the owner still the right person? Sometimes ownership is nominal and the actual work has drifted elsewhere.
Each answer leads to a different action. A wanted-but-blocked card needs its blocker named and assigned. A too-large card needs decomposition. An unwanted card should be closed or deliberately parked, so it stops occupying a slot that real work could use. Recording the answer, even briefly in the card, helps the next reviewer understand why the card is still open.
A practical weekly aging review
A short, repeatable review keeps aging from becoming a one-time cleanup. Set a recurring slot, perhaps fifteen minutes once a week, and walk the board column by column. Start with the cards that exceed your threshold and go through the four questions above for each. Keep notes minimal: a status phrase, a new owner, or a date for the next check is usually enough. Resist the urge to reprioritize the whole board during this pass; the goal is to reveal stalled work, not to replan the quarter.
The review works best when it is framed as a check on the work rather than on the people doing it. If the conversation feels like an inspection, cards will be quietly moved to look fresh rather than honestly updated. Focus on whether the work can move and what would help it move. Teams that treat aging as information tend to surface problems earlier, which is the real point of the exercise.
A checklist for setting up card aging
Before you start, confirm that your board can show when cards entered their current column, or at minimum that your team can estimate it. Then work through a short list: agree on the columns where aging matters most, usually the ones representing active work; set a threshold for each based on your historical completion times; choose a fixed weekly slot for the review; and decide in advance who owns the follow-up on flagged cards. Finally, revisit the thresholds every month or two, because a team's pace changes as it grows or as its product matures.
Card aging will not replace conversation, and it will not fix an unclear priority list. What it does is make stalled work visible while there is still time to act. For a team heading toward a launch or a planning deadline, that early visibility is often the difference between a small adjustment and a scramble.