Log in or create a free Rosenverse account to watch this video.
Log in Create free account100s of community videos are available to free members. Conference talks are generally available to Gold members.
Hands on AI #3: Claude Code for UX people
This video is featured in the Evals + Claude playlist.
Summary
In this final talk in the series, we are not going to write code, but we will dig into Claude Code, and do a deep analysis of why it has taken off the way it has as an agent.
What are the properties and the UX decisions that went into building it that make it such a success? What are some of the things we as UX people can learn from it.
You will go away with a much better intuition around AI agents, how you can set them up yourself or build them for your customers in a more successful way, how to think about adoption and agent UX properties. It’s still very early in this agent journey - get ahead of the pack right now.
Key Insights
-
•
Claude Code is a minimalist AI agent that uses tools in a loop, enabled by post-training models for reasoning and tool use.
-
•
Despite a terminal UI being poor UX by traditional standards, Claude Code creates user feelings of respect, control, and trust through transparency and interaction design.
-
•
Agents like Claude Code operate by the model writing output tokens to its own prompt window, effectively chatting with itself while calling tools to perform actions.
-
•
Context and memory for agents are managed by simple markdown files that describe projects, workflows, or skills, allowing models to have relevant information without built-in memory.
-
•
Claude Code supports multimodal inputs, enabling tasks like analyzing images as well as text or code.
-
•
The 'decade of agents' implies ongoing rapid evolution with agents becoming central to product workflows over years rather than an instantaneous shift.
-
•
Users, rather than designers or developers, should be empowered to define workflows and prompts, shifting traditional roles and responsibilities.
-
•
Model memory is externalized via saved context text files or 'skills' that function like onboarding materials loaded on each session start.
-
•
There is no fixed best practice yet for agent workflows; experimentation and simplicity outperform over-engineering.
-
•
The evolving AI landscape challenges rigid job titles like 'designer' and 'developer,' encouraging more collaborative, role-fluid approaches.
Notable Quotes
"Cloud code wasn’t programmed to do this; it’s a very lightweight system where the model does most of the work."
"Agents are literally models using tools in a loop—they respond to themselves and the tools in chat-like conversations."
"Despite the worst user interface ever, cloud code is the most popular and successful agent that exists today."
"Trust the user and trust the model are the two lessons I’m getting over time."
"Your short term memory is the context window; too big, and the model has trouble accessing everything."
"Skills are like onboarding material for the model; you write them as simple markdown files that describe workflows or tools."
"If you build for the next model, even if it can hardly do something now, it will probably do it well in the future."
"Don’t overcomplicate workflows; the simplest thing that could possibly work is often best."
"We need to dramatically change the hats, the walls, and the workflow of how we work together in design and development."
"You can’t just be a designer adapting UX workflows assuming everybody else’s workflow stays the same; everything is changing with AI."
Or choose a question:
More Videos
"Design ops has the opportunity to set a new default future, not follow the path set by the past."
Dr. Karl JeffriesThe Science of Creativity for DesignOps
January 8, 2024
"Creating internal champions in client organizations helps improve adoption and reduces churn."
Amy MarquezINVEST: Discussion
June 15, 2018
"The weakest insight method might win simply because of the relationship to the power structure."
Steve Portigal Chris Chapo Kelly Goto Christian RohrerDiscussion
May 13, 2015
"Splitting people’s allocation across different teams created work-life balance issues requiring more oversight."
Alicia MootyDesign Staffing Models
September 30, 2021
"We may not have tech prowess but our sticky notes, card sorts, and test reports are our real superpowers."
Ana Maria Montero Barrantes Aditi Dhar Michelle Kaplan Nate Osborne Matt LaurenceThe Authentic UX Talent Show
January 8, 2024
"Field usability testing showed stakeholders immediately how much value UX can add by catching issues before deployment."
Lada Gorlenko Sharbani Dhar Sébastien Malo Rob Mitzel Ivana Ng Michal Anne RogondinoTheme 1: Discussion
January 8, 2024
"I didn’t want to be part of that as a founder, hacking attention just to fulfill engagement metrics."
Sofia QuinteroThe Product Philosophy Behind EnjoyHQ
March 10, 2021
"The incentive structure at a big company is set up to reward people for entirely different stuff than innovation requires."
Laura KleinUnique challenges of innovation in enterprises
April 23, 2020
"Without Jim, what we're going to see today would have been a lot worse."
Andrew MichaelBuilding a Product Insights Team
March 10, 2022
