---
title: "Tokens as a product"
url: /cases/tokens-as-a-product
description: "At Notino, tokens moved between the design tool and code in both directions, automatically, and shipped as versioned packages for many internal teams."
---

## §0 · problem

# Tokens as a product

**Level 2 · 2022 to 2024 · React developer, part-time, in the design-system team of Notino**

The system served 15 internal teams [claim case3-teams: The author's reference deck, 2024; source: author's reference deck 2024 (docs/early-work/phudran_reference_2024.pdf); confirmed]. Each team needed the same decisions in its own code, kept in step with the design files.

## §1 · built

### What was built

Tokens moved between the design tool and code in both directions, automatically, and shipped as versioned packages, with visual tests and a documentation portal.

## §2 · taught

### What it taught

Decisions became data.

## §3 · open

### What is still open

A token carries a value, not a rule. "Use this colour only for destructive actions" stayed in prose that people had to read. That is the gap level 4 closes.
