Trend over time
Line chartShow direction, seasonality and turning points.
A dashboard is useful only if someone can look at it, understand what changed, and know what deserves attention next.
The job of a chart is not to show all the data. It is to make the important comparison hard to miss.
“The dashboard has everything, but we still spend the first 20 minutes asking what actually changed.”
That is a visualization failure. A dashboard can be technically complete and still make the decision harder.
Your goal is to create information hierarchy: what changed, why it matters, where it happened, and what deserves investigation.
Show direction, seasonality and turning points.
Make ranking and magnitude easy to scan.
Use only when composition is the question.
Show spread, skew and outliers.
Explore association between two numeric variables.
Pair the value with target, change or comparison.
Choose the chart after you know the comparison. “I want a pie chart” is not an analytical requirement.
Dhaka and Chattogram explain most of the cancellation-rate increase. Top-of-funnel traffic remained healthy.
The dashboard starts with the answer hierarchy: headline → primary KPIs → trend → driver. Filters and diagnostic detail can come later.
Describes the chart, but makes the reader do the analytical work.
States the relevant comparison and focuses attention immediately.
Use the title for the conclusion, the subtitle for context, and annotations for evidence.
One sentence explaining the main business change.
Completed orders, cancellation rate, demand, conversion.
Show when the shift began and whether it persists.
City or segment contribution to the change.
Reasons, platform, customer type, operational detail.
Freshness, exclusions and confidence caveats.
You are reviewing a weekly operations dashboard.
Decision:
Should leadership escalate the recent completed-order decline to Operations?
Known analysis:
- completed orders -11.9% week over week
- sessions +3.2%
- new users +4.9%
- cancellation rate increased from 8.2% to 15.1%
- Dhaka and Chattogram explain most of the increase
- data-quality checks have passed
Review the dashboard design:
1. Identify the 4–6 visuals that should be on the first page.
2. Explain what decision each visual supports.
3. Suggest an insight-led title for each.
4. Identify any misleading or redundant chart choices.
5. Suggest what should move to drill-down pages.
6. Do not invent additional findings. What decision should this visual help someone make?
What is the one main message?
Is the chart type appropriate for the question?
Are the axes, scales and time windows honest?
Is comparison context visible?
Can a viewer distinguish signal from noise quickly?
Does the title state the insight rather than the chart type?
Is uncertainty or data-quality risk visible when relevant?
“Completed orders fell 11.9% week over week even though sessions and new users increased. The decline is primarily associated with higher cancellations, concentrated in Dhaka and Chattogram. The next action is to investigate cancellation reasons and operational capacity in those two cities rather than reduce acquisition spend.”
Say what changed and what appears to drive it.
Use a small number of visuals that directly support the claim.
Show comparison periods, definitions and relevant caveats.
End with the next decision or investigation, not a generic summary.