I led the transition to Figma as an opportunity not just to migrate, but to rethink the system entirely. Rather than carrying over outdated patterns, I rebuilt components from the ground up.

​

We began by auditing existing products to identify inconsistencies, common patterns, and opportunities for standardization. From there, I defined a core visual language—establishing typography, color, spacing, and interaction principles that could scale across a wide range of use cases. With that foundation in place, I designed a library of reusable components, each built to be flexible, accessible, and grounded in real product needs.

Each component was documented with usage guidelines, states, and behaviors to ensure clarity and ease of adoption. Collaboration was central to the process. I worked closely with engineering to validate components in development, ensuring design and implementation stayed aligned. Rather than a one-time handoff, the system was treated as a living product—continuously refined through feedback and iteration.

​

The shift made a noticeable difference. With a more accessible and thoughtfully structured system, teams began to adopt it more naturally in their day-to-day work. What was once underutilized became a core part of the design process.

Brand colors were redefined into a scale of tints and shades to keep consistent color usage.

​

The button system was designed to create clear hierarchy, consistency, and ease of use across wm.com and its applications. I established a set of primary, secondary, and tertiary styles to guide user attention and reinforce action priority, ensuring that the most important actions are always visually distinct. Each variant includes defined states—hover, active, disabled, and focus—to support accessibility and provide consistent feedback across interactions. By standardizing buttons across the system, teams were able to make faster, more confident decisions while maintaining a cohesive user experience.

​

A consistent typescale was defined to be used on all text on the page establishing hierarchy between large bold headlines and smaller body text.

Over time, the design system brought a sense of alignment back to the product. What once felt fragmented became more cohesive both visually and functionally.

Teams were able to move with more clarity and confidence, relying on shared components instead of starting from scratch. This reduced friction between design and engineering, improved efficiency, and made collaboration more seamless.

For users, the impact showed up in the details—a more consistent, intuitive experience across wm.com and its applications.

More importantly, the system created a foundation for what comes next. As the product continues to grow, it now has a framework that can scale with it—supporting new ideas, new features, and a more unified experience moving forward.