Weekly curated resources for designers — thinkers and makers.
“AI coding agents are bringing some of that interaction model back. You can describe an outcome and let the agent decide which commands to run, which files to change and which tests to execute. You no longer have to operate the software step by step, but a familiar design problem comes back in another form: What did the system understand? What is it doing? What has it changed? What can I stop? What should I review?
The interface is no longer just something we operate; it can act.”
When the canvas starts acting, who’s really in control? →
By Aurélie Radom
Talk with your users in the moment →
[Sponsored] Marvin’s Live Intercept launches an AI-moderated interview inside your product or website. Users talk through their experience and share their screen, giving your team fresh, contextual feedback. Try it now
Editor picks
- Beyond the corporate stairs →
Rethinking success in the world of design.
By Darren Yeo - AI took away engineering’s right to say no →
The power to say what’s possible.
By Dan Maccarone - The call for an agentic standard →
We need to stop shipping the same form four different times.
By Patrick Neeman
The UX Collective is an independent design publication that elevates unheard design voices and helps designers think more critically about their work.
Step inside Teddy Blanks’ film title design process →
Make me think
- How AI-ready is your design system? Now you can measure it. →
“Every design system team is having the same conversation right now, and nobody can back it with numbers. We built the eval, ran it against four real systems, and published the harness.” - A good move is enabling →
“Product strategy is expressed in the moves your team makes on the field of play. Or as above, the path you take at each fork, one after the other. Bad moves waste work, overcommit resources, and close future possibility, to say nothing of the toll they take on team members stuck out in the wild.” - You have to beat the models at something →
“Today, value over replacement is even more important. A replacement-level engineer in the 2010s was fine: maybe not worth promoting, but still worth paying, because writing code had a high fixed cost. Now writing code costs a hundred bucks a month. What are you doing that GPT-5.6-Sol or Claude Opus 5 wouldn’t do in your position? Why is it worth paying an extra two or three orders of magnitude for?”
Little gems this week
Users don’t see your design system →
By Chris R Becker
Neuroqueering design practice →
By Kristina Gushcheva-Keippilä
Your synthetic self belongs to strangers →
By Anamol Rajbhandari, MSc
Tools and resources
- The prompt is the product →
What I learned teaching Claude to build the tool I actually meant.
By Sophia Hee - A larger responsibility for designers →
UX in 2027 may be less about interfaces and more about behavior.
By Lucas Camara - Making kyōwa possible with AI →
Words that work as sketches.
By Hiroshi Sato
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
- Sponsor an edition
AI canvas, Synthetic self, The prompt is the product was originally published in UX Collective on Medium, where people are continuing the conversation by highlighting and responding to this story.