work / reporting-hub
The Reporting Hub
A design system that made enterprise analytics feel designed
Worked with Solo designer · collaborated with the product & customer success teams, driven by customer feedback
- Came on as the founding designer for an early-stage team with paying customers but no design bandwidth; ran the audit solo and built the design system from scratch
- Customer success was weak because key information lived in docs; with the product deployed on client servers, no telemetry coming back, no chat support, the UI itself had to carry the knowledge
- Key decision: standardised on Bootstrap 5 and delivered design specs for every custom component, a common language the developers could actually build
The real problem
The Reporting Hub is a white-label Power BI portal built by a lean, early-stage team that already had paying customers, which is exactly why design kept losing to the roadmap. Three problems compounded:
- No design bandwidth. The team couldn’t focus on design while serving customers, so I took up the responsibility: a full design audit, findings presented with concrete improvements.
- Information invisibility. Customer success was weak because the answers existed, in the docs, but not where users were. And this isn’t a traditional SaaS deployment: the product runs on client servers, with no telemetry coming back and no chat support to catch confusion live. Whatever users needed to know, the interface itself had to teach.
- A fast-built stack. The web app had grown quickly, accumulating custom components. The redesign looked great, but needed a common language with the developers to ever ship.
Audit the product, make its knowledge visible in-context, and deliver a design system the existing team could implement and maintain.
WCAG-checked audit with prioritised improvements; key information surfaced as tooltips, hover-to-view and purposeful popups with visible cues; Bootstrap 5 chosen as the shared language, with design specs for every custom component.