top of page

1 of 2 designers / Q3 of 2025 / ui design & design systems

DESIGN SYSTEMS / BRANDING / INTERNSHIP 

Tess Design System

Rebranded an early-stage design kit and restructured its documentation into a shared system for eight product teams to use.

tess hero.png

ROLE

visual design intern,
on a design team of 3 

TIMELINE

may - july 2023
 

SCOPE

branding, documentation,
component maintenance

THE PROBLEM

A design kit existed, but nobody trusted it.

I joined a three-person design team at IBM supporting a suite of internal products for a global automotive client. Eight product teams were building on their own, and their visual language was drifting apart.

 

​A shared Figma kit existed, but it was barely set up: early-stage, grassroots, and thinly documented. The teams had no reason to rely on this outdated system.

MY ROLE

Making the design system worth adopting.

My team gave me creative ownership of the rebrand. I drove the visual concept with the team, rebuilt the documentation site’s structure, wrote documentation for 30+ components, and maintained updates to the system through the end of the summer.

tess-role-diagram.png

THE CONCEPT

We rebranded as 'Tess' as a callback to describe what a design system does

The kit needed an identity that teams would recognize and trust. I brought visual explorations to design meetings so we could shape the concept together. With this design system, we wanted to convey that smaller pieces working together fit into a seamless whole. We landed on tessellation, which felt like an honest metaphor for what a design system actually does. 

Group 188.jpg

DECISION 1: ONE CUBE VS. MANY

single-cube variations

multi-cube variation

Early directions centered on a single cube, which read as one object rather than a system. Multiple cubes let the identity show pieces working together.

DECISION 2: COLOR

single-shade variations

multi-colored variation

Teal, orange, and purple stay distinct from each other and carry through to the documentation site's sections.

THE GAP

The biggest gap to resolve was component documentation. 

I compared the existing documentation site against the Figma kit, mapping what existed, what was missing, and what needed restructuring. Using IBM Carbon and Google Material as benchmarks, I rebuilt the site architecture around a new sitemap and wrote component documentation for 30+ components.

This site covered component usage, variants, formatting, behaviors, and modifiers. I worked with the team to gather real use cases for every component so the documentation reflected how people were actually building.

COMPONENT PAGE

Every component page followed the same template, with labeled anatomy and clear guidance on when to use it.

MAINTENANCE

A design system stays trustworthy only if it stays current.

For the rest of the summer, I maintained the system week to week and pushed release notes as the kit evolved and new designs were created for the products.

IMPACT

A shared system gave every team the same starting point.

Tess gave the account’s product teams one place for components, guidance, and updates. The goal was simple: fewer one-off decisions, more consistent products, and design reviews and stakeholder conversations that started from shared ground. 

​

A few months after I left, a colleague who joined told me she’d learned Tess during onboarding, and that it was still being worked on and built into the team’s workflows.

bottom of page