Yevgeniy Belov

Getting three teams onto one design system during a React migration

Separate front-end teams built CloudGuard’s domains with no shared standards. I built a design system into the move to React, so unification came with the migration.

Unification example / Buttons

Role
Sole UX/UI designer
Collaboration
3 front-end teams
Scope
UI audit, shared patterns and design system in code
Timeline
3 months
Summary

Summary

Challenge

Separate teams built CloudGuard’s domains with no shared standards, so the interface looked and behaved differently from one area to the next.

My contribution

I audited recurring patterns, built the design foundations, assessed third-party components and worked with front-end teams to bring them into the product.

Solution

One design system, delivered through the move to React, with third-party components for complex controls.

Impact
3 of 3 teams on the same design system
~80% of major screens aligned
Rebranded easily to Check Point’s new style guides
Fewer UI bugs especially in the data grid
Context

Context

CloudGuard is Check Point’s cloud security platform, spanning posture management, network security, identity, workload protection, and more.

Three front-end teams built these domains, some owning more than one, in AngularJS or React, with no shared standards to work from. Every team solved common interface needs in its own way, and the product was moving from AngularJS to React.

Problem

Problem

CloudGuard’s interface looked and behaved differently from one product area to the next.

Reframing the problem

How can separate teams build one consistent product?

Constraints

Constraints

  • One designer, new to the domains, across a large product
  • The product was mid-migration from AngularJS to React
UI audit

UI audit

Method

  1. Capture recurring UI elements — I walked through every product area and recorded the elements used.
  2. Group by purpose — I brought together elements that do the same job.
  3. Compare visual treatments — I identified where the same job was handled differently across the product.
CloudGuard audit inventory with captured screens arranged in columns by product area
Only a small part of CloudGuard: a sample of captured screens, grouped by product area.

Findings

Symptom

Actions with no clear hierarchy

Primary buttons came in seven colors, one form had three filled buttons side by side, and “add” was worded five ways.

Primary buttons: 7 fills across 7 areas
Symptom

The same control, rebuilt per page

Six tab styles, toggles as both switches and pills, three ways to label a field, four table headers.

Tabs 6, form controls 7, tables 4 variants
Symptom

One meaning, many visual languages

Severity, the key signal in a security product, appeared in six forms: colored text, filled badges, pills, flags, labels and colored percentages.

6 variants across 4 areas
Symptom

Detail opens in a different place each time

An object opened in a drawer, a tab, a side panel or a modal, depending on the area.

Across 6 areas
Symptom

Meaning carried by color alone

Status was mostly an unlabelled icon; severity and compliance relied on red, orange and green.

Status: 4 variants across 5 areas
Symptom

Missing states

Two loading treatments, one designed empty state and no error states.

4 instances in 57 screens

Evidence

Navy / dark

  • + ADD NEW Assets
  • VALIDATE PERMISSIONS Assets
  • RUN Events
  • TEST Posture Management

Blue

  • Suggested Fix Assets
  • NEXT Posture Management
  • SAVE Settings
  • GET ACCESS FOR ALL 2 SERVICES Network Security

Pink

  • VIEW RESTRICTED POLICY Identity

Mixed fills in one form

  • DELETE (orange) · CANCEL (purple) · SAVE (navy) Intelligence

Destructive red

  • YES Intelligence
Approach

Approach

Fix the UI first, structure later

Problem
The audit revealed information architecture, navigation and UI consistency issues. As the sole designer and new to the project, I couldn’t address them all at once.
Decision
I addressed UI inconsistencies first—action labels, controls, tables and forms—using shared patterns, and left information architecture, navigation and user flows for later stages.

Unify through the React migration

Problem
Separate teams needed consistent visual rules while the product moved from AngularJS to React. Aligning individual screens would leave those rules maintained in separate places.
Compare the options
Direction A Fix the existing designs

Align existing interfaces in place, updating their components and styles wherever they are defined.

B Chosen Build a new system

Create shared foundations and a CSS layer for screens moving to React.

C Adopt an established library

Start with an existing component library and adapt it to CloudGuard.

Fits the move to React Partly: Existing styles can be aligned, but each source needs parallel updates during the migration Yes: Screens moving to React can be built on the shared styling from the start Partly: Some libraries suit React; styling consistency and adaptation effort would need evaluation
Keeps teams aligned over time No: Each interface keeps its own styles, so they can drift apart again Yes: One shared source for the visual rules, used by every team Partly: A shared library sets a baseline, but each adaptation can drift
Starts with broad component coverage Partly: Starts with the components already in the product; audit gaps still need to be filled No: Coverage has to be designed, built or integrated, and maintained Yes: An established library provides a broad starting set, though gaps remain
Freedom to fit CloudGuard’s workflows Partly: Existing implementations can be adapted, though their structure may constrain changes Yes: Foundations and components can be designed around the product’s requirements Partly: Specialized workflows may require customization beyond the library’s patterns
Limits replacement work Yes: Keeps components that meet the shared standard and replaces only the rest No: Requires creating the styling system and adapting existing interfaces to it Partly: Some components may fit; others need mapping to the library or replacing
DecisionPreserves existing implementations, but leaves them disconnected. Fixes must be maintained across separate sources, allowing the interfaces to drift apart again.Gives us control over shared visual rules as screens move to React. Requires building and maintaining the system.Provides ready-made components, but consistency would depend on how far the library could be adapted to CloudGuard.
Decision
I built a custom design system and made it the styling foundation for screens moving to React, so unification came with the migration rather than as a separate redesign.

Use third-party components for complex controls

Problem
Front-end teams were building and maintaining complex controls in-house, including the data grid.
Evaluation
I shortlisted components that had the features CloudGuard needed, checked how actively each project was maintained, and assessed how easily we could apply our design tokens to match our style guide. I asked front-end developers to try the candidates and assess their fit with our architecture and the clarity of their documentation.
Decision
For the data grid, I recommended AG Grid and secured the VP of R&D’s support to replace our internal grid. AG Grid handled the grid behavior, and our design system supplied the styling.
Solution

Solution

I brought recurring patterns into one shared system: action labels, sentence case, tables, forms, modal actions and icons.

I built its foundations in code: design tokens, Tailwind CSS utilities and CSS components. Screens moving to React used them, with thin wrappers around third-party components. Visual decisions lived in the tokens, so one change reached every screen built on them.

Example

Example

Assets / Environments

Redesigned CloudGuard Environments page with one filter and search bar, a toolbar with Add new, Validate permissions, Columns and Export, and a data grid of environments with organizational units and protection bars; the pointer hovers one environment name, which shows as a link
  • Keep data actions on the left

  • Keep view actions on the right

  • Use verb-only labels when context is clear

  • Use sentence case by default

  • Group related options in drop-downs

  • Start every row with an entity icon

  • Show links on hover only

  • Limit row icons to entity and status

  • Group related columns and collapse by default

  • Show status icons only for issues

Adoption

Adoption

I worked with all three front-end teams as I built the design system. They adopted the shared patterns as they moved their screens to React.

The implementation evolved with use. Some developers found Tailwind’s utility classes awkward to work with, and all three teams gradually moved to styled-components.

Impact

Impact

3 of 3 teams on the same design system. Teams that had been solving the same interface needs separately now built on one shared system.

~80% of major screens aligned. Alignment came with the move to React, with no separate redesign.

Rebranded easily. The system stayed in use. When Check Point rebranded, well after the work began, some of the implementation was just replacing design tokens.

Fewer UI bugs. UI bugs dropped in some areas, especially the data grid, once AG Grid replaced the internal grid.

What came next

With the UI aligned, I moved on to a navigation redesign and a color system redesign.

Next case study

Designing a conversation-first interface

I designed how customers move between a conversation and its artifacts in a Check Point interface.

Read nextor press →