MyData lets teams ask for analytics in plain language instead of digging through messy data. The idea worked. The interface didn’t. I rebuilt the core experience around clarity, control, and a design system that could scale with the product.
The platform’s concept was ahead of its time, but its execution held it back. Basic tasks like customizing a channel or setting a KPI took far more steps than they should have. Powerful features existed but stayed hidden, and a design language that had never been unified made the whole product feel improvised rather than built.
Replaced a fixed, one-size-fits-all dashboard with a homepage users can configure to surface the graphical reports they care about, not what the system assumed they wanted. Why it matters: Reduces time-to-insight; users land on relevant data, not a hunt.
Turned static permission tables into a visual, editable org chart. Admins drag and drop to assign roles and see reporting structure at a glance, instead of parsing a settings table. Why it matters: Makes an abstract, error-prone task (permissions) spatial and intuitive.
The old task manager was one long list sorted by date, with no sense of progress. Rebuilt with Pending / Active / Completed tabs, giving users an immediate read on where things stand. Why it matters: Cuts cognitive load; users scan a state, not a timeline.
Introduced a conversational UI where users chat directly with the assistant to generate, view, and download reports on demand, giving the platform’s core “ask a question, get an answer” promise a proper home. Why it matters: Makes the product’s smartest feature visible and usable, not hidden in a menu.
Settings had become a dumping ground: every option on one overwhelming page, so confusing that users regularly contacted support just to change a setting. Redesigned into logically grouped tabs (user vs. organizational, for admins), with clear labels, short descriptions, and a search bar to jump straight to what’s needed. Why it matters: Self-service replaces support tickets.
Notifications were dense, single-line text blocks with no visual hierarchy, making it hard to tell what was urgent, read, or actionable. Redesigned using a familiar app-inbox pattern (clear read/unread states, grouping, scannable message hierarchy). Why it matters: Borrows a mental model users already know, so nothing needs explaining.
