DASHBOARDS & GRIDS
Dashboards vs chat: two kinds of questions
A dashboard answers the questions you ask every week with definitions everyone shares. Chat answers the question you have right now. Same data, same charts, different job.
The region pivot shows North far ahead with 395 orders, followed by West with 247, East with 168 and South with 142.
Two kinds of questions
Some questions come back every week with the same wording. How many orders did we take, against last week? How many are urgent right now? What did each region bring in this month? The answer changes; the question does not, and neither does the definition of what counts as an order or a region. These are recurring questions, and they are most of what a business watches.
Other questions arrive once, in the middle of something. Which region drove the spike on Tuesday? Why are rejected orders up this week, and is it one store or all of them? Show me that by category, then by week. Nobody planned for them, nobody will ask exactly that again, and the next question depends on the answer to this one. These are ad hoc questions, and they are most of what a business actually thinks about.
A dashboard is built for the first kind. Chat - a conversational assistant over the same data - is built for the second. Confusing the two is the most common way either one disappoints.
What a dashboard is for
The same numbers for everyone. A dashboard carries definitions. Revenue means what the widget says it means, net of the same exclusions, for the sales director and the warehouse lead alike, and the argument about whose spreadsheet is right stops.
Monitoring. It is open on a screen, glanced at between other things, and it shows when something has moved without anyone asking. A chat window cannot do that; it answers when spoken to.
Filters and saved views. An operations manager filters the orders grid to urgent, saves it, and opens the same view every morning. Urgent orders · 14 is a saved grid, not a question, and it is one click from the moment of opening the laptop.
Period comparison. This week against last, this month against the same month last year, built into the widget so the comparison is always the same comparison.
Access scoped by team. The North team's dashboard shows North. Scope is set once, by the people who manage access, rather than negotiated in every question.
What chat is for
The question you did not know you would ask. There is no widget for "which stores in North declined the most against the same week last year" because nobody knew to build one. In chat it is a sentence.
Follow-ups. The answer prompts the next question. Orders by region, then by category within North, then just the rejected ones, then why. Each step narrows the last, and the assistant carries the context, so nobody rebuilds the filter from scratch.
Pivots and leaderboards from one sentence. "Rank the regions by orders" is a leaderboard: North 395 · West 247 · East 168 · South 142. "By region and month, with totals" is a pivot. Shapes that take an afternoon to configure as widgets take a sentence to ask for.
The summary that explains the finding. A dashboard shows North at 395. An assistant can say that North leads order volume by a wide margin, name the next three, and offer what to ask next. The sentence is the part a dashboard cannot write.
Where each fails when used for the other
Dashboard sprawl. Treat every question anyone ever asked as a widget request, and the dashboard becomes forty widgets nobody reads, each one answering a question that was asked once in 2024. The signal drowns, and the people who needed the three recurring numbers stop opening it.
Chat as a daily monitor. Re-asking "how many urgent orders are there?" every morning is slower than opening a saved grid, less consistent, and invisible to the colleague who needed the same number. A question that is asked the same way every day is not a question any more; it is a widget that has not been built yet.
The handoff
The two surfaces feed each other, in both directions.
Chat to dashboard: when a question has been asked three times, with the same wording, by more than one person, it has earned a widget. Build it with the definition that the answers used, and the recurring version is now shared, monitored and one click away.
Dashboard to chat: when a widget shows a number that needs explaining - orders down, rejections up, a region out of line - the explanation is a question. Which region drove this? Which store within it? Since when? The dashboard says what; chat is where you ask why.
The same chart, either way
Nothing about the surface changes which chart is right. A trend is a line whether a widget draws it or an assistant does; a comparison is a bar; a part of a whole is a stacked bar; a ranking is a leaderboard; one number with its change is a KPI tile. The question picks the chart, and the rules in Choosing the right chart for business data apply to both. What differs is who chooses: on a dashboard a person chose once, in chat the assistant chooses per answer.
A day in the life
Nine in the morning. An operations manager opens the Urgent orders saved grid: 14, the same definition as yesterday, sorted the same way, and works through them. The Rejected orders grid shows 36; the Orders awaiting review grid shows 0, which is the number she wanted to see. Three glances, no questions, the day starts; the KPI tile at the top says 952 orders in all.
Three in the afternoon. The weekly dashboard shows an orders spike and no reason for it. She asks, in chat, which region drove it. North, 395 orders, well ahead of West on 247. Which stores in North? A leaderboard. Was it one category? A pivot. By four she knows, and by Monday, if the question comes back, it becomes a widget on the dashboard where it belongs.
Same data underneath both: one indexed layer, so the 395 in the chat answer is the same 395 the dashboard would show. That is the condition that makes the handoff safe. If the two surfaces counted differently, nobody would trust either.