Skip to content

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.

Primary100 to 500
  • 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.

UI standardization

Reused components, and where their styles differ.

TableColumn header stylesNetwork Shield, Data Map, User Authentication, Approvals
AccordionPaddingAccess Portal, Data Map suggestions, Approval requests, Config, Data Labels
TagFilled vs outlinedData Map, Data Repo Details header
ButtonStatesFilter and Advanced buttons in the Data Access Portal
Radio buttonLabel font weightUser Authentication access rule modals, Policies add and edit
IconsOutline vs filled, sharp vs roundSide nav, inputs, selects, accordions
From my audit of the product UI.

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.

Buttons
PrimaryThe most important action, once a screen (modals and side panels aside).
SecondaryThe most used. Alone, or beside a primary: Cancel, Filter, Sort.
TertiaryActions the other two don’t cover, like Remove filters.
LinkGoes to another page, in a new tab.
DestructiveDelete, remove, undo, disable.
IconSmall spaces, like table rows and inputs, with or without a border.

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.

Screen width1440px
v1 max 1024976px of content, centred
v2 max 12801232px of content, centred

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.

Changelog
TYPECOMPONENTCHANGE
June 22 2024
CHANGED
Data table
Rows can expand to show detail in place.
ADDED
Access restriction
Patterns for showing which conditions gate a repository.
April 18 2024
CHANGED
ACTION
Typography
One rule for leading everywhere, replacing the values each screen had set for itself.line-height: 1.5 x font-size
FIXED
Accordion
One padding value everywhere. Access portal, data map suggestions, approval requests, config and data labels each had their own.
CHANGED
Button
One set of states across every variant. Filter and Advanced in the data access portal were each carrying their own.
FIXED
Radio button
Label weight was inconsistent between the user authentication access rule modals and the policies add and edit workflows.
CHANGED
Icons
Outline only, one corner treatment. The side nav, inputs, selects and accordions had been mixing outline with filled and sharp with round.
CHANGED
Table
One column header style. Network shield, data map, user authentication and approvals each had their own.
CHANGED
ACTION
Tag
Narrower, and the type moves to Body-2. Anything relying on the old width needs re-checking.max-width: 250px -> 200px
DEPRECATED
Tagfilled
Use the outlined variant. The data map and the data repo details header had been splitting between the two.
ADDED
ACTION
Badge
Split out of Tag, which had been doing both jobs. Takes the renamed Badge type.font-weight: Bold -> Semi-Bold, line-height: 16 -> 18
CHANGED
Text input
One label convention, descriptive rather than instructional, and one required indicator.
ADDED
Code blockinline
Connection strings, tokens and queries had been set as body text.
ADDED
Toast
Replaces the confirmations each workflow was writing for itself.
ADDED
Tooltip
One component, replacing the title attributes and hand-built popovers in use.
ADDED
Stepper
For the multi-step configuration workflows.
A change to a component reached every project using it, and the changelog showed what had changed and why.

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.