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
"The moat that once protected researchers—their exclusive data access—is disappearing; now our value is enabling others to use insight."
Jemma Ahmed Megan Blocker Eduardo OrtizRedefining the research toolkit: Expanding methodologies for a changing world
March 12, 2025
"Design systems are the language of implementation; they allow us to communicate ideas in a common format and process."
Mitchell BernsteinOrganizing Chaos: How IBM is Defining Design Systems with Sketch for an Ever-Changing AI Landscape
September 29, 2021
"Procurement portals can be hard to navigate; act like you’re bidding and go through the user experience yourself."
Emily LessardRFPs Without Tears: Writing Inclusive RFPS that Don't Scare Away Talent
December 9, 2021
"Transformation isn't just about ideas, it's about infrastructure."
Jenny PriceFrom Tradition to Transformation: Unlocking Startup Agility in a Legacy Enterprise
September 10, 2025
"Always design a thing by considering it in this next largest temporal context — a day in a month, a decade in a century."
Sarah Auslander Betsy Ramaccia Gordon RossInsights Panel
November 18, 2022
"Different UX methodologies should coexist and collaborate like an ecology of practices rather than compete."
Soma Ghosh Savina Hawkins Dave Hoffer Rob Thomas Victor UdoewaWhat emerging methods are advancing UX research [Advancing Research Community Workshop Series]
September 28, 2023
"Continuous adaptation is key; you're adapting to the system as much as adopting it."
Charles Lee Jennie YipBuilding a New Home for the Atlassian Design System
October 22, 2020
"Songs become methodologies—the way you identify who is at the door is through the song they sing."
Victor UdoewaBeyond Methods and Diversity: The Roots of Inclusion
March 26, 2024
"Many hiring managers feel stuck by bureaucracy and policies that haven’t adapted, limiting candidate pools to specific locations."
DesignOps and The Great Talent War of 2021
August 19, 2021
