By the end of this lesson you can
- Design dashboards that support decisions, not decoration.
- Design data tables for scanning, sorting and bulk actions.
- Handle roles, permissions and complex workflows.
The idea
SaaS and enterprise products are used for hours a day by expert users doing complex work. Efficiency, clarity and reliability matter more than novelty.
Dashboards
Start with the decisions people make. A good dashboard answers "Is anything wrong? What needs my attention?" Show a few key metrics with comparison (versus target or last period), highlight exceptions and link to detail. Avoid filling space with charts nobody uses.
Data tables
- Align numbers right and text left; use tabular figures.
- Allow sorting, filtering, column choice and saved views.
- Support bulk selection and actions.
- Keep headers visible on scroll and offer density options.
Roles and permissions
Different users (admins, managers, agents) need different views and actions. Hide or disable actions people cannot take, explaining why when disabled.
Complex workflows
Support keyboard shortcuts, drafts, undo and audit trails. Research with real expert users, as their workflows are often invisible to outsiders.
Why it matters in real projects
Small inefficiencies in tools used all day multiply into large costs in time and errors. Enterprise buyers increasingly judge products on usability, and poor tools lead to workarounds, spreadsheets and mistakes. Designing for expert workflows creates real value and loyalty.
A realistic example
A support dashboard shows twelve charts. Team leads ignore it and check a spreadsheet instead. Research shows they need to know three things: tickets at risk of breaching the response target, agents overloaded and unusual spikes. The redesign shows these three at the top with exceptions highlighted and links to filtered ticket tables. Team leads start using it daily.
Step by step
Identify decisions
List the decisions each role makes.
Choose metrics
Pick a few metrics with comparisons.
Highlight exceptions
Surface what needs attention.
Design tables
Add sorting, filtering, bulk actions and saved views.
Map roles
Define what each role sees and can do.
Support experts
Add shortcuts, undo and audit trails.
Common mistakes
Mistake Decorative dashboards.
Instead Design for decisions and exceptions.
Mistake Tables without sorting or filtering.
Instead Support scanning and manipulation.
Mistake Designing without expert users.
Instead Research real workflows.
Check your understanding
Choose an answer, then check it. There is an explanation either way.
Practice exercise
Exercise · about 1 h
Dashboard redesign
Redesign a dashboard for one role.
Steps
- Choose a role and list their decisions.
- Pick three to five metrics with comparisons.
- Sketch the dashboard with exceptions highlighted.
- Sketch the linked detail table.
Deliverable
A dashboard and table sketch.
Self-assessment
Tick each item when it is true of your exercise. Be honest; this is for you.
4 items
Summary
- Enterprise users need efficiency and clarity.
- Design dashboards around decisions.
- Make tables powerful and scannable.
- Design for roles and expert workflows.
Further reading
Third-party sources, chosen for reliability. They open in a new tab.
- Data tables: four major user tasks (opens in a new tab)Nielsen Norman Group
- Material Design: data tables (opens in a new tab)Google
Your notes
Marking complete updates your course and roadmap progress.