Skyler Tse

It’s Skye!  I’m a product designer that builds
durable design systems and research-led
experiences
for complex products.


back

Product Desgn & Sys  /  
IndustryDemo Brand Library

Industry Demo
Brand Library (IDBL)


A dynamic repository that complies comprehensive Studio industry guidlines—covering logos, buttons, UI elements, etc.—to facilitate effortless integration into project creative files, and provide consistency across all Studio deliverables.



42.5k components implemented, 60 teams worldwide, across 20+ industries, all in 1 Library.
Salesforce QStudio / Demo Studio
New York City  ID# 0722-1224
Figma Library 2 years
Project Lead & Designer
Figma, Photoshop, Illustrator
Industry Brands
Published Library Components
Brand Hub






Here, let me catch you up!

The Industry Demo Brand Library (IDBL) is a centralized Figma ecosystem that solves a decade-long problem of scattered, legacy brand assets across QStudio and Demo Studio. As the deisgn lead, I built this single source of truth to curate, standardize, and deliver all components directly within designers' workflows, eliminating inconsistency and inefficiency.


 



ChallengeThis challenge was compounded by the sheer scale of historical work. The studios had been generating brands since the early 2010s, with assets created by a revolving roster of designers. This resulted in a deep well of legacy work—scattered across obsolete platforms and created with outdated standards. Designers were forced to act as digital archaeologists, spending excessive time just to find, verify, and manually adapt old assets for modern use, introducing risk and inconsistency into every project.


Breakdown As the lead designer for the IDBL project, my mission was to design and build a dynamic, self-service repository directly inside Figma that would end the cycle of hunting and guesswork. This would free out more time for designers to focus on backlog or another project. 


The solution was dissected into 5 parts:

①  Audit, consolidate, and modernize over a decade's worth of disparate brand assets into a single source.

② Establish consistent, and clear current standards for all brand components.

③ Facilitate effortless integration with Figma system along with how-to guides, do’s and don’ts, faq, etc.

④ Support users with supplements like slack help channel, and hands live enablement.

⑤ Designate a council that provides designers an opportunity to take on product leadership roles with quarterly maintainence and innovation. 


BeginningMy process began with understanding the full scope of the problem—that includes interviewing previous designers, documenting thier old teams various brand files and drives, and reaching out to upper leadership for access and permissions. I had two designers on my project that helped with collborating a comprehensive audit, sifting through a decade's worth of accumulated assets. This includes sorting and reorganizing them thru spreadsheets, and the current team’s google drive. 
About 2 quarters was spent just on huddling, identifying old assets, chasing down dead ends, and filtering viable and feasible rennovations. 

This wasn't just about collection—it was an act of curation.

While the other designers jumped on creating a home in Google Drive—various file types like PDF, JPG, Balsamiq, Sketch, InVision—for all these veteran assets we found, I took ownership of assessing, selecting, and thoughtfully modernizing core UI components and brand elements within Figma. This way it would ensure that the assets were not only historically accurate, but functionally relevant for current projects. The goal is to build
a system where the resources are all at the same level, and not missing a button component here, or missing a color variant there. I aimed to have all brands conform unanimously and stuctrually as assets, but remain individual as brands in their respective industries. 

Now armed with this audit, I centered the solution on the “frustrated designer”. Their pain points—wasting hours as "digital archaeologists" to track down and decipher outdated specs—became the core user story.

As the overall design departments continued to utilize Figma as the core design software, and the number of team designers on an uptick, it became clear that the key strategic decision would be to build the library natively within Figma, and to make it the authoritative home for every brand, past and present, eliminating the need to ever leave the design environment.


From this strategy, I designed a comprehensive, self-sustaining ecosystem within Figma, where the master file would level rationalization just as important as organization. This also establishes, single, updated standards for logos, buttons, and UI elements, to finally resolve years of version discrepancies. 


To ensure immediate usability for the primary users, I designed an intuitive welcome page with a clear directory, providing instant access to all brands. 





Understanding that adoption relies on clarity and support, I also embedded learning directly into the library—including practical Dos/Don'ts guides that addressed common legacy pitfalls—and created a resources hub. 

Top left: Directory, Top right: Do’s and Dont’s, Bottom left: Enablement Videos, Bottom right: FAQ


Finally, to ensure longevity, I established a "live document" model with a clear update cycle, transforming the IDBL from a static project into a maintained system.


Ever-changing pattern
F

a



TakeawaysA

Postitive Sentiments on Profiles“More user-friendly than what I’ve been dealing with for SW [launch 1]...and you bring in some of the stuff I was familiar with for Solution Central.”
- Diana, Senior Visual Designer

“It’s very similiar to what I would do in Solution Central...it covers what I need.”
- Vanessa, Senior Demo Architect, FINS

“Discoverability, quick and easy, like on my profile, my content [and] features are there...how easily I can leverage that feature.”
- Vamsidhar, Lead Product Manager, Data Cloud

“Really easy to manage and...not take much time to make sure your stuff is up to date.“
-  Tom, RFP Manager

End of Project Preview
Oh dang, you’ve hit the end of the story!

But don’t worry, this is the tldr version since some of the contents are restricted—there is much more in the longer version just waiting to be heard, so don’t be shy to connect!