RentSpreeProduct design · Guidelines & token research · 2022–2023

Design System & Tokens

A shared language for a growing design team.

As RentSpree’s design team grew, inconsistent component rules made UI design and handoff harder. I created checkbox and radio guidelines, led design-token research, and shared naming examples with designers and developers to establish a common vocabulary.

Team: Designers and developers

Role
Product Designer · UX & UI
Company
RentSpree
Timeline
2022–2023
Scope
Guidelines & design tokens
RentSpree design system project cover
The RentSpree design system and design-token project.

A growing team needed shared rules.

I created component guidelines, led token research, and worked on bringing tokens into the system. I shared the work with designers and developers so behavior and naming could be discussed together.

The problem

The team grew faster than the system.

The design team grew from two or three people in 2019–2020 to around eight in 2022 and 14 in 2023. An unstable system made UI work and handoff difficult, while developers dealt with frequent design changes.

Make the rules explicit before asking people to reuse them.

I documented checkbox and radio usage before implementation so the team could agree on behavior. The guidance covered selection, nesting, label interaction, alignment, spacing, and normal, hover, focus, error, and disabled states.

Checkbox and radio guideline page with references and UX agreements
The guideline introduced shared usage rules and supporting references.
Checkbox and radio behavior, usage, alignment, and spacing examples
Examples explained behavior and when to use each control.
Radio and checkbox components in normal, hover, focus, error, and disabled states
The state matrix made component behavior easier to compare.

Design tokens

Give visual values names that explain their purpose.

I explored a naming structure from raw values to global, alias, and component tokens. A purpose-based name such as color-button-primary gave designers and developers a shared way to refer to a value.

Value

The underlying color value, such as #0150B5.

Global token

A palette name, such as blue-100.

Alias

A shared role, such as color-primary.

Component token

A specific use, such as color-button-primary.

Button token example mapping #0150B5 to blue-100, color-primary, and color-button-primary
An example from my token research, connecting a button’s appearance to named values.

Show how the system behaves in real interfaces.

Switch variants documented loading and error states as well as on/off behavior. Table examples showed fixed and scrolling columns, connecting component definitions to actual layouts.

Switch component variants with on, off, disabled, loading, and error states
Switch variants documented states with and without text labels.
Desktop table layouts comparing fixed and scrolling columns
Desktop examples showed fixed-column and fully scrolling table layouts.

Outcome & reflection

What I produced

Guidelines and token examples the team could discuss.

I produced component guidelines, state examples, and token-naming examples, and shared token knowledge across design and development.

These are documented deliverables. Adoption, handoff efficiency, and time savings were not measured for this case study.

Intended benefits

A common vocabulary and a clearer way to manage change.

Shared names were intended to reduce ambiguity during handoff. Connecting components to tokens would also let a value change propagate across its uses; this was the maintenance benefit I was working toward.

Reflection

My first step into design tokens.

This was my first work with design tokens. Defining values was only part of the task: the team also needed to understand and agree on the rules behind them.