Building A Design System: Aligning Design And Engineering

Being the only designer at Zen Locum, there were imited resources to dedicate to starting a new project. Still, we deemed a design system necessary to eliminate existing design inconsistencies and improve future workflows for both designers and developers as the company scales up.
Client
Zen Locum
Category
UI Design

Zen Locum is an online platform that directly connects locums to stores in their area, making it quicker, easier, and cheaper for stores to find supply work.

After being promoted to lead designer of Zen Locum, I embarked on the journey of learning a new product with a new customer base of over 8,000 active users.

As the only in-house UX designer I was on my own, working on a 2 year old product that had no style guide or brand guidelines to follow (not to mention a light mode and dark mode for both web and native applications. No design files, no design team, not even a clear job description. I got started in building a UI kit right away with the aim of strengthening consistency between design and engineering.

Let's Get Started...
What problem are we facing?

Component Audit

In order to get an overview of all the use cases we need to cater to, it is important to audit existing components in our product. We used Brad Frost’s interface inventory guideline as inspiration as we conducted a 2-hour audit within the team. We were each assigned areas of the web application to go through and make note of any design inconsistencies we noticed. At the end of the workshop we would each share our findings with the team.

As a result of this exercise, we identified a lot of inconsistencies in our design assets, which only proved the need for a more systematic approach to documenting, communicating, and maintaining our design system.

Below are some examples of the components screenshots we came up with after this exercise:

From this exercise, we felt it most useful to start with web components first as our desktop application was most frequently used yet accompanied with a cluttered codebase.

This was a workshop with the tech lead, senior developer, PM, and designer to uncover where to start.
Defining the problem...
What do our users need?
Building the designs...
Bringing our ideas to life

Design Exploration

We decided to focus first on the foundational elements (atoms) of our design system, such as colour palettes, fonts, grid, spacing, buttons, etc., and then move on to more complex components over time. We created components on Figma, taking dimension inspirations from existing components in the codebase.

Some of the activities at this stage involved:

  • Researching other design systems and interfaces for components common practices and inspiration.
  • Analysing the instances and use cases captured during the audit and ideating on the solutions that serve our goals best.
  • Unifying: we merged different variations of components to leave only the essentials. For example, we limited our colour schemes to a maximum of 9 shades for each hue and all the excessive variations were matched and merged with the decided upon schemes based on proximity. Below is our final colour palette:

Frequently-Used Components

Once the foundational elements of our design system were established, I started plotting out the most frequently-used components of both our light and dark mode for web.

Some principles we followed:

  • We tried to make our components responsive with the auto-layout Figma feature, so we could reuse those components when designing for different devices or layouts.
  • We designed to cover all scenarios, or “states” in the system: hover, focus, filled out, error, and disabled state.
  • Each component we designed with accessibility in mind. We strived to comply with WCAG AA accessibility standards. We used the Stark Figma plugin to ensure we were compliant with all components.

When the Variants feature was introduced to Figma, we started using it to combine variants into component sets with custom properties and values. Using variants makes components easier to maintain, browse and swap through the sidebar menu.

‍

Testing our hypothesis...
Are we moving in the right direction?
In conclusion...
What we achieved, challenges, and next steps

Keeping designs up-to-date

With this project, we strived to create a robust design system that was adapted for a scaling product and a growing team. With this, comes necessary documentation and integration software to ensure our design system stays up-to-date with the codebase.

We used Zeroheight, a platform that integrates with Figma and allows product teams to create and maintain web-based design system documentation. This allowed all components created in the Figma design system to have an in-depth written documentation attached to it, (including best practices, guidelines, breakpoints, and accessibility guidelines).

Our talented development team then set up a component repository using Storybook, a tool that allows to create an interactive pattern library for code in isolation and supports all the popular frontend frameworks. This allows any changes made in Zeroheight, or Figma to reflect in Storybook for these components to be easily kept up-to-date and re-used.

Due to privacy reasons, this is not a screenshot from the Zen Locum component repository.

Moving forward

The design system is an ongoing project. We iterate, change and learn a lot in the process. So far, we have a set of basic components ready, which has been game-changing for our team in terms of efficiency, as well as consistency, and standardisation.

Some of our team’s next steps include:

‍

More work
Building A Design System: Aligning Design And Engineering
Read case study
Accessibility-Driven Design Challenge: Redefining Communication in Healthcare
Read case study
Optimising User Experience and Searchability
Read case study