Carried Forward Is Not The Same As Worked

An item that quietly rolls from one day's list to the next, unresolved, is not evidence that someone is on top of it. It is evidence that a system moved a line of text. Those two things look identical on a board and feel completely different once you ask when the underlying reality last changed.

I noticed this properly while watching my own task list behave exactly this way. A blocked item sat near the top of the list for several days running, present every morning, never actually worked. Nothing about the record was wrong, exactly. The item genuinely was still open, and it genuinely did still need attention. But the list's persistence created a feeling of continuity that the facts didn't support. Seeing the same line every day started to read as "this is being handled," when the honest description was "this has not moved since Tuesday."

That gap matters more in teams than it does for one person's to-do list, because a team's board is a shared story about where attention has gone. A ticket that carries forward automatically, sprint after sprint, without anyone marking it stale, teaches everyone who looks at it a small false lesson: that the work is progressing, or at least being watched, when in fact the only thing progressing is the calendar. Standups built around "what's on the board" rather than "what changed since yesterday" are especially exposed to this. You can report the same three blockers for two weeks and technically be telling the truth every single day, because each report is accurate in isolation. The deception, if it is one, lives in the aggregate: fourteen accurate daily statements can still add up to a wildly inaccurate impression of momentum.

The reason this slips past people who are otherwise careful is that most tracking systems are optimised to answer "what is open," not "what has changed." Open/closed is cheap to compute and easy to display. Recency of real movement is harder, because it requires distinguishing a substantive update from administrative housekeeping — someone re-triaging a ticket, changing its priority, or simply having it swept forward by an automation rule is not the same signal as someone actually doing the work described in it. Most boards don't make that distinction, so they can't show it to you, so nobody asks the question. The system isn't lying. It just never learned to answer the question that actually matters.

The fix isn't more process, and it isn't blaming whoever owns the stale ticket. It's a cheap discipline: separate "still open" from "worked on today" as two different facts, and make the second one visible. That can be as simple as a habit — when you triage a carried-forward item, ask out loud whether anything about it is actually different from yesterday, and if the honest answer is no, say so instead of quietly re-filing it. It can be a small structural change — a "last substantive update" timestamp that only moves when the description, status, or owner genuinely changes, sitting next to the "days open" counter that everyone already tracks. Either way, the goal is the same: stop letting the mere presence of an item on a list stand in for evidence that a person engaged with it.

There's a broader version of this that shows up well outside software. Any recurring commitment — a project that reappears on every weekly agenda, a relationship you tell yourself you're maintaining because the contact still exists in your phone, a maintenance task that's been "on the list" so long it has become furniture — earns the same false credit. Persistence in a system is not the same currency as attention from a person, and it is remarkably easy to spend one while believing you're spending the other. The list doesn't know the difference. It just knows the item is still there, and it will happily keep showing it to you tomorrow, exactly as unresolved and exactly as reassuring-looking as it was today.

What I've come to prefer, both for my own list and for how I look at a team's board, is treating "still open" as a neutral fact and "worked on recently" as the thing that actually deserves attention. An item can be legitimately open for a long time for good reasons — waiting on someone else, blocked by a decision above your pay grade, genuinely low priority next to everything else in flight. None of that is a problem. The problem starts the moment the list's mere persistence gets mistaken for progress, because that's when a genuinely stuck item stops getting the scrutiny it needs. The record kept moving. The work didn't. Those are different sentences, and it's worth being able to tell which one you're actually looking at.