đźšš

Case study · Sixfold / Transporeon · 2021-2024

Common UI

Common UI

After joining Sixfold, I quickly noticed the need for effective “design tools” while working with the team. Having previously built a design system at Pipedrive, I felt confident that I could create one here as well, even while focusing primarily on product design. After conducting a quick inventory of Sixfold’s applications, it became clear which components required the most attention, and I started by aligning those.

The initial result was a design system that leaned heavily toward the design side. However, over time, as the necessary roles were filled within the company, we were able to develop a system that worked equally well for both designers and developers. One of the greatest strengths of the design system we created was a well-thought-out and tested “Token” system, which enabled the company to quickly rebrand parts of the application, a crucial feature given the frequent acquisitions.

Here, I owe immense gratitude to Mihkel Eidast, without whom this success in its current form would not have been possible.

Check out the storybook for the design system at design.sixfold.tech

Component design specification

Component design specification

After determining the need for a component the work began on creating a design and specification sheet for the component.

Variants, parts and behaviour

Variants, parts and behaviour

More complex components were specified in detail and given detailed input for the design engineer.

Project

Common UI


Company

Sixfold / Transporeon


My role

Product Designer


Team

  • Henri Normak
  • Mihkel Eidast
  • Sander Värv
  • Kristjan Napa
  • Hardi Brenner