Dashboards fail in predictable ways: everything screams, nothing answers, and the demo looks great until real data arrives. Seven principles we apply on every product.
1. Design for the question, not the data
Every widget should answer something a user actually asks: Am I on track? What needs me today? If you can’t name the question, the widget is decoration. Cut it.
2. One screen, one job
The overview orients; detail screens operate. When an overview tries to do both, it does neither — that’s how 40-widget dashboards happen. Orient, then link deeper.
3. Hierarchy is the product
A user should read the screen’s most important fact in one second, the supporting picture in five. Size, weight, and position carry that — if everything is bold, nothing is.
4. Respect density
Operators who live in a tool all day want information-rich screens, not whitespace theater. The skill is dense and calm: tabular numerals, aligned columns, disciplined color. Our Merchant OS order queue is designed to be triaged at keyboard speed.
5. Charts answer; they don’t decorate
Default chart libraries produce rainbow noise. Use one accent color plus grays, label directly instead of legend-hunting, and pick the form the question demands — trend over time is a line, composition is not a 3D pie.
6. Design the empty, loading, and error states first
A dashboard’s first impression is its emptiest state — day one, no data. If onboarding shows a graveyard of zeros, activation dies there. Real products live in partial states most of the time; design them deliberately.
7. Real data or it doesn’t count
“Jane Doe / $1,234” hides every layout failure. Test with the ugly truth: 47-character names, nine-digit revenues, negative numbers, empty columns. If the design survives that, it ships.
Building a product and staring at a blank dashboard canvas? That’s our favorite brief.