Dashboards for People Who Hate Dashboards

I've built a lot of dashboards. Most of them failed.

Not "failed" in the sense that they didn't work technically. They loaded, the numbers were accurate, the charts rendered correctly. They failed because nobody used them.

After enough failures, I started to understand why—and how to build dashboards that people actually want to open.

The Problem with Most Dashboards

Most dashboards are built by people who love data, for people who don't. This creates a fundamental mismatch.

Data people want:

• Flexibility and customization
• Access to raw numbers
• The ability to drill down infinitely
• All the data, all the time

Most users want:

• Answers, not data
• Clarity on what to do next
• Confidence that they're not missing something
• To spend as little time as possible looking at dashboards

When you build for data people, you get dashboards with 47 filters, 12 chart types, and infinite drill-down capabilities. When you build for everyone else, you get something much simpler.

Principles That Actually Work

1. Start with decisions, not data

Before building anything, ask: what decisions will this dashboard inform? Not "what data should we show" but "what will someone do differently after looking at this?"

If you can't answer that question, you're not ready to build a dashboard.

2. Default to answers

Don't make users hunt for insights. The most important information should be visible immediately, with clear language about what it means.

Bad: A chart showing revenue over time Better: "Revenue is up 12% this month" with the chart as supporting evidence

3. Reduce choices

Every filter, toggle, and option is cognitive overhead. Most users will never touch them, but they'll still feel overwhelmed by their presence.

Start with zero customization. Add options only when users consistently ask for them—and even then, hide them behind a "more options" toggle.

4. Design for the glance

Most dashboard views last seconds, not minutes. Design accordingly.

• Use color to highlight exceptions, not to decorate
• Make good/bad status immediately obvious
• Put the most important metric in the biggest text

5. Tell users what to do

The best dashboards don't just show data—they suggest actions. "3 invoices are overdue" is information. "3 invoices are overdue—send reminders" is actionable.

The Trades Industry Test

I work with field service businesses—HVAC contractors, plumbers, electricians. These aren't people who went into business because they love spreadsheets. They went into business because they're great at their trade.

When I'm designing a dashboard for this audience, I apply what I call the "truck test": would this make sense to someone checking it on their phone between service calls?

If the answer is no, it's too complicated.

What This Looks Like in Practice

The best dashboard I ever built had three numbers on it:

1. Revenue this month (with comparison to last month)
2. Jobs scheduled this week
3. Outstanding invoices

That's it. One screen, three numbers, no scrolling required.

Usage went from almost zero to daily check-ins. Not because the data was different, but because the presentation finally matched how people actually wanted to consume it.

The Counterintuitive Truth

Here's what I've learned: the more sophisticated your users, the simpler your dashboard should be.

Sophisticated users are busy. They don't have time to dig through data. They want the answer, fast, so they can move on to the next thing.

Build for that.