---
title: "The Number Was Real. It Just Wasn't Recent."
canonical: https://dxdev.com/blog/2026-08-08_dashboard-number-with-no-age-on-it/
datePublished: 2026-08-08
---
## A number that looked like it was happening right now

Someone on our team read a dashboard, saw a count next to a page name, and next to that count sat a "most recent occurrence" timestamp from that same day. Two numbers, side by side, telling two different stories. Read together, they told one story instead: this is happening right now, a lot.

That reading made sense. It was also wrong. The count wasn't a measure of today. It was every time that error had ever happened, going back more than two years, added up into one number with no label to say so.

## Why the old way was a trap

Nobody wrote that dashboard to be misleading. The count was accurate. The timestamp next to it was accurate. The problem was that neither one said what it actually was. A total with no age on it, sitting beside a timestamp that did have an age, gets read as if it shares that age. It's not a math error. It's a labeling gap, and it's an easy one to walk right past, because both numbers are individually correct.

Checking real, current data directly, rather than trusting the dashboard's framing, showed the truth: a slow trickle spread across two years, not a flood from that morning. Getting to that answer took someone stopping, doubting the framing, and going to look at the raw numbers instead of the summary.

## What changed

The fix wasn't a note explaining the old number better. A note gets read once, if that, and the same misleading pair would still be sitting there for the next person who glances at the screen. The actual fix added a second count next to the first, one genuinely bounded to the last seven days, and relabeled the old count "all time" so it could no longer pass as something current. Now a person glancing at that page sees both numbers at once and can tell instantly which one matters for right now.

## What a person still has to decide

Nothing here removes the judgment call. A real, current count still needs a person to decide whether it's actually urgent, how to prioritize it, and who should look at it next. What changed is what that person is looking at when they decide. Before, they were deciding based on a number that was quietly answering the wrong question. Now the two questions, "how much has ever happened" and "how much is happening lately," each get their own honest answer, and the decision that follows is at least based on the real one.

## The rule worth keeping

Any number you show someone needs its age stated in plain sight, not buried in a query nobody reads. If a total and a recent timestamp are ever going to sit near each other on a screen, put a real time-bounded number there too, so nobody has to guess which story they're being told. The next time a number on a screen makes you want to act immediately, check its age first. It might have been sitting there for two years.