SaaS · Dashboard · 2024
Partner Dashboard
A dashboard experience designed to help partners track project performance, insights, and operational progress.
Overview
Project overview
The Partner Dashboard is the daily control center for business partners managing performance, payouts, and inventory. I redesigned it to be scannable, fast, and trustworthy at scale.
01
The problem
Partners managed their business across spreadsheets and emails. The original dashboard showed everything at once, so nothing stood out and key decisions were slow.
02
My role
I led the redesign as senior designer — establishing a dashboard framework, data-viz guidelines, and a scalable component library used across the platform.
03
Who we designed for
Operations leads and account managers who live in the product all day and need to act on anomalies before they become problems.
04
Research
- Contextual inquiry with 7 partner teams in their workflow.
- Heatmap and session-replay analysis of the legacy dashboard.
- Prioritisation workshops to define the 'first five seconds'.
- Iterative usability testing across three prototype rounds.
05
Key insights
Partners checked the same 3 metrics before anything else.
Anomalies needed to find the user — not the other way around.
Density was fine; lack of hierarchy was the real problem.
Customisation mattered, but smart defaults mattered more.
06
Design decisions
A clear visual hierarchy
Built a strict typographic and spacing scale so the most important numbers always win attention.
Insight, not just data
Added contextual deltas, thresholds, and proactive alerts so the dashboard interprets, not just reports.
Composable widgets
A modular grid of widgets with sensible defaults and optional per-team customisation.
07
Final solution
A calm, high-contrast dashboard with a confident grid, a disciplined chart palette, and alerting that surfaces what needs attention first — all responsive down to tablet.
Impact
The impact
−35%
Time to insight
200+
Partners onboarded
+24%
Daily active usage
Reflection
What I learned
- In dense interfaces, hierarchy is the feature — restraint outperformed more data.
- A shared component library kept quality high as the surface area grew.
Next case study