UI/UX, Design System, Figma, React, Data Visualization, Component Libraries
Product / Web App
The Challenge
Momentum's productivity platform was powerful, but it was a classic victim of its own success. Rapid feature growth over three years, with multiple product teams working in silos, had led to a complete breakdown in UI consistency.
The user experience was fragmented, developers were wasting time rebuilding the same components, and design debt was cripplingly high. The platform felt like five different apps rolled into one, and users were getting confused and frustrated.
The Solution
My solution wasn't just to redesign a few screens. It was to build a single source of truth for the entire organization: the new Momentum Design System.
My process was methodical:
UI Audit: I started by conducting a full UI audit of the entire platform, capturing screenshots of over 200 unique (and often redundant) component variations. This visual proof was the key to getting engineering and product stakeholders to buy in.
Build the Foundation: From the audit, I designed and built a new, scalable component library in Figma. This included everything from atomic elements (colors, type, spacing tokens) to complex, interactive components like data tables, navbars, and modals.
Document Everything: I wrote the initial documentation for the system, clearly outlining usage guidelines, "do's and don'ts," and accessibility standards. This ensured that everyone, from designers to new-hire engineers, would be building from the same playbook.
The Outcome
The impact of the new design system was immediate and measurable. By creating a single, shared language for our teams, we were able to:
Accelerate new feature development by 40%, as developers could now build with pre-vetted, reusable components.
Eliminate nearly 90% of our existing design debt, making the product faster and easier to maintain.
Cause a 30% drop in user-reported confusion and support tickets, as the new, consistent UI was far more intuitive to navigate.
Ultimately, this project wasn't just about making the product "look nicer"—it was a strategic move that unified our teams, streamlined our workflow, and delivered a measurably better experience for our users.
