UCD Surf

Find what matters in the design archive

UCD Coach

Practice brief · Design systems

Design tokens have quietly become a baseline skill

Published 15 August 2026 · Source dated 1 August 2026

Used for: Design-system tidy; 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 August 2026.

Saves the claim and source date (1 August 2026) on this device. No account.

Ongoing design-system coverage keeps circling back to tokens and governance rather than shiny UI kits. Knowing what a token is and how it maps to Figma/Penpot variables is now a reasonable expectation, not a specialism.

Token-based systems — shared name/value pairs for colour, spacing, type — have moved from a niche design-ops topic to a recurring theme across design system coverage. That shift matters for juniors because it's no longer just a design-systems-team concern; it shows up in everyday component work. Both Figma (variables) and Penpot (W3C-aligned tokens) support this now, so you can practise the concept in either tool. Being able to explain what a token is and why it beats a hard-coded hex value is a small, concrete thing you can bring up in a portfolio walkthrough. This is established practice at this point, not a hype cycle — the debate has moved from

Coach

rebuild one small component using tokens/variables instead of hard-coded values, and note the change in your file.

Source: designsystems.news ·

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.