While transitioning to work with different team, we had to shift all our design assets from Sketch to Figma and that came with a challenge of creating a new file structure from the ground up. Here’s an overview of various file structure we experimented with in the beginning and then the final file organization.

A few more things that I initiated and led for features used by 100,000+ users-

Created &amp; improved colors, typography, spacing and loader styles

 Scaling a design team comes with the challenge of onboarding new members and being an advocate for the system constantly! I was blessed to have team members who supported my initiative and helped me create an aesthetic and consistent design system out of sheer chaos and complexity!There were a lot of experiments, and long end-of-the-day sessions involved in designing a workflow to make collaboration easy for new designers. It took an average of 2 months to onboard designers for them to successfully contribute to the design system on their own - and I consider that a great win :)

Created onboarding material on Notion to familiarize designers with file structure

Weekly component design audit &amp; critique meetings

Decentralising knowledge by giving sole component ownership to designers

Regular workshops and sessions to just.. create &amp; learn things together :)

A couple of designers regularly critiqued about getting lost in the design system and were clueless about half of the things. In the span of 2 years, my responsibility was to experiment with ways to communicate our intent of the components and the library itself to designers using varied types of documentation. Here’s a look at various documentation we initiated and scraped as opposed to “a single mold works for all” strategy :)

A huge part of the design system involves communicating our designs and intent to our outstanding team of developers. Along with giving them new updates on the design system, we also focused on developing relationships and rapport for seamless collaboration by-

Conducted 2 anonymous surveys which resulted in 80% improvement from previous handoff process

Brought out key problems through cross-collaboration vs one way updates

Creating custom learning material, handoff guidelines and nomenclature to encourage consistent usage among internal teams

The surveys brought another interesting insight - how do we make sure our designs were translated perfectly into the developed version? Our team ran a brainstorming session and included an audit and testing cycle after every design sprint. Most of the large companies had a similar process although, it was interesting to come up with our own method through trial and error after a year of running sprints within the small teams.

Scaling Lyearn products with 2x speed by bringing consistency in visual components and encouraging collaboration through design system

Design System