Cyral Design Style Guide
One reference for Cyral’s product UI, built between features
From styles each engineer chose alone to a documented system the whole team built from.
- Role
- Lead Designer
- Team
- Cross-functional, 6
- Timeline
- Aug 2021 to Aug 2024
Cyral sells data access control to enterprise security teams. Its first year of product UI was built by engineers working from low-fidelity wireframes in Google Slides, each making their own styling calls. I joined as the first and only designer, with no design system, no component library and nothing written down to hand anyone.
- Primary 100: #E6F6FF
- Primary 200: #ABE4FF
- Primary 300: #26459E
- Primary 400: #393D74
- Primary 500: #061748
Problem
An inconsistent UI with no shared standard
After a year without a reference, type, colour, spacing and corner radii all varied from screen to screen, often by values too close to tell apart. New engineers learned which styles to use by asking colleagues, which slowed everyone down.
Reused components, and where their styles differ.
Solution
Standardize whatever is shipping, one feature at a time
I was hired to design prioritized features, so there was no time set aside for a system. I built it alongside them instead, defining the styles each feature needed and fixing older screens when they came up for a refactor.
Foundations first
Type, colour, spacing and radii came before any component. Line heights were set to one and a half times the font size, and each text style was given the colour it should be used in.
Then the components in heaviest use
Tags, buttons, inputs and tables were the most reused and the least consistent, so they went next. Each got its states and usage written down, and tickets to bring the code in line.
Designing for wider screens
The UI had been designed at a single size. I moved pages and components to a maximum width with set padding, first 1024 and later 1280, so layouts held as screens got larger.
Iteration
The system grew with the product
Over three years the work was mostly small changes to existing components, and new ones added when a feature needed them. Engineers built reusable components from the file, and new hires could learn the front end from it without someone walking them through.
Reflection
What I learned
Explain decisions in terms others care about
Getting buy-in at a startup meant tying each design decision to what it saved engineering or the customer. That was what earned design a place in product discussions.
Write it down for whoever comes next
The guide worked because engineers could use it without me. Documenting usage alongside each component made it something to build from.