PROJECTS

ROLE

PRODUCT DESIGNER

TEAM

MOCHI HEALTH

TOOLS

FIGMA

STORYBOOK

FOCUS

DESIGN SYSTEMS

INTERFACE AUDIT

COMPONENT ARCHITECTURE

DOCUMENTATION

Redesigning Mochi's internal facing design system and adding new components.

Problem

A growing product ecosystem without a shared design foundation

As we scaled across the provider, operations, and pharmacy products, teams kept designing similar chart, table, and data-heavy components in inconsistent ways โ€” creating growing design and tech debt. The original system grew reactively rather than by design. There were inconsistent styles across components, bloated configurations built to patch individual use cases, and layouts that varied from screen to screen.

Old design system

Key Challenges

Through UX research and collaboration with patients and internal teams, I narrowed broad usability issues into three core pain points that guided the redesign.

๐Ÿ‘๏ธ

Visual inconsistency increases cognitive load

Inconsistent typography, iconography, and spacing across sign-in, home, and notifications made the experience hard to navigate and understand at a glance

โ“

Inconsistent interactions break learned patterns

Similar actions behaved differently across the app, forcing patients to relearn how to interact with familiar features and creating unnecessary friction

๐Ÿ’”

Unclear communication can erode trust

Differences in tone and content presentation made information feel less cohesive. Unclear or inconsistent communication can increase anxiety and undermine patient trust

Goal

Create a scalable design system that unifies Mochi's existing product ecosystem while helping future product teams design, build, and maintain new tools more efficiently.

Color Tokens

Utilizing a two-tiered token system, we created primitive tokens for raw values like colors and spacing, and semantic tokens that mapped those primitives to meaningful and contextual roles across the design system.

Token hierarchy

Color system

Semantic color tokens

Components

I had ownership of creating an entirely new set of components for the operations portal, refactoring the product end to end and designing each component with slots to allow for maximum flexibility across use cases.

Atomic design system

Component parameters

Refactored ops portal

What was the outcome of all this?

The result was a unified design system adopted across all three internal portals. I led QA sessions with the design team to ensure consistency before handoff, then partnered closely with software engineers to implement components in code, using Storybook to document and validate each one against its design spec.

This collaboration consolidated dozens of redundant, one-off component variants into a single flexible, slot-based version, cutting the number of duplicate components in the codebase by an estimated 40%.