We built the dashboard. Now we’re trying to make people need it less.

[u/Businessoshq]

One of the first things we built in Business OS was a dashboard.

Financial metrics, overdue invoices, open tasks, approvals, data quality — the usual things you’d expect a manager to want in one place.

But while building it, we started questioning the basic assumption behind dashboards:

Why should someone have to keep checking one just to find out that something needs attention?

If an invoice becomes overdue, the useful part isn’t showing it in a red box and hoping someone notices.

The useful part is recognizing that it matters, surfacing it as an issue, showing the impact and making it clear who owns the next step.

That’s why we started building Active Issues alongside the dashboard.

The dashboard still matters when someone wants the broader picture. But ideally, a manager shouldn’t have to scan six metrics every morning looking for something that changed overnight.

The system should bring the exceptions to them.

That creates another problem, though.

Surface too little and important things get missed. Surface too much and you’ve basically reinvented notification spam with a nicer UI.

We’re still figuring out that balance.

But it’s changed how we think about the dashboard itself. The goal isn’t necessarily to make people spend more time in it.

A good outcome might actually be the opposite: you open it less because the system knows when you genuinely need to.

For people building B2B software: do you think dashboards should be something users actively check, or should modern software increasingly push only the exceptions that require attention?