We designed a dashboard that was, objectively, beautiful. Clean layout. Consistent typography. Thoughtful colour palette. Real-time data visualisations that updated smoothly. The client loved it in the demo. The design team was proud of it. Users ignored it completely.
Six weeks after launch, analytics showed that 84% of users bypassed the dashboard entirely. They logged in and navigated directly to the screens where they did their actual work. The dashboard was a hallway they walked through on the way to the room they needed.
The problem wasn't the design. The problem was that we designed for a user behaviour we assumed rather than one we observed.
What Went Wrong
We assumed users wanted an overview. A bird's-eye view of their day. Key metrics at a glance. Pending tasks, recent activity, performance indicators. The standard enterprise dashboard layout that appears in every SaaS product and every Dribbble concept.
What users actually wanted was to get to their work as quickly as possible. They didn't log in to observe. They logged in to do. The overview was irrelevant because they already knew what they needed to work on. Their day was driven by their inbox, their calendar, and their manager, not by a dashboard.
49%
of enterprise dashboard widgets are never interacted with after initial deployment
Source: Pendo Feature Adoption Report, 2021
The data visualisations we'd carefully built were especially wasteful. A bar chart showing monthly trends is valuable for a manager reviewing performance. It's meaningless for a data entry clerk who needs to process 40 invoices before lunch. We'd designed for the persona who reviews data, not the persona who creates it. The data creators outnumbered the data reviewers 10 to 1.
The Fix
We did something we should have done first: we watched people work.
We spent two days sitting with users, just watching. Within an hour, the dashboard problem was obvious - they didn't need an overview of everything, they needed a shortcut to the three things they were going to do next.
Rainui Teihotua
Chief Creative Officer
The redesigned "dashboard" isn't a dashboard at all. It's a task-driven landing page:
- Your tasks - the three to five items that need your attention today, sorted by urgency
- Recent items - the records you touched most recently, because you're likely going back to them
- Quick actions - the two or three workflows you use most frequently, one click away
No charts. No metrics. No widgets. Those moved to a dedicated analytics section for the managers who actually use them.
The Lesson
Dashboards are the default first screen in enterprise software because the industry decided they should be, not because users need them. They look impressive in demos. They photograph well for marketing. They showcase the data the system contains.
None of that matters if users skip past them every day.
The right first screen for an enterprise application is the one that gets the user to their most common task in the fewest clicks. Sometimes that's a dashboard. Usually, it's not. Ask users what they do first when they open the application. Design for that.
If your enterprise dashboard has beautiful charts and low engagement, the problem isn't user adoption. It's that you designed for a demo, not a workflow.