Nimbus Design System

My Role:

Solo Product Designer

Highlight:

Redesigned 30% of the most used products in 2 sprints!

The Problem

As the enterprise cloud security market started to become saturated with competitors, DivvyCloud's lack of focus on product experience design was cause potential customers to choose easier to use tools

As the first company to create a multi-cloud enterprise cloud solution, early days, DivvyCloud customers had no choice but to use DivvyCloud because it provided them with the value they needed. 

However as cloud adoption became more mainstream and other companies entered the market, new customers were willing to buy a combination of other tools over DivvyCloud because they were easier to use.

How might we improve the usability of DivvyCloud products quickly, in order to decrease customer churn?

The Solution

Create and use a design system to implement standard patterns use cases across the platform efficiently

  • Gives a score summarizing how compliant your entire cloud ecosystem is
  • Shows you where to focus, cloud resources with severe violations
  • Patterns and trends you can drill into for a path to violation resolution

The Results

Updated 2/3 of DivvyCloud's platform in 2 weeks

Reduced project turn around time by 35%

The Process

Inventory

Following an atomic design strategy I first took inventory of every UI component and pattern in the platform. I then evaluated how the pattern was being used, and determined if it was the best pattern or component to use.

A few screenshots of the DivvyCloud Application

Screenshots of different parts of DivvyCloud

Audit

After capturing all of the patterns and components that made sense for their use case, I grouped them into categories, side by side. I used this to display to the broader team visually how different experiences were throughout the platform.

A screenshot of the groupings of UI elements in DivvyCloud

A few of the category groupings of UI element

Edit

I then used a UI component library as the bones and modified the components and patterns to fit our platform's needs. I then created a name convention for all the components, and patterns, reviewing them with the team regularly.

A screenshot of the naming convention used for the design system

A screenshot of the Figma file of the design system

Evolve

I worked with an engineer on the team to implement the components in the design system we needed for a specific project: Exemptions. We used this as a test to see how much of a difference the design system makes with shipping out an experience quickly

A screenshot of the Figma File for the design system

A screenshot of the Figma file of the design system

Results

The successful and speedy launch of our test project helped us validate our hypothesis that, creating and implementing a design system would allow us to improve the usability of the platform and ship our ideal experiences efficiently. My engineer and I went product by product and switched out the old components with those of the design system, focusing on the highest-impact products first, We were able to completely update 2 of our 3 flagship products within two sprints. We continued to update DivvyCloud products with best in class user experience, thanks to the implementation of the design system.

Photo of Anna enjoying a drink
Let's chat!

Do our missions align? Shoot me an email and let's chat