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 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
"Unfortunately, that natural, spontaneous connection in person is something we can’t fully replicate virtually; it has to be scheduled and intentional."
Nicole UmphressDelivering Design Education During a Global Pandemic: Lessons Learned
June 9, 2022
"I’ve found that being approachable and providing space for Q&A helps build trust and confidence in the design ops practice."
Michelle ChinThe DesignOps Starter Kit
September 29, 2021
"You really have to use a broader net of the titles and levels you’re looking for because you’re not gonna find the perfect fit just within the title."
Abbey SmalleyToday’s Design Ops and Programs Landscape & Career Paths
October 4, 2023
"Tomorrow of design ops belongs to those who lead with foresight into designs and designers future, to stay human and resilient."
Ebru NamaldiDesigning the Designer’s Journey: Scaling Teams, Culture, and Growth Through DesignOps
September 11, 2025
"Startups struggle daily with pricing, and conjoint analysis is the single most underrated tool to find optimal prices."
Ricardo MartinsUnlocking the power of advanced quantitative methods
March 12, 2025
"We found design managers want team health, DesignOps managers want standardization, product managers want transparency, and producers want autonomy."
Aurobinda Pradhan Shashank DeshpandeIntroduction to Collaborative DesignOps using Cubyts
September 8, 2022
"Join together as a community inch by inch to find a way through what feels impossible."
Jemma AhmedTheme Three Intro
March 29, 2023
"What if we are optimizing ourselves into relevance?"
Patrizia BertiniThe (r)evolution of designOps: It’s Time to Think (really) BIG
September 11, 2025
"If you hear what I’m saying and you’re uncomfortable, and I say I’ll do it your way, now you’re connected and you’ll back me until you can’t anymore."
Jacqui Frey Dan WillisPanel Discussion: Integrating DesignOps
November 7, 2018