Atrium

Atrium was shipping fast, faster than its design system could hold: missing components, an inconsistent type scale, and primitives the team kept working around. I rebuilt the foundations, uplifted the visual language alongside the brand, and reworked how users move through the product as it scaled.

The product had outpaced its design system. Teams were forking components, the type scale wasn't holding, and the primitives weren't deep enough for what new features needed. The fix wasn't more one-off components, it was a stronger base layer everyone could build on, and a fresh look at how users moved through the product.

• Fill the gaps in the system

  Add the missing components and primitives and refine the type scale, so new features stop forking the system.

• Uplift the visual language

  Bring the design system in line with Atrium's evolving brand, so the product reads as one piece instead of patched-together features.

• Rework the flows as the product scales

  Revisit core UX flows to match how users actually use Atrium today, not how the product launched.

• Filled the gaps in the system: missing components, primitives, and a refined type scale that holds across surfaces.
• Uplifted the visual language alongside the brand and reworked core UX flows to match how users actually use Atrium today.