Question for the frontend and UX folks here. Why do most SaaS dashboards in 2026 still feel like enterprise software from 1998 in everything but the CSS?
I noticed this hard when redesigning my own product (Zenovay, cookieless web analytics). The first version of our dashboard had:
- a left sidebar with 14 menu items
- a top bar with 6 controls
- 8 chart widgets visible at first paint
- a "configure dashboard" modal with 23 options
It looked exactly like every other analytics tool. I could not tell my dashboard apart from PostHog or Amplitude in a screenshot.
Then I looked at how my actual users used it. The pattern was:
- arrive at dashboard
- look at 2 numbers
- click one drill down
- leave
Total time spent in the dashboard: 47 seconds median. Almost nobody touched the sidebar after onboarding.
So the 14 menu items, 6 controls, 8 widgets, and 23 configuration options were all competing for attention with the 2 numbers people actually came for.
The redesign
New version:
- 2 numbers at the top, big, no chart, just numbers
- 1 trend chart underneath
- 3 drill in cards (top pages, top sources, top conversions)
- everything else moved to a "more" menu
Median time on dashboard went up to 1m 50s. Pages per session went up. The "I can't find X" support emails dropped.
Why this took 4 years across the industry to figure out
Hypothesis 1: founders look at their own tools through builder eyes, not user eyes. We see all 14 menu items because we built them. A new user sees noise.
Hypothesis 2: dashboard density correlates with perceived "powerful". We're rewarded by the prospect's "wow this is comprehensive" reaction in the sales call. The customer then ignores 90% of it.
Hypothesis 3: the B2B buying loop selects for tools that look like they have lots of features. Procurement teams want checklists. Engineers want simplicity. The buyer is rarely the user.
Hypothesis 4: it's just hard. Saying no to a chart widget that someone, somewhere, wants is a daily resistance pattern. The default is to add.
The pattern I'm trying to follow now
- First paint is sacred. Whatever is on first paint is what the user thinks the product is. Choose ruthlessly.
- Power users get a different surface. Don't try to make one UI that pleases the casual visitor and the power user. Casual visitor gets a minimal dashboard. Power user gets a separate "explorer" route.
- Sidebar items are debt. Every item is one more thing the user has to mentally ignore. Items must earn their place by being clicked.
- Configuration is for users who asked for it. Default to opinionated defaults. Configuration is a power user feature. The setting hidden in a submenu is rarely the same one that's exposed at first paint.
Counter argument I can hear
"You're describing a consumer UI pattern. Enterprise customers want density." Maybe. But I think the gap between consumer and enterprise UI standards is closing fast, and the new buyer who is a millennial PM or technical founder is closer to consumer expectations than to circa 2010 enterprise.
Real question for the thread
What's a SaaS dashboard you actually enjoy using? Specifically: not respect, not "admire from a distance", but actually open with mild satisfaction. Curious where the bar actually is.
I'm Valerio. Built Zenovay, spent an embarrassing amount of time learning this lesson on my own product.
Top comments (0)