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
The secret ingredient for impactful AI products is “evals”—an architecture for ongoing evaluation of quality. Without evals, you don’t know if your output is good. You don’t know when you’re done. Because outputs are non-deterministic, it’s very hard to figure out if you are creating real value for your users, and when something goes wrong, it’s really tricky to figure out why. Simply Put’s Peter van Dijck will demystify evals, and share a simple framework for planning for and building useful evals, from qualitative user research to automated evals using LLMs as a judge.
Key Insights
-
•
AI product development involves three layers: model capabilities, context management, and user experience, with evals central to experience quality assurance.
-
•
Automated evals help scale testing of AI with inherently open-ended inputs and outputs, enabling faster iteration cycles with confidence.
-
•
LLMs can serve as judges (evaluators) of other LLM outputs, which works because classification is cognitively easier than generation.
-
•
Defining what 'good' means for an AI system is a detailed, evolving process informed by research, domain expertise, and observed risks.
-
•
A three-option evaluation (e.g., yes/no/maybe) works better than fine-grained scales for consistent automated scoring by LLMs.
-
•
Synthetic data, generated by LLMs based on manually created examples, efficiently expands dataset breadth and usefulness.
-
•
Domain experts are essential for tagging data and establishing quality criteria, especially for high-stakes areas like healthcare or legal.
-
•
Building effective evals requires substantial effort—expect 20-40% of project resources devoted to this work.
-
•
Cultural differences impact subjective evals like politeness, requiring localization and careful domain definition.
-
•
AI product quality management is a strategic ongoing commitment, extending beyond initial development into production monitoring and iteration.
Notable Quotes
"AI products almost always have both open-ended inputs and outputs, which makes testing really hard."
"You have to build a detailed definition of what is good for my system to do meaningful automated evals."
"It’s much easier to classify an answer than to generate an answer, and that’s why LLM as a judge works."
"You don’t want to give too many options like rating from one to ten because consistency gets lost between different LLM calls."
"Synthetic data is useful because it’s easier to generate more examples of something you already have than to create entirely new data."
"If you launch in the US and politeness is an issue, first try to fix it with prompts; only if that fails should you build an eval."
"Evals are really your intellectual property—they define what good looks like in your domain."
"Domain experts are crucial for tagging data because users might say ‘that’s great,’ but experts can tell it’s totally wrong."
"You should plan 20 to 40 percent of your project budget on evals—it’s a lot more work than most people expect."
"This is where UX and product strategy bring huge value—defining what good means rather than leaving it to engineers alone."
Or choose a question:
More Videos
"Stakeholders are users too; the product we’re sharing is the research and learnings for their decision-making."
Sara LogelYour Colleagues are Your Users Too
March 29, 2023
"Enterprise problems are often engineering problems as much as design problems."
Dan WillisEnterprise Storytelling Sessions
May 13, 2015
"Finding your people inside an organization and being brave together is a great first step to climate action."
Aiyana Bodi James Christie Marc O'Brien Louis RosenfeldThree Key Climate Initiatives and How You Can Help
September 11, 2024
"Cross-functional relationships often matter more to output than relationships within the immediate team."
Liam ThurstonWhy Your Design Team Is Quitting, And How To Fix It
June 10, 2022
"The first year federal incentives ended, the market changed completely; buyers started listening to end users more."
Chris MosesStretching the Definition of DesignOps with Product Development
November 7, 2018
"Human tasks will become more complex and multi-dimensional as simple tasks get automated."
Janaki KumarInnovate with Purpose
June 14, 2018
"The pandemic pulled our remote team much closer—being physically apart made us feel closer."
Smitha Papolu Nova Wehman-Brown Melissa Schmidt Adam MenterTheme 3 Discussion
January 8, 2024
"One of the most important parts of any successful research study is your research sample."
Noah BondRedefining truth and inclusivity: Navigating data ownership and ethical research in the age of disinformation
March 11, 2025
"There wasn't much attention paid to onboarding team members—not the clients or users, but the actual team."
Tanya SnookDesigning the team experience: Building culture through onboarding
November 4, 2021
