Every dashboard is a question somebody stopped asking
By Meet Patel · 2026-09-06 · updated 2026-09-11
Summary
Every dashboard began as a live question, and building it converted the question into a display that no longer requires anyone to ask. Reporting infrastructure makes numbers correct and available; decision infrastructure determines what happens next, and consists of a threshold, an owner, a response and a review. Companies respond to decision failures by adding more reporting, which is the same layer one unit larger. A retirement rule — every dashboard names its decision, its owner and a review date, or is deleted — keeps the surface honest.
Key Metrics & Takeaways
- 41 dashboards
- in one company, 19 unopened for a month
- 4 parts
- threshold, owner, response, review
- 6 weeks
- a correct churn signal sat unread on an unopened dashboard
Every dashboard in your company started as a real question.
Somebody cared urgently. They wanted to know whether the change was working, whether the segment was holding, whether the thing they had just shipped had done anything. The question was alive, and someone built a chart so it could be answered whenever it came up again.
That was the moment it stopped being a question. It became a display, and displays do not require anyone to ask.
The count only goes up
I counted forty-one dashboards in one company. Nineteen had not been opened in a month.
Nobody had been careless. Each one had been built on the day it mattered most, by someone with a good reason, and none of them was wrong. They just outlived the week that produced them, and nothing in the building was responsible for noticing that.
This is the structural bit. Dashboards accumulate monotonically. There is a role that creates them and no role that removes them, so the surface grows every quarter while the attention available to read it stays exactly the same size it was in 2019.
And the response to a miss makes it worse. Something goes wrong, we ask how nobody saw it, and we build a chart. Which is the same layer, one unit larger, and it will be unopened by March.
Two layers, and companies keep buying the wrong one
It helps to name them separately.
- Reporting infrastructure — warehouses, models, dashboards, scheduled emails. Its responsibility is that the number is correct and available. It has succeeded when a person who goes and looks can find out.
- Decision infrastructure — thresholds, owners, responses, reviews. Its responsibility is that the right person finds out without having looked, and that something happens next. It has succeeded when a decision was made and someone checked whether it worked.
Nearly every company I have seen has excellent reporting infrastructure and essentially no decision infrastructure. Not thin — absent. No written thresholds, no owner per signal, no measurement of how long a response takes.
And because the two get confused, every decision failure gets a reporting fix. That is why the count only goes up.
What decision infrastructure actually contains
Four parts, and a chart is not among them.
A threshold. The number at which this stops being normal variance and becomes something. Written down, in advance, by a person with the authority to set it. Deciding this is uncomfortable, which is why it is almost never done — it forces you to say out loud how bad something has to get before you will interrupt your week.
An owner. A named person, not a team. A team owning a signal means nobody owns it, and everyone assumes it has been seen.
A response. What happens when the threshold is crossed. Even if the answer is we discuss it at the next review, that is a response and it can be evaluated. What cannot be evaluated is the absence of one.
A review. Whether the response worked, checked at a stated point afterwards. This is the part everybody drops, and dropping it means the thresholds never get better because nobody ever finds out that one of them was set wrong.
None of that requires software. All of it can be written on one page per signal, and the exercise of writing it is most of the value.
The thing that actually cost us
The churn signal that lost us a quarter was on one of the nineteen unopened dashboards. It had been correct and visible for six weeks.
The instinct afterwards is to look for negligence. There was none. Nobody's week had room, and the chart had no threshold, no owner and no response — so being correct was the only thing it was ever going to do.
A dashboard is a passive instrument. It cannot fail, and it cannot succeed either. It has no view about whether what it is showing is worth anyone's Tuesday, and asking it to have one is asking the wrong object.
The retirement rule
Every dashboard names the decision it supports, the person who makes that decision, and the last date it was used to make one.
Anything that cannot answer all three gets archived. Not deleted with ceremony — archived, quietly, and if somebody notices within a month you bring it back and now you know it was real.
Very few come back. That is the finding, and it is worth more than the reclaimed space: most of the surface a company maintains is answering questions nobody is currently asking, and the maintenance of it is being paid for in the one budget nobody tracks.
Frequently asked questions
Why do companies have too many dashboards?
Because building one is the standard response to a decision failure. Somebody missed something, so a chart is added, which feels like a fix and costs almost nothing. The dashboard count therefore grows monotonically — nothing in a normal company is responsible for removing one — while the attention available to read them stays fixed.
What is decision infrastructure?
Decision infrastructure is the set of thresholds, owners, responses and reviews that determine how a company moves from information to action. It differs from reporting infrastructure, which is responsible only for a number being correct and available. Most companies have industrial-grade reporting infrastructure and almost no decision infrastructure.
How do you decide which dashboards to retire?
Require each one to name the decision it supports, the person who makes that decision and the date it was last used to make it. Anything that cannot answer all three is a display rather than an instrument and can be archived. The count matters less than the fact that something in the company is finally responsible for removing them.
Written by Meet Patel — founder of Company 8, building Dan (usedan.com). Dubai, UAE.