PRONTO XI DASHBOARD
From one generic dashboard to a role-based workspace platform
Information architecture · Role-based UX · Design systems · Responsive design · Product scalability
Designed once. Configured everywhere.
"Every user opened the same dashboard, regardless of what their job actually was. A payroll officer and a sales rep saw identical screens. I redesigned it as a platform, not a page — one framework, twenty-four modules, a different workspace for every role."
Scope
Stakeholder Interviews · Business Requirements · Product Audit · Workflow Analysis · User Pain-Point Analysis · IA · Role-Based UX · Interaction Design · Prototyping · User Testing · Responsive UX · Design System · Engineering · QA · AI Opportunity Assessment
IMPACT
45% fewer unnecessary widgets
30% faster access to daily tasks
4 → 1 navigation steps for key activities
24 modules supported by one dashboard framework
THE SHIFT
The brief was a visual refresh. The opportunity was a platform.
BEFORE
One dashboard for everyone.
18 portlets
Generic KPIs
No role-based priorities
Repeated alerts
Different modules competing for attention
When I started looking at the legacy Pronto Xi dashboard, I found a single, static landing page — every user, every role, every module, staring at the same generic layout regardless of what they actually needed to get done that day.
AFTER
One configurable dashboard framework
Role-aware content
Prioritised information
Reusablecomponents
Responsive layouts
Module + permission configuration
A role-based DASHBOARD with AI recommendations
Once the dashboard understood the user's role, permissions and context, it could also support intelligent recommendations. I extended the framework to surface a Pronto AI recommendation within the Sales workspace—helping the user understand which deal to prioritise and why.
Validated beyond one screen
I tested the framework across Finance, Payroll, HR and CRM, running roughly 3–4 rounds of testing per module across 5–6 modules. The validation focused on whether role-specific priorities, content hierarchy and workflows remained clear as the framework moved across different enterprise contexts.
OUTCOME
45%
Fewer unnecessary widgets
30%
Faster access to daily tasks
4 → 1
Navigation steps for key activities
24
​
The result was not a redesigned dashboard. It was a reusable product framework that could adapt to role, module, permissions and device without fragmenting the experience.
I turned a static landing page into a scalable workspace system—one framework, configured around the person, not the module.