UCD Surf

Find what matters in the design archive

UCD Coach

Practice brief · Design systems

Tokens: the boring bit that actually matters

Published 24 August 2026 · Source dated 1 October 2025

Used for: Alpha assumption; Design-system tidy; Stakeholder brief; Portfolio proof; Tool experiment. Practice brief for the gate you are in — not an industry digest dump.

Hype check: Established. Treated as established practice. Source dated 1 October 2025.

Saves the claim and source date (1 October 2025) on this device. No account.

Design tokens — named values for colour, spacing, type — are the established backbone of keeping design systems consistent across Figma, Penpot and production code. Not new, but still the bit a lot of junior portfolios skip entirely.

Tokens map design decisions (a specific blue, an 8px gap) to variables that both design tools and code can reference, so a change in one place propagates everywhere instead of being hunted down file by file. It's a well-established practice on any team running a real design system, and ongoing discourse on tokens and patterns (tracked by outlets like Radical Design) keeps refining how teams govern them, not whether they're worth doing. If your portfolio work still has hard-coded hex values scattered across frames, that's the tell a reviewer will spot fastest.

Coach

Open a current Figma or Penpot file, pick three colours you've used more than once, and turn them into variables/tokens instead of hard-coded values.

Source: radical.design ·

Pair with UCD Coach

Coach is the forward habit — today's five, every morning. Surf is the rearward workbench on the same briefing corpus. Today's five is not restaged here.

Open today's five on UCD Coach

Daily email stays on Coach. Surf has no subscribe form.

More practice briefs on the same topic — not today's five from UCD Coach.