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
"People get stuck during the sessions when asked to describe their brand voice in just one or two words."
Trisha Causley[Demo] Complexity in disguise: Crafting experiences for generative AI features
June 5, 2024
"Some people have been doing research ops a lot longer than the term has existed."
Kate TowseyAsk Me Anything (AMA) with Kate Towsey
April 2, 2025
"We unapologetically move forward when high-level stakeholders miss deadlines, but also collect feedback via surveys."
Briana Thomas Christina RodriguezWhen Design Ops Comes in H.O.T. : A Tale of a Transformed Design Org
September 30, 2021
"Optimal design leadership looked like a CEO who promoted design as strategy and a chief design officer with the ear of the CEO."
Brianna SylverLead With Purpose
March 31, 2020
"Research has layers like an onion; we operate at multiple layers, from discovery to concept evaluation."
Anna Poznyakov Richa PrajapatiGet The Most Out Of Stakeholder Collaboration—and Maximize Your Research Impact
March 12, 2021
"The three in the box model is business, design, and technical representation, plus legal and compliance in regulated environments."
Frank DuranPartnership Playbook: Lessons Learned in Effective Partnership
January 8, 2024
"My boss might be looking over my shoulder and see nothing but red and think I’m not doing my job."
Craig VillamorResilient Enterprise Design
June 8, 2017
"Start with quick wins, show value, and communicate loudly to get buy-in for more design ops capacity."
Rachel Radway Katie Bingham Joe WiertelThe Many Paths Of Design Operations
September 8, 2022
"SAFe often turns UX into just digital or visual designers, which is wasteful and marginalizes valuable skills."
Christian CrumlishAMA with Christian Crumlish, author of Product Management for UX People
March 24, 2022
Latest Books All books
Dig deeper with the Rosenbot
How can co-created custom investment models change decision-making processes in government development agencies?
How does the culture clash between design's human-centered values and corporate bureaucracy manifest in organizational health?
In what ways can organizations use scaffolding to overcome bureaucratic constraints in service design?