Figma just made your design system debt everyone’s problem
Weekly curated resources for designers — thinkers and makers.
“This is the real shift. Design system debt used to be paid by one person, quietly, in files nobody else opened. Now it gets paid by the engineer whose generated component is wrong, the PM whose timeline slips because handoff broke, the marketer whose banners came out off-brand. The cost moved out of your corner and into theirs.
Designers have argued for years that a design system is not a deliverable but a product that needs governance, funding, and an owner(…) The argument was always correct and almost always lost, because the people who held the budget never felt the failure. Now they do.”
Figma just made your design system debt everyone’s problem →
Visualize striking 3D embellishment mockups →
[Sponsored] DREAMCOMPOSER® transforms designs into impressive 3D mockups. Try 100+ KURZ transfer decorations and share results instantly.
Editor picks
This is your real value in tech companies →
You’re missing the point.AI personality is a design problem →
An interface we build deliberately.Discovery is a capability, not a phase →
The judgment layer most discovery practice leaves unexplored.
The UX Collective is an independent design publication that elevates unheard design voices and helps designers think more critically about their work.
Make me think
Legibility of effort →
“Until recently, “someone cared enough to write this” was an ok heuristic. Plenty of writing on the internet was bad, but you could convince me that you cared about something just by writing it down.”Repricing of software engineering labor →
“I don’t think software engineering is disappearing. I think the market is repricing it. For years it rewarded implementation throughput. Engineers that were able to move fast and build stuff are becoming obsolete overnight. These are large middle implementation-heavy generalists whose value was mostly shipping software built from known patterns.”On the semantic web →
“The easiest way to make an interface harder to maintain is to rebuild the browser badly. (…) That sounds obvious until you look inside a lot of modern component libraries. The visual layer is treated as the source of truth, then the behaviour is patched back on afterwards. It works in the demo. It usually works with a mouse. Then someone tries to tab through it, submit it from a form, use it with VoiceOver, disable it properly, or nest it inside a more complex flow, and the component starts leaking implementation detail everywhere.”
Little gems this week
The stone that blocks nothing →
Game UX: the cursor that wasn’t supposed to be there →
You don’t design the UI anymore; you design the deciding →
Tools and resources
How designers need to change for an AI-powered world →
A panel discussion.39 principles for designing human-AI interaction →
An applied framework for designing AI interfaces.Research is not a deliverable →
The gap between what data shows and hides.
Support the newsletter
If you find our content helpful, here’s how you can support us:
Check out this week’s sponsor and support their work too
Forward this email to a friend and invite them to subscribe