NAVIGATING ORGANIZATIONAL SYSTEMS
Component Library
To improve the efficiency of client implementations, I led the design effort for creating a component library to standardize design elements and significantly reduce work for UI developers; this initiative involved navigating organizational leadership dynamics and creating influence.
High points:
• Reduced implementations by 88%
• Created a more consistent and efficient design process
• Established relationship between Design and UI development team
Adobe XD
Excel
Figma
Miro
ROLE
Product Designer
TIMELINE
Jun 2022 - ongoing
SOFTWARE
THE PROBLEM
Where It All Began
Friction between design and development
I joined a previously established team of one designer and three UI developers. The groundwork was laid to define the problem, but little work had been done to begin designing components. Friction existed between design and developers due to lack of shared language, systems, and hand-off process.
Client implementations took too long
The existing process took an average of 4-6 weeks to complete. This created a bottleneck at the development level, which caused friction between clients and project managers, and reduced engagement.
Other issues included:
• Revenue remained stagnant due to lack of resources and capacity.
• Designs were inconsistent across different implementations due to lack of reusable components.
• High development initial effort required for each new client, with repetitive tasks.
• Difficult to maintain as updates needed to be manually applied to multiple instances across the platform.
THE PROCESS
What We Did About It
Our strategy was multi-faceted yet coordinated
I led the design development of the component library in coordination with the UI team. This effort aimed to:
• Reduce the implementation time for each client.
• Increase the capacity for more projects, therefore increasing revenue.
• Standardize existing design elements and create consistency across products.
• Minimize manual, redundant work for UI developers.
• Create a shared development process and language for both designers and developers.
THE SOLUTION
Get to the Core Issue
The end result of a token-based development system
By streamlining the implementation process, cutting timelines from 600 hours to just 70 hours—an 88% reduction, my team able to take on more clients, due to freed up capacity, develop more consistently, and decrease redundancy. This solution enhanced client satisfaction, portal usage, and long-term scalability, and ultimately created a more consistent and efficient implementation experience.