Note
Dashboards Don’t Show Data. They Answer Questions.
A dashboard filled with charts is not necessarily useful. What matters is whether those charts answer the right questions—and in the right order.
You open a dashboard.
You see:
- A row of KPIs
- A few trend charts
- Some breakdowns by segment
Everything looks complete.
So you start scanning.
Top left. Then right. Then somewhere in the middle.
A few minutes pass.
And you realize: you don’t actually know what you’re supposed to take away.
The data is there.
But the understanding isn’t.
The Hidden Assumption
Most dashboards are built on an unspoken assumption:
If we show enough data, the insight will emerge.
So people include:
- Every relevant metric
- Every useful breakdown
- Every chart they can fit
Nothing is technically wrong.
But nothing is clearly right either.
Because dashboards are not meant to display everything.
They are meant to answer something specific.
Start With a Topic
Every dashboard should be anchored on a topic.
Not a vague area.
Not a collection of metrics.
A topic.
For example:
- Revenue performance
- Customer retention
- Operational efficiency
Once the topic is clear, the role of the dashboard changes.
You are no longer asking:
What data do we have?
You are asking:
What does someone need to understand about this topic?
From Topic to Questions
A topic on its own is still too broad.
So the next step is to make it concrete—through questions.
If your topic is Revenue, the natural questions might be:
- How did we do overall?
- How did performance change over time?
- Where is revenue coming from?
- Are we improving or declining?
These questions define the scope of your dashboard.
They define what belongs—and just as importantly, what doesn’t.
Because every chart is doing a job.
It is evidence for answering a question.
If a visual doesn’t contribute to that, it doesn’t belong.
From Questions to Flow
Once the questions are clear, flow is no longer a design choice.
It becomes a constraint.
You’re not arranging charts.
You’re ordering answers.
The key question is:
Which answer needs to come first, for the next one to make sense?
For example:
You wouldn’t start with “Where is revenue coming from?”
Because without knowing overall performance, the breakdown has no context.
So the sequence becomes:
- How did we do overall?
- How did performance change over time?
- Where is revenue coming from?
- Are we improving or declining?
Each answer makes the next one easier to understand.
That is flow.
Not storytelling as applied in slides (discussed in Every Slide Should Tell a Story).
Structured understanding.
What Happens Without Them
When there is no clear topic—and no defined questions—something predictable happens.
Everything feels relevant.
So everything gets included.
More KPIs.
More charts.
More filters.
The dashboard grows.
But the clarity doesn’t.
Because now the viewer has to:
- Decide where to look
- Decide what matters
- Decide how to connect the pieces
And when the audience has to construct the logic themselves, the dashboard has already failed.
Before You Build Your Next Dashboard
Start here:
What is the topic?
Then:
What questions must be answered for someone to understand it?
Then:
In what order should those questions be answered?
And finally:
If someone lands on this dashboard cold, can they follow that sequence without guidance?
If they can’t, that’s where the structure breaks.
Because at the end of the day, dashboards are not collections of charts or data.
They are structured answers to a topic.