Compound design system

Phoenix Group

2022

Design System

Pink Flower
Pink Flower
Pink Flower

The challenge

A growing UX team and several squads were shipping in parallel, creating inconsistent UI and design debt. This slowed delivery, confused users, and duplicated effort.

My role

Supported the design system lead designer
Owned audit, definition, Figma libraries, documentation, adoption, partnering closely with engineering and content.

Impact

  • Improved consistency: one single source of truth for multiple products.

  • Increased efficiency: designers and developers stopped re-building page layouts.

  • Scalable onboarding: new team members got productive faster with clear, living documentation.

  • Wider adoption: workshops and guidance raised alignment across cross-functional squads.

What I did

  • Audit: inventory of live components and patterns. Identified duplicates and gaps.

  • Defined foundations & components: page layouts, navigation, cards, banners, content hierarchy, designed as reusable, responsive variants.

  • Built in Figma: created structured libraries with clear naming, states, and usage notes.

  • Documented for humans: wrote practical guidelines and examples in a documentation tool (e.g., Supernova) so designers and developers could use.

  • Partnered with devs: aligned on technical constraints and mapped designs to code equivalents on the website.

  • Drove adoption: ran workshops, playbacks, and office hours to support roll-out across squads.

Key design decisions

  • Design for variants: components built with flexible props (content density, media, CTAs) to cover real use cases without re-creating patterns.

  • Clarity over decoration: guidelines focus on content hierarchy, states, and behaviour.

  • Document where it lives: every pattern includes when/why/how, examples, and do/don’t, so teams can self-serve.

  • Ship while standardising: supported active product work while gradually retiring legacy components.

Constraints I navigated

  • Legacy patterns: consolidated without a full rebuild.

  • Many stakeholders: aligned brand, content, product, and engineering on standards.

  • Time pressure: delivered value incrementally so squads could adopt without slowing existing roadmaps.

This case study is part of my public portfolio.

Some of my most impactful projects are confidential, I can share them privately on request.