Overview

Persona Design System

An iteration of Privy's open-source design system focused on reorganizing foundations, adopting newer Figma capabilities, and making the library lighter to maintain.

Platform

Internal design library

Role

Product Designer

Timeline

4 weeks

01

Context

The shared system behind Privy

Persona is Privy’s public design system: a shared foundation for designers and developers building products across the company.

After the first release, I continued the next iteration as the team became smaller and the library needed to catch up with current product and engineering needs.

02

Challenge

A system that was getting harder to use

The system had not been updated for a while. Some assets were outdated, several components had implementation issues, and the file had become heavier than it needed to be.

The task was more than a visual refresh: reduce the overhead, improve the components, and keep the existing ecosystem working.

03

Approach

Start with how the team works

I began by mapping the components, variables, and styles people were actually using, then reorganised the library around those patterns.

From there, I introduced Figma variables and slots, fixed component issues, and tested each pattern before publishing the update.

04

Outcome

A lighter library for everyday work

The result was a cleaner system that better matched the team’s current workflow and reduced the effort of maintaining shared assets.

Persona v2 gave the team a lighter library, a clearer structure, and foundations that were more useful for ongoing product work.

Selected UI Design

Animated Persona design system playground for testing components.

Component test playground

A playground used to test updated components in light and dark contexts before publishing them into the shared library.