- 100% · Figma adoption across the company
- 86% · Legacy code removed
- 8.7K · Community library downloads
A design system for a career platform with 3 million users
Wanted is a career growth platform with 3 million MAU. On the back of its recruiting business, it kept opening new businesses: career content, community, AI and freelancing. The design system was what kept that growth from piling up design debt, and let many teams ship the same quality of UX faster.
When I joined, foundations like colors, icons and buttons were already underway. My job was to diagnose the system and grow it into a better one.
The system existed, but almost nobody could see it
The design system was built and shared in Sketch and Zeplin. Components carried little information, and only a few people could open the source files. There was also no way to see where or how the system was used. I wanted to start by checking usage, and that data simply didn't exist.
To spread and grow the system, people first had to see it, understand it and get comfortable with it. So I decided to move every team's design work to Figma, which had what the system needed to grow: the cloud, real-time collaboration, libraries and component usage tracking.
Obstacle 1: persuading a company to switch tools
The Sketch system had been built through many rounds of trial and discussion. Switching would change how every designer and developer worked, so for my first few months I kept working in the existing system while mapping the pros and cons of both tools. I compared them on features and also on people and cost, then tested and made the case.
The key to persuasion turned out to be fun. A new internal sharing program let anyone teach a skill to colleagues, and I used it to run two sessions.

- Make emoji with Figma: people loved using custom emoji in our messenger, so I ran a session where anyone could design an emoji in Figma and add it to the messenger. While playing, they picked up Figma's basics and saw why it was useful. Article (KR)
- Figma for designers: to show it worked for real product work, I ran a series of in-depth onboarding sessions for designers.
After the sessions, I kept a #figma_study channel running so anyone could get answers quickly.
Obstacle 2: changing the wheels on a moving car
Even with buy-in, product teams kept shipping with legacy assets to hit their goals. I designed a migration that would cost those teams as little time as possible.

- I moved every Sketch file to Figma and refined the system components to fit.
- I held a 1:1 migration meeting with every product designer to review their files together and adjust details for their team.
- With developers, I replaced icons, colors and typography in the product with the new system, removed 86% of the legacy code and cut icon file size by more than half.
Beyond design: a bird's-eye view that saves everyone time

Onboarding alone wasn't enough. I wanted a project that actually saved people time, and that became the Bird's Eye View. It combined Figma's openness with Wanted's clean event data to show the main screens and data flow at a glance, so anyone planning a service could understand the product quickly. Article (KR)
Obstacle 3: staying off the "important but not urgent" pile
The system I started alone became, over two years, a project run by a four-person design platform team. But infrastructure easily becomes "important but not urgent" and loses out to product launches. Keeping its priority took more trust, inside and outside the company.
So we released part of the system as a library in the Figma community. It was featured in Monthly Design, Design Compass and other media, and it is the most downloaded Korean design system in the community. Wanted Design Library

I spoke about the design system at Figma Leaders Meetup, Inflearn, Notefolio, Wantedlab and Design Spectrum. The talks fit Wanted's brand of supporting people's careers, and they told the industry what we had built. Slide deck
Where it stands: a design tool for everyone
- Figma adoption across the company · 100%
- Average design system usage · 38%
- Community library downloads · 8.7K
- System usage measured in Figma · July not measurable → October about 16,100 → January about 380,000
A system whose usage nobody could see became one used about 380,000 times a month, within half a year.

