Stepped up to lead cross-functional efforts to develop a design system
Endpoint: great for engineers, but limited adoption as it always required logging into your Wealthfront.com account; hidden behind the main site rather than an internal resource, which we actually had a engineering-centric version that was much more accessible
https://s3-us-west-2.amazonaws.com/secure.notion-static.com/d64b5f36-d369-4f22-9298-f855e0c9fac4/PatternLibrarySystemWealthfront.pdf
PLS Google Doc: completed and updated to v4, which involved a lot of meaningful audits and cutting out of extraneous colors, type/spacing sizes and component variants
Spritesheet conversion: completed ~90%; project was abandoned due to the departure of the original 2 members of the PLS cross-functional team
Sketch library: completed ~60%; project in limbo as it was observed that the team only used ~20% of the library components, and most of their workflows continued with creating variations of separate assets they had used in their previous projects
After the departure of the original PLS team, I became the de facto leader
Rallied a new cross-functional working group to determine direction of PLS
Instituted bi-monthly "PLS Office Hours" to encourage cross-functional project teams to present components at any stage of development for feedback and visibility for cross-pollination with other projects
Collaborated to create a Guidelines doc and Vision presentation to align the company on the new team's efforts:
[WiP] PLS Guidelines: initial write-up on how a design system should be approached
[WiP] PLS Guidelines: initial write-up on how a design system should be approached
[WiP] PLS Vision presentation that unfortunately was never given due to shifting company priorities at that time
Initiated effort for the Design team to participate in Figma's Orgs (beta) program as a possible replacement of our clunky Sketch+InVision workflow