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
"If you want to avoid time zone confusion, you can switch the conference schedule to your local time on the program page."
Bria AlexanderOpening Remarks
November 17, 2022
"You’re constantly training people and optimizing protocols even after successful implementation."
Sofia QuinteroBeyond Tools: The Messy Business of Implementing Research Repositories
March 10, 2022
"I knew that probably 80% of the problem was about teamwork and maybe 20% was about stuff we needed to build."
Alana Washington(Remote) Service Design: A Transformation Case Study
June 8, 2022
"More frequent change isn't always better; good communication and team pulse are key."
Deanna SmithLeading Change with Confidence: Strategies for Optimizing Your Process
September 23, 2024
"Handwritten notes have no boot up time, and that immediacy helps enter deeper flow states."
Jorge ArangoThe Best of Both Worlds: How to Integrate Paper and Digital Notes (1st of 3 seminars)
April 5, 2024
"Support software used to be really shitty and expensive, and Zendesk set out to fix that by making it beautifully simple."
Jilanna WilsonDistributed Design Operations Management
October 23, 2019
"I’m regularly pleasantly surprised by not having to explain a lot of the foundational concepts of design when working with others inside government."
Ariel KennanTheme Two Intro
November 17, 2022
"We try to keep things as consistent as possible in terms of the API but document where platforms need to deviate to be good citizens of their environment."
PJ Buddhari Nate BaldwinMeet Spectrum, Adobe’s Design System
June 9, 2021
"Most of the primitives of how you do work are portable to climate tech from other industries."
Dem Gerolemou Alexis Oh Neef RehmanClimate technology fundamentals
May 15, 2024