In 2017, I saw a need for a design system to support our growing team. I took the initiative to establish the core principles and foundations on my own time.

My Role

  • Initiated the project in 2017, setting the first foundations and principles.
  • Enlarged the system to encompass UX patterns and workflows.
  • Led a team of designers actively contributing to the design system.
  • Results

  • Increased consistency and delivery speed.
  • Developed a UI kit library with hundreds of components.
  • Lead the tech team to a component library implementation.
  • Squad projects always incorporate UX patterns and UI components in solution discussions.

  • This was not just a quest to create a set of static guidelines, but a living, evolving framework that would serve as a shared language for our growing team. Many years later, we've created more than just a UI kit library with components; we've created a culture of consistency, collaboration, and efficiency that permeates every project we undertake.

    The design system was built on a scientific approach, with rules defined for elements like typography and colour shades based on their luminance. It wasn't all about strict rules – we kept a designer's eye on things and made adjustments based on how it actually worked.

    As the team expanded, the design system grew with it. New contributions not only came in the form of interface components but also in the form of best practices.

    UX patterns, and guidelines on feedback, handoff, and tone of voice. These articles and documents, which now makeup our design manifesto, ensure a consistent approach to problem-solving and communication across the team.

    One critical milestone was securing dedicated time to work on the design system.

    With 20% of our time now allocated to this project, we've seen a significant increase in production speed and a reduction in accumulated debts.

    The design system's impact is not confined to the design team. Our tech team is now implementing a coded counterpart to the UI kit library, linking the two through versioning. This means that we have a clear understanding of which versions of components are implemented and can select component versions for our mock-ups accordingly. This clarity is invaluable for our tech and QA teams as they know exactly what is expected for implementation and testing.

    Finally, the design system has become an integral part of our solution discussions. As we work in squads, the system's standards and components are always front and centre, informing our decisions and ensuring product consistency.

    Building a design system is a continuous effort. We are constantly iterating, adding new components and patterns, and refining existing ones based on user feedback and evolving design trends. We are aiming to implement a KPI system that allow to better track this evolution and take data driven decision.