Design Systems • SaaS • Front-End <

NS Design System

A reusable design system created to improve consistency, scalability, and product quality across a SaaS benefits platform.

My Role
UI/UX Designer
Timeline
Product initiative
Team
Design • Product • Engineering
Technologies
Figma • HTML • CSS • PHP • JavaScript
NS Design System
01 — The Problem

Growth created inconsistency.

As the product grew, teams needed a common visual and interaction language. Repeated patterns were being solved independently, which made experiences feel inconsistent and created unnecessary design and development work.

The challenge was not simply to create a library of components. It was to create a foundation teams could actually use and extend.

02 — The Approach

Start with foundations, then build upward.

I established reusable foundations for color, typography, spacing, borders, states, and interaction patterns before expanding into components.

This created a common set of design decisions that could be translated into reusable front-end patterns instead of being recreated from scratch for every feature.

03 — Foundations

The visual language behind Gravity.

The system's foundations created consistency before a component was ever placed on a page.

Color

A focused palette establishes hierarchy while semantic colors communicate status alongside text and icons.

Aa

Typography

A clear type hierarchy separates page titles, section headings, body content, labels, and supporting information.

Spacing

A predictable scale makes layouts easier to compose and helps reduce one-off implementation decisions.

Default Focus Hover

States

Interaction states are treated as part of the component rather than visual polish added at the end.

04 — Components

Reusable components became the building blocks.

Each component was designed to be recognizable, reusable, responsive, and understandable to both designers and developers.

Buttons

Clear hierarchy and predictable states for common actions.

Benefit Selection

Forms

Consistent labels, controls, validation, and focus behavior.

Plan summary Coverage details View details →

Cards

Structured content containers with consistent hierarchy and spacing.

Overview Plans Resources

Navigation

Predictable navigation patterns make location and hierarchy clear.

Data displays

Tables and information-dense layouts use hierarchy to reduce cognitive load.

✓ Changes saved

Feedback

Status, confirmation, loading, and error patterns communicate what happened next.

05 — Patterns

Components work together to support real tasks.

01

Complex forms

Break complicated workflows into smaller steps while maintaining context and clear progress.

02

Benefits comparison

Use consistent cards, tables, controls, and hierarchy to help users compare options.

03

Responsive behavior

Patterns adapt across screen sizes without making hover the only way to understand an interaction.

04

Accessible feedback

Use text, structure, focus, and appropriate status messaging instead of relying on color or animation alone.

06 — Documentation & Collaboration

A system needs shared ownership.

Gravity was intended to connect design and engineering, not create another silo. Documentation helped communicate component intent, usage, states, and implementation expectations.

The most valuable outcome was a shared vocabulary. Designers could talk about patterns using consistent terminology, while developers had clearer expectations for reusable implementation.

NS Design System Component documentation
BUTTONS

Primary button

44px minimum target
07 — The Result

Gravity created a stronger foundation for consistent SaaS experiences.

The system gave design and engineering teams a shared vocabulary for building the product, reduced repeated design decisions, and established reusable patterns that could scale with the product.

Shared language Design and engineering could work from the same set of concepts.
Reusable foundation Common decisions could be applied across new product experiences.
Better consistency Users encountered more predictable visual and interaction patterns.
08 — The Takeaway

A design system is a living product.

The strongest systems evolve with the products and people they support. The goal is not to create a perfect library once. It is to create a foundation that makes thoughtful, accessible decisions easier to repeat as the product changes.

Quick navigation