Chat is the wrong interface for AIUX Collective
DesignProduct
A UX Collective piece argues chat windows oversimplify what AI agents can actually do.
- The core argument: Chat-first interfaces flatten complex agent capabilities into a single text box, hiding state, context, and available controls.
- The cost: Users lose visibility into what an agent is doing and why — a real usability gap as agents get more autonomous, not less.
- Design challenge: Teams need richer interaction patterns — dashboards, timelines, approval flows — instead of defaulting to chat for every AI feature.
For design
Before your team ships another 'just add a chatbot' feature, map out what state and control visibility users actually need — chat is often the fastest path to a confusing product.
Designing for the proxyUX Collective
DesignProduct
As AI agents start acting on users' behalf, designers need to rethink who the 'user' really is.
- New audience: When agents — not humans — navigate and transact on someone's behalf, standard UX assumptions about attention and interaction start to break down.
- Design implication: Interfaces may increasingly need to serve two audiences at once: the human and their AI proxy, with very different information needs.
- Why it matters: This is an early signal of a structural shift in what 'designing for the user' will mean over the next few years.
For product
Start auditing which of your flows might soon be navigated by an agent instead of a human, and what breaks in that scenario.
The architecture of watching workUX Collective
EthicsDesign
AI monitoring tools are quietly rewriting the century-old question of how offices observe work.
- The shift: For a century, office design answered 'how do we see work?' with physical layout — AI monitoring tools are now changing the question entirely.
- New capability: AI can track granular activity, output, and sentiment signals far beyond anything physical office design ever allowed.
- Why it matters: For workplace and DesignOps leaders, this raises real trust and autonomy questions as monitoring tools proliferate under the banner of 'productivity insight.'
For ethics
If your org is evaluating AI activity-monitoring tools, get ahead of the trust conversation with your team before IT quietly rolls one out.
Design.md: the one standard file carries your visual identity, for humans and agentsUX Collective
DesignProduct
A proposed 'design.md' file could give both humans and AI coding agents one source of truth for brand identity.
- The idea: Like a README.md but for design — a machine-readable file encoding your visual identity and design system for AI coding agents to reference.
- Why now: As more UI gets AI-generated, teams need a reliable way to keep output on-brand without manually reviewing every screen.
- Design systems angle: This could become a new artifact design systems teams maintain alongside tokens and component libraries.
For design
Worth prototyping internally — a lightweight design.md could save your team from endless brand-consistency fixes as more engineers lean on AI coding tools.