The interface has left the buildingUX Collective
DesignProduct
As AI agents take over tasks, the traditional screen-based interface is quietly disappearing.
- Shift in paradigm: The argument: we're moving from designing screens to designing systems of intent, where interfaces become invisible or conversational.
- Why it matters: Design teams built around visual UI craft may need to rethink what 'the product' even is when agents act on users' behalf.
- Skills at risk: Traditional UI skills like layout and visual hierarchy matter less; orchestration, trust design, and fallback states matter more.
- Bottom line: Design orgs need to start experimenting with agentic flows now, not wait for the shift to fully arrive.
For design
Start auditing your design system for 'agentic-readiness' — do your components assume a screen, or can they flex into conversational and invisible interactions?
Did you verify that — or was it just too easy to believe?UX Collective
EthicsDesign
AI-generated content exploits cognitive ease, making us trust answers we never actually verify.
- The core idea: Fluent, confident AI output feels true because it's easy to process — not because it's accurate.
- Why it matters: As AI-generated content floods products, designers need to build in friction that encourages verification without killing usability.
- Design implication: Patterns like source citations, confidence indicators, and 'show your work' UI become trust infrastructure, not nice-to-haves.
- The tension: Too much friction kills adoption; too little breeds misplaced trust — there's no easy line to draw.
For design
Audit any AI features you ship for 'cognitive ease' traps — if answers feel too smooth, users won't question them, and that's a liability, not a compliment.
The Kintsugi problemThe best design decisions happen not when things work, but when they break.
- The metaphor: Kintsugi — the Japanese art of repairing broken pottery with gold — is used to argue error and edge-case handling deserves the same care as the happy path.
- Why it matters: Most design systems and specs over-invest in ideal-state flows and under-invest in failure, error, and recovery states.
- For DesignOps: Teams that build robust error and edge-case patterns into their design systems ship more resilient products with fewer support escalations.
- Bottom line: Treat failure states as a first-class design deliverable, not an afterthought engineers patch in later.
For design
Consider auditing your design system's coverage of error and edge states — if most documented patterns are happy-path only, that's your resilience gap.
Craft still matters, but it's about outcomesUX Collective
DesignProduct
A pushback on the craft-vs-outcomes debate: craft is only valuable when it drives real results.
- The debate: As AI speeds up production, some argue polish matters less — this piece says craft still matters, but must be justified by outcomes.
- Why it matters: Design leaders are under pressure to show ROI; craft-for-craft's-sake is a harder sell when AI can produce 'good enough' fast.
- The reframe: The argument isn't to abandon craft, but to tie every craft decision explicitly to a measurable user or business outcome.
- For DesignOps: This gives ammunition for justifying design investment in AI-accelerated workflows — frame craft as a lever for outcomes, not a cost center.
For design
Useful framing for budget conversations — reposition craft investment requests around specific outcome metrics rather than quality for its own sake.