A dashboard is not a product


Most people don’t open dashboards. Even in analytics tools companies pay for and train people on, only about a quarter of employees use them actively. For busy users, a to-do list or a recommendation usually works better, though a dashboard is still the right call in some cases. The article covers how to tell which one you need.
A dashboard is the default answer when a team has data and isn't sure what users need. It demos well, it looks impressive in a sales call, and it puts every number in one place. Nobody has to decide which number matters.
That last part is the problem. A dashboard hands the hardest part of the job, deciding what to do, to the person with the least time to do it. The user has to open it, read it, work out what's unusual, decide what that means, and then go somewhere else to act on it.
BI and analytics tools are dashboards that companies pay for and train people on. Even there, only about 25% of employees actively use them, according to a global survey of 214 data and analytics leaders, and that share has barely grown in the years the researchers have tracked it [2].
Then think about who uses your product. Usually it's someone in the middle of something else, like a manager who looks at the screen between phone calls. That person isn't going to read a chart to work out what to do next. If the screen doesn't tell them, they'll do what they did yesterday.
UX researcher Page Laubheimer describes a dashboard as information “on which users can act quickly”, like a car dashboard that answers “Am I speeding?” [3] The word that matters there is act. A lot of product dashboards answer "what happened?" and leave "so what should I do?" to the user.
A dashboard hands the hardest part of the job, deciding what to do, to the person with the least time to do it.
Take one example. A dashboard shows a chart of overdue invoices and the total amount outstanding. Accurate, and nobody does anything with it.
The to-do version uses the same data: "Four invoices are more than 30 days late. Two of these customers usually pay after one reminder. Send reminders?" There's a reason, a suggested action and a button. When the user is done, the list is empty, and that empty list is the point.
A recommendation goes one step further: the product decides for the user and lets them overrule it. For example: “These two customers usually pay within a week of the due date, so we won’t send them a reminder yet. Send one anyway?”
A few signs that the screen should suggest an action:
The user acts on the data. If every look at the screen ends with the same few actions, the product can suggest them.
The same patterns lead to the same decisions. If you can write the rule down ("late by 30 days and usually pays after one reminder"), the product can apply it.
The user is busy or interrupted. If they only have a minute between other tasks, that minute should go to the next step.
There's a clear "done". A list can be finished. A dashboard can't.
A dashboard is still the right tool in some cases: for people whose job is to look for trends, like analysts and managers reviewing a month; for exploring a question nobody has asked yet; and for monitoring, where the normal state is "nothing to do" and the screen only needs to show when that changes.
The opposite mistake is just as common. A team swaps the dashboard for notifications and sends one for everything.
Nielsen Norman Group’s advice on dashboards is to guide attention to critical values, but not by flashing endless alerts without priority [4]. Hospitals show what happens when there are too many warnings: clinicians override the vast majority of electronic warnings, including ones marked critical, according to the US Agency for Healthcare Research and Quality [1]. People learn to click past them.
A suggestion that’s ignored 90% of the time is teaching people to ignore the other 10%.
A useful to-do list is short and ordered. Each item has a reason (in the invoice example, “this customer usually pays after one reminder”), one obvious action and a way to dismiss it. Then track which suggestions people ignore and cut those. A suggestion that’s ignored 90% of the time is teaching people to ignore the other 10%.
You don’t need to rebuild the product to try this. A small start looks like this:
Watch someone use the dashboard. Note what they do right after they look at it. That's the action the product should be suggesting.
Write down the decisions people make. In the invoice example from earlier, the person checking the screen wants to know which late-paying customers to send a reminder to. The total amount outstanding doesn’t tell them that. The screen should show who to remind, and why.
Turn the most common decision into one list. The others can wait until this one works.
Show the reason next to each item. People act on suggestions they understand and ignore the ones they don't.
Keep the numbers one click away. Some users will want to check the data behind a suggestion. Let them, but don't make them start there.
The test is simple: after someone opens your product, do they know what to do next? If the answer is “only if they read the charts carefully”, the product is still leaving the hardest part to them.
Sources
AHRQ, PSNet (2019). Alert Fatigue
BARC (2022). Infographic: Strategies for Driving Adoption and Usage with BI and Analytics
Laubheimer, P., Nielsen Norman Group (2017). Dashboards: Making Charts and Graphs Easier to Understand
Nielsen Norman Group (n.d.). Alert Fatigue in User Interfaces

Edita Dermontaité
Hands-on CPO and product leader who still builds (with AI)
I’ve often been the first: the first product hire at Leadcamp and Bizzy, where I led product as CPO for five years, and the first user researcher at Lighthouse, where I spent two years building the research function.
For the past year I’ve worked as a fractional CPO and hands-on product leader, helping B2B SaaS teams between traction and scale connect what engineering builds to what brings in revenue.
I started out as a graphic designer, so I still design and test things myself, these days mostly with AI: in Claude and Lovable, or straight in code with Cursor.
Book a free 30-minute call, or a coffee in Ghent. We’ll look at what’s slowing your product down and what to do about it. I work with teams fractionally or hands-on as an embedded product leader, 2–5 days a week, depending on your needs and my availability.
Product leadership for B2B SaaS between traction and scale, from a hands-on CPO and product leader who still builds (with AI). I take product decisions off the founder’s shoulders and get product, engineering and sales moving in one direction: revenue.

New North BV
BE 1025.547.940
9050 Ghent
Belgium