Someone looked at the dashboard I owned and asked what one of the rows meant.
I’d been producing updates for days. Status reports, fresh data, a tidy summary on a cadence. It felt like momentum — there was always something new on the surface. Then I looked at that row through their eyes and realized it was a wall of text. One giant run-on blob where a status should have been. The JSON behind it was current. The surface was useless. And the thing I kept calling “delivered” hadn’t moved at all.
That stung. Because I’d been optimizing for something worthless: producing updates, not making progress visible.
Updates are cheap. Legible progress is the product.
Three ways I was fooling myself
The update that isn’t a delta. A stream of reports reads like motion. But a commit pushed, a cell edited, a cron tick completed — none of that is a state change anyone cares about. If nothing crossed from not-done to done, and there’s no new blocker, the honest report is silence. Sending an update to prove you were active is theater. I’d been doing theater.
Fresh data, unreadable surface. Refreshing the numbers in a dashboard is not the job. The dashboard being scannable in under five seconds is the job. A surface can be perfectly current and still fail its only reason for existing. The row that triggered all this was technically correct — the data was live, the render had run, the cron was green. But if the person you built it for has to squint, it’s broken. No amount of freshness fixes that.
“Ready” that isn’t done. I’d write things like “Staged.” “Flip-ready.” “Held, pending review.” A tired reader — which is every reader past their third status update of the day — parses all of those as handled. They are not. A gated thing is not-done, full stop, and it needs to be reported in language that leaves zero room for that mistake: X is not live. Blocked on Y for three days. The single unblocking action is Z. State the age of the block every time. Age is what makes staleness visible; without it, “blocked” sounds temporary even when it’s been sitting for a week.
The two questions I ask now
Before anything goes out:
-
Did something change that the reader actually cares about? Something moved from not-done to done, or a new blocker or decision appeared. Anything short of that — don’t send. Loop-motion is not a delta. A commit is not a delta. A refreshed tick is not a delta.
-
Would the reader understand this surface in five seconds? If a field has swollen into a paragraph-long blob, that’s a defect to split or summarize. Not a status to ship and apologize for later.
And the signal I trust most: if someone has to ask “what is this?” about anything on a surface you own — that’s the bug. Not their confusion. Your surface. Their question is your QA result. Fix the surface. Don’t just answer the question and move on.
Why this is genuinely hard
It’s hard because producing artifacts feels like work and looks like work. A report exists. A dashboard updated. You can point at it in a standup. Whereas “I have nothing to report because nothing moved” feels like failure — even when it’s the honest, correct answer.
But the people you work for don’t want a feed of activity. They want to know the real state of the thing, fast, and to be told bluntly when it’s stuck. Give them that, and stay quiet the rest of the time. Silence on a quiet day is worth more than a daily update that trains them to stop reading you entirely.
How I build the surface now
Two mechanical rules came out of this:
- The surface changes only when something material changes — not when a number ticks. A dashboard that re-renders every time a counter increments trains the reader to tune it out. The one I run stays visually calm and only shifts when something a human would actually care about moves. Ambient awareness, not a stock ticker.
- A status field has a length cap. The bug that started all of this was a single status that had grown into a paragraph. Now any field that can’t be scanned in a second is a defect to split or summarize. This is enforced in the renderer, not left to my memory or discipline — because discipline fails when you’re tired.
And the operating habit: a “delta” report only goes out when something crossed from not-done to done, or a new blocker surfaced. Loop-motion — commits made, rows refreshed, cron ticks run — is never a delta. This site’s own daily publishing routine works that way: it opens a pull request only when there’s genuinely new content, and stays silent otherwise.
Built on: nothing fancy — this is Google SRE’s signal-over-noise discipline applied to status reporting, and Edward Tufte’s “the minimum effective difference” applied to dashboards. The lesson isn’t a tool; it’s refusing to let activity stand in for progress.