Back
Contributing to the Design System
July 2024
Researched and designed new drag-and-drop component for the organization-wide design system. Designs cannot be shared due to confidentiality reasons.
Researched and designed new drag-and-drop component for the organization-wide design system. Designs cannot be shared due to confidentiality reasons.
Objectives
Fill in the gap of missing component that was causing malpractice organization-wide
Cultivate a collaborative environment between the team and the firm's design system team, as well as contribute back to the wider organization to succeed together.
Process
Collaborating and getting aligned with the design system team
Propose requirements for the component and present to the design system leads
Includes industry and best practice research
Benchmark and prioritize key requirements for iteration 1
Create lo/high-fi mockups
Figma library planning
Outlining property and auto-layout structure
Dev handover
Challenges & How I overcame them
The main (and probably obvious) challenge throughout this project was ensuring I'm designing a component that makes sense for various use cases. Due to the nature of the firm where some teams may have 20 internal clients vs. other teams having thousands of daily external users, a thorough research of all possible variants of the component was crucial. Through this process I was also reminded that it is always data-backed/evidence-backed designs are scalable and usable while delivering intuitiveness.
Objectives
Fill in the gap of missing component that was causing malpractice organization-wide
Cultivate a collaborative environment between the team and the firm's design system team, as well as contribute back to the wider organization to succeed together.
Process
Collaborating and getting aligned with the design system team
Propose requirements for the component and present to the design system leads
Includes industry and best practice research
Benchmark and prioritize key requirements for iteration 1
Create lo/high-fi mockups
Figma library planning
Outlining property and auto-layout structure
Dev handover
Challenges & How I overcame them
The main (and probably obvious) challenge throughout this project was ensuring I'm designing a component that makes sense for various use cases. Due to the nature of the firm where some teams may have 20 internal clients vs. other teams having thousands of daily external users, a thorough research of all possible variants of the component was crucial. Through this process I was also reminded that it is always data-backed/evidence-backed designs are scalable and usable while delivering intuitiveness.