UCD Surf

Find what matters in the design archive

UCD Coach

Practice brief · Design systems

Design tokens are now the default, not the extra

Published 5 September 2026 · Source dated 20 January 2026

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 20 January 2026.

Saves the claim and source date (20 January 2026) on this device. No account.

Token-based systems — colours, spacing, type as reusable variables rather than hardcoded values — have moved from 'nice to have' to baseline practice in design systems work. If your portfolio still hardcodes hex values, that's a gap worth closing.

Design system communities have been converging on token-first thinking for a few years now: Figma Variables, W3C-aligned token formats, and cross-tool token export are standard conversation topics, not edge cases. This is **established** practice — it's been stable long enough that hiring managers expect junior candidates to at least understand the concept, even if you haven't built a full system yet. The risk for juniors isn't missing the next shiny thing — it's still submitting portfolio work with hardcoded values when tokens are the expected baseline.

Coach

take one component from your portfolio and rebuild its colours and spacing using variables/tokens instead of hardcoded values.

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.