Our marketing and hosting tools suffered from inconsistent design and a fragmented user experience, creating frustration for users and inefficiencies for developers. We needed a scalable design system to unify our products with a cohesive visual and functional framework—one that could easily adapt to new features, acquisitions, and the multiple code languages in our ecosystem.
HAPPINESS: Achieve a 80% satisfaction score among designers and developers using the system within the first six months. Metric: regular surveys assessing ease of use, satisfaction with documentation, and overall usability.
ENGAGEMENT: Ensure at least 60% of all new feature development utilizes the design system components in the first year. Metric: % of new features or updates implemented with design system components compared to custom builds.
TASK SUCCESS: Reduce the average time to develop and implement new UI components by 30% within six months. Metric: Time tracking in Jira for development tasks before and after implementing the design system.
HAPPINESS: After 6 months, we achieved a 92% satisfaction score among designers, who praised the system’s clarity, ease of use, and well-documented guidelines. However, satisfaction among developers lagged due to the complexity of implementation and insufficient resources to fully integrate the system into their workflows.
ENGAGEMENT: By the end of the first year, around 55% of new feature development utilized design system components, nearly meeting our target. This adoption rate reflected strong alignment and enthusiasm within the design team.
TASK SUCCESS: Measuring the reduction in development time proved challenging due to the diverse nature of our development teams, each working on different products with varying coding languages, funding, and bandwidth.