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.
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
"Testing one user is 100 percent better than testing none, but it’s not a strategy forever."
Leisa ReicheltThe Five Dysfunctions of Democratized Research at Scale
March 30, 2020
"In 2020, UX hiring grew 20% as digital experiences became critical during the pandemic."
Dana Bishop2022: The Year UX Demonstrates its Business Impact
March 11, 2022
"I literally would have to jump up in meetings to introduce myself as the director just to be recognized."
Lisanne NormanWhy I Left Research
March 27, 2023
"Without proper evaluation, you’re just building a demo – demos are easy, quality production is hard."
Peter Van DijckBuilding the Rosenbot
June 4, 2024
"Many designers get pushed into leadership roles they're not equipped for, and design ops can help fill those gaps."
Holly ColePanel Discussion: Growing People and Teams
November 8, 2018
"Different ops functions have different incentives; aligning those incentives could make leaps and bounds in collaboration."
Jon Fukuda Jake Burghardt Jose Coronado Natalie Dunbar Denise TillesAll the Ops: Successful cross-functional collaboration
September 10, 2025
"We benchmarked usability and found Intuit was average compared to competitors — not good enough anymore."
Kaaren HansonStop Talking, Start Doing
June 9, 2017
"Our card deck helps give us respectful language and bite-sized info to engage with different communities."
Saara Kamppari-MillerInclusive Design is DesignOps
September 29, 2021
"Please come away from this conference with at least one contact, maybe even a friend."
Louis Rosenfeld Christian CrumlishOpening Remarks
November 29, 2023
