GoGuardian - Galaxy Design System

Designed GoGuardian's design system Galaxy to help improve the productivity of designers and engineers

Interaction Design | UX Design | UI Design | Motion Design
About GoGuardian

In the summer of 2019, I worked at GoGuardian as UX Design Intern located in Los Angeles, California. GoGuardian is an Ed-Tech company that provides K-12 schools and districts with software for safe access to online educational content along with technology management.

Overview

About the Project

Galaxy was initiated by the design team to create the latest design components and design code for the Design and Engineering team. The aim is to increase the productivity for both teams and have a consistent design style for all GoGuardian products.

Since the project was in its initial stage, as an intern, I was assigned to take over the project and collaborate with the Design Manager to bring in some fresh perspective. I was responsible for creating, setting rules, and iterating on some of the major design components.

My Role | UI & Interaction Design

Research, Ideation, Created rules, Visual Design, Interaction, Motion Design, Usability Testing

Timeframe

10 Weeks | June - August 2019

Tools

Sketch, Principle, Invision, Craft, Contrast, Abstract, Confluence

Team Members

Design Manager, Engineer & Myself

The Challenge

To create a foundation for the design system that can help designers and engineers to have a consistent design on all the products.

The initial designs for GoGuardian products had no standard design guidelines, which resulted in redundancy in design components and inconsistent design across products.

The Solution
Design Components Preview

The following are the highlights of the main components I designed and set rules:

Designed a universal search bar to implement on the product's dashboard and internal pages.

Designed three sizes of dropdown menus: small, medium, and large based on the character limit.

Designed four sizes of modals as per character limit along with destructive message and form fill up modals.

Designed three sizes of text fields based on character limit along with four variants: Normal text field, text field with subtext, text field with optional tag, and error state text field.

Designed four types of information card and seven types of action cards.

Designed two types of list view tables normal and compact view with three variations.

Designed three states of the checkbox: unchecked, checked, and multiple checked state.

Designed two variants of accordions for the drop-down checklist and FAQ section.

Designed the primary filter dropdown menu for all tables.

Designed the main buttons for all products: primary, secondary, tertiary, and delete buttons in default and hover state.

01
Search Bar
02
Dropdowns
03
Modals
04
Text Fields
05
Cards
06
Tables
07
Check Boxes
08
Accordions
09
Filters
10
Buttons
Target Users
01
Primary Users
IT Admins

GoGuardian products are mostly for IT Admins to manage devices, filter content for safe digital learning.

02
Primary Users
Teachers

Some of the core GoGuardian products are for teachers for classroom management and digital learning.

03
secondary Users
Counselors

Few GoGuardian products are for the counselors to monitor and ensure the overall well being of students.

Design System Roadmap

Guidelines

Principles

The design team set three principles to follow while creating the design system. All components must adhere to these goals.

01
Principle
Consistent & reusable

There should be no inconsistencies, and every element in the design system can apply to all the products without looking off-brand.

Aim to make collaboration easy between and within teams.

02
Principle
Robust & responsive

The design system should serve as a strong and flexible foundation such that it gives you a basis while still allowing customization.

Aim to shift efforts from production work on to the design system to reduce the team's time for more creative problem-solving tasks.

03
Principle
Independent & informative

The design system should be a comprehensive source for design and engineering teams to look for design guidelines.

Aim to provide an informative system to share knowledge across and within teams more efficiently.

The 8-Point Grid
defining dimensions, padding, and margins
Why 8-Point Grid?

It’s difficult to create a consistent design without defining the spacing relationships of the elements in a page. Therefore we adapted to the 8-point system using multiples of 8 to set dimensions, padding, and margin of both block and inline elements. Also, the majority of screen sizes are divisible by 8.

How would it benefit us?

Enables us to:
• Create flexible components for various screen sizes
• Eliminate need for engineers to guess padding/sizing/spacing
• Eliminates pixel fitting
• To lay a foundation for responsive design

Accessible Design
WEB CONTENT ACCESSIBILITY GUIDELINES 2.0
Why WCAG 2.0 standard?

World Wide Web Consortium (W3C) creates open standards that ensure the long-term growth of the Web. To become compliant with Federal Accessibilities standards, we needed to ensure that the products are accessible for our users.

Design Check List

Text Contrast Ratio:
• 4:5:1 ratio for small text
• 3:1 ratio for large text

Forms:
• Have Text Labels for each field

Color:
• Ensure that there’s sufficient contrast
• Not to solely rely on color to be the only differentiator
• Use symbols along with color

Ideation

Design Exploration

We started brainstorming designs by involving different perspectives in the process.

1. White-boarding sessions
2. Design Workshops
3. Design Inspiration
01
IDeation
Whiteboard sessions
Weekly progress

Design Manager and myself had a weekly white-boarding session and invited other designers to brainstorm ideas and show them the progress each week for approval.

02
Ideation
Design Workshops
Inspiration & Insights

To get different perspectives and to ensure that our designs make sense, we hosted a few workshops with the engineers and marketing team and asked them to draw and critique our designs.

03
IDeation

Iterations

A/B Testing
Highlights on some of the iterations

We had weekly meetings with the entire design team to do A/B testing of design components to get feedback. We emphasized on it until approved, ready to be updated, and available to the team.

Final Designs

Final Design Components
Setting rules for all components designed

After designing all the components, I documented the rules for each component to help teams use as a guide when using or modifying them.

01
Search Bar
Do
  • Use the shortcut "Cmd+K" to activate the search bar
  • Change the arrow to "Type Cursor" on hover state
  • Provide a "Clear" text to remove tags
Don't
  • Use only search Icon, support the icon with text
  • Force a user to click on a search button
02
dropdowns
Do
  • Keep the dropdown close to the corresponding feature/table, etc.
  • Use carrot icon to indicate that there's additional functionality stored
  • Use the checkbox for multi-selection application
Don't
  • Only store one additional options or functionality in a dropdown
  • Use radio buttons for multi-selection application
  • Use dropdown without titles
03
Modals
Do
  • Use modals to interrupt, alert and confirm the user to make an explicit action
  • Left align text
  • Use Modals to reduce user errors
Don't
  • If it requires any type of search functionality, a page would be better for it
  • If the workflow requires multiple steps, it should not be in a modal
06
Tables
Do
  • Use tables to show list view
  • Allow users to customize the table type as per their needs
  • Maintain a minimum width of 880px for standard table
Don't
  • Exceed the list in the table to more than 10 in a single view
07
Check boxes
Do
  • Use checkboxes for multiple selections
  • Use at-least 8px of padding between the checkbox and text
  • Always place a checkbox to the left side of the text
Don't
  • Use checkboxes for only single selection
08
Accordions
Do
  • Use accordions for categories and group elements
  • Give the flexibility to select multiple accordions at once
  • Align the inner elements inside its group category
Don't
  • Use the same font-weight for category and its element when expanded
10
Buttons
Do
  • Use 16 px font size for buttons
  • Use padding of 8px around the text within the button
  • Use 16px of padding between multiple buttons
Don't
  • Use buttons stacked vertically
  • Never use Icon-only buttons

Deliver Designs

Managing Design System
making design system available for the designers

Following is the breakdown of how we aim to maintain and update the Design System for designers.

Conclusion
Overall Impact

The updated design system is currently being used by the design team to design new products and update the design style for legacy products feature by feature.

Next Steps

Since my internship came to an end, the Design Manager is working along with the engineering team to build design tokens and add it to the code base.

All Projects