The Dashboard Problem
Every SaaS has one. Few do it well.
We redesigned a client's dashboard 3 times. Here's what finally worked.
The Mistakes
1. Too Much Data
"We show everything users might want."
No. Show what users need.
Most dashboards fail here.
2. No Hierarchy
Everything is equally important.
Nothing is.
Users can't find what matters.
3. Charts for Charts' Sake
"We need visualizations!"
Why? What does the user learn?
The Framework
1. Who Is Looking?
Different users need different views.
Admin? Manager? Individual contributor?
Design for the primary user.
2. What Do They Need?
One question each dashboard section answers.
Not "here's data." But "here's insight."
3. What Should They Do?
Dashboard isn't passive viewing.
It's action-oriented.
What should users do based on this data?
The Layout
Top: The One Number
What's the most important number?
Revenue. Users. Conversions.
Show that. Prominently.
Middle: Trend
How is that number changing?
Sparkline. Last 30 days. Trend matters.
Bottom: Action Items
What needs attention?
Flag issues. Highlight opportunities.
The Principles
1. Reduce
Remove anything that doesn't answer a question.
If it's decorative, remove it.
2. Group Related Data
Users think in tasks, not metrics.
Group metrics by task, not by type.
3. Make Numbers Readable
Big fonts for important numbers. Small fonts for context.
The Checklist
- Who is the primary user?
- What is the most important number?
- What trend matters?
- What action should they take?
- What can be removed?
The Honest Take
Most dashboards are vanity projects.
Show what matters. Remove everything else.
Less is more.
