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
If you’re a product manager, UX researcher, or any kind of designer, you know everyone is talking about agents. And perhaps the best agent out there right now is Claude Code. 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
"No tracking is perfect because numbers tell you what likely happened, but not why it happened."
Erin WeigelUX Lessons from running more than 1,200 A/B Tests
July 10, 2024
"To innovate smarter, you need to get access to the roadmap as early as possible and start research even when not asked for it."
Mike OrenWhy Pharmaceutical's Research Model Should Replace Design Thinking
March 28, 2023
"Being fluent in multiple data languages and understanding behavioral and attitudinal data will be essential."
Lija Hogan Milan Mijatovic Sam Proulx Louis RosenfeldThree Years Out: Perspectives on the Near-Term Future of User Research
March 15, 2024
"Prompt injection attacks can trick AI agents into accessing private data like emails without the user realizing."
Heidi TrostWhen AI Becomes the User’s Point Person—and Point of Failure
August 7, 2025
"If you just throw new hires into cubeville, most of them would probably quit."
Adam CutlerPeople + Places + Practices = Outcomes
June 8, 2016
"Helper texts appear when hovering on unfamiliar features, explaining what buttons or controls do."
Rittika BasuAge and Interfaces: Equipping Older Adults with Technological Tools
February 23, 2023
"One superpower of ops humans is making problems and gaps visible to build awareness and drive change."
Saara Kamppari-MillerDesignOps for Inclusive Design and Accessibility
May 26, 2022
"I often find myself wondering what I really gained from time away from my desk beyond swag and catching up with colleagues."
Bria AlexanderTheme Two Intro
October 3, 2023
"It’s okay if these junior roles are short term; they help get started and expand the overall design ops talent pool."
Laine Riley Prokay Lisa GordonCarving a Path for Early Career DesignOps Practitioners
September 9, 2022
Latest Books All books
Dig deeper with the Rosenbot
How does including metadata like methodology, market, and date improve the quality of research repository search results?
How does healthcare UX balance creativity with strict regulatory compliance and safety requirements?
How can teams create lightweight visibility systems that improve workload transparency without reducing productivity?