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.
Building impactful AI products for design and product leaders, Part 3: Understand AI architectures: RAG, Agents, Oh My!
This video is featured in the AI and UX playlist.
Summary
Agents, RAG, Memory, Vector Databases, Tool Use, MCP! The sector is rapidly evolving lots of architectures to make AI products more helpful and impactful. Peter van Dijck of Simply Put will share a simple framework that helps you understand how to think about these architectures, how to plan around them, and how to work with engineering teams on them. None of this is rocket science, but the acronyms are many. You don’t need to write code, but you do need to understand what is going on in these systems. You will learn how to think about and understand these complex-seeming architectures, and how to think about new ones as they come out.
Key Insights
-
•
Large language models are stateless and rely entirely on the provided context window for each response.
-
•
The context window is essentially a text file aggregating system instructions, user queries, documents, and other relevant data.
-
•
All modern AI techniques (retrieval, augmented generation, tool use) aim to improve the quality and relevance of this context window.
-
•
Tool use allows the model to autonomously decide when to invoke external APIs or services based on the input query.
-
•
Agent models enhance tool use by planning and executing multiple tool calls in an iterative, reasoning loop until a task is complete.
-
•
Post-training with billions of examples significantly improves models' abilities in reasoning, tool use, and planning.
-
•
Designing AI products should begin with user needs and the necessary context rather than starting with complex agent architectures.
-
•
Prompt structure, including semantic content and organization (e.g., XML tags), helps the model parse context effectively but is flexible.
-
•
Token limits constrain the context window size; modern models like Google’s can handle up to a million tokens, enabling very large context inputs.
-
•
User-specific data (e.g., PTO policy, employee info) can be integrated into the context window dynamically through backend queries to provide accurate personalized responses.
Notable Quotes
"Models are stateless; they have no memory and forget everything after each response."
"Context design and context engineering mean figuring out and building what needs to go into that text file sent to the model."
"All the complicated-sounding techniques are just ways to put the relevant text into the context window."
"Think of the context window like an intern's briefing document: would the intern be able to answer the question with this information?"
"Tool use lets the model decide itself when to call external APIs or services to get needed information."
"An agent is a model using tools in a loop, making plans, reasoning, and calling tools until it’s done."
"Post-training on billions of examples is like training a dog over and over until it gets really good at reasoning and tool use."
"You never start AI product design from the technology itself; you start from the user outcomes and retro-engineer the needed context."
"Language is hard, and we use anthropomorphic words like reasoning and thinking to describe what the model does technically."
"If you understand how engineers think about these models, you won’t be scared of concepts like synthetic data or tool use."
Or choose a question:
More Videos
"To maintain tagging and freshness, you need content PMs with expertise, supported by robust content management processes."
Ben Davies Matt Duignan Andrew Michael Dr. Emily DiLeoExpert Panel: The Principles of Research Repository Design
March 11, 2022
"We are open source. Our work is public. You can fork it and have the code. That’s pretty fair as taxpayers."
Russ UngerGetting Out from Under Everyone: How to Escape the Paralysis of Getting Started
June 8, 2016
"Our bet was that distributing ownership would create more advocates and free bandwidth for strategic work."
Elizabeth Sklar Jessica ShengCo-creating research enablement with your tech org: a case study
March 10, 2026
"When difference comes together, something new emerges neither could have traveled alone."
Victor UdoewaTheme One Intro
March 27, 2023
"Evergreen content needs a strong perspective on why the topic matters along with practical examples on how to apply it."
Louis RosenfeldCoffee with Lou: Should You Write a (UX) Book?
March 7, 2024
"Being involved early in product planning lets us bring the art and science of research to where it can be most helpful."
Erin May Roberta Dombrowski Laura Oxenfeld Brooke HintonDistributed, Democratized, Decentralized: Finding a Research Model to Support Your Org
March 10, 2022
"No one is born knowing how to facilitate; it takes training, observation, and practice."
Alexandra SchmidtEnterprise UX Playbook
December 1, 2022
"We were spending time defending the meaning of words rather than discussing the content of the work."
Saara Kamppari-Miller"Prototype" vs "Prototype"--Breaking Down and Rebuilding Our Understanding of What We Do
October 24, 2019
"Space matters, but don’t start with the space; start by changing people, processes, and mindsets."
Sam YenDriving Organizational Change Through Design? Do more of this and less of that
June 9, 2017