By playing, you agree to uListen's Terms and Privacy Policy and YouTube's Terms of Service.
Aakash GuptaWhat AI PMs REALLY Need to KNOW in 2026 (Agents, Discovery, EVERYTHING)
Summaries, chapters, transcripts, and FAQs on this page are made by uListen, not YouTube.
At a glance
WHAT IT’S REALLY ABOUT
2026 AI PM playbook: technical fluency, evals, roadmaps, governance, execution
- AI PM demand is rising fast, but “AI PM” labeling is a marketing and scarcity game that will be heavily scrutinized in hiring due to rampant AI-washing.
- To upskill, PMs should build firsthand model fluency (tradeoffs, privacy, residency), understand data pipelines/RAG, and practice prompt engineering as a core communication layer with LLMs.
- As products become agentic, PMs need working knowledge of observability (trace analysis), production realities (SRE boundaries, access controls), and cost/performance optimization tied to gross margins.
- Evals become a PM-owned domain because PMs best define quality and user outcomes, while engineers supply the harnesses and infrastructure to run evaluation at scale.
- Strong AI roadmaps avoid shiny-object chasing by focusing on hard workflows, leveraging unique data/context, killing weak features quickly, and communicating a clear narrative to stakeholders and boards.
IDEAS WORTH REMEMBERING
5 ideasDon’t claim “AI PM” unless you can back it up in depth.
Olson warns that premium pay invites deeper interrogation, and AI-washing is increasingly obvious in resumes and company positioning; credible experience means shipping successful AI features in production at scale.
AI is both a work accelerant and a product capability—PMs must do both.
PMs should use AI for prototyping, competitive research, and speed (e.g., Deep Research, rapid prototyping tools), while also identifying where LLM APIs can quietly improve product features even without “AI” marketing.
Model fluency is table stakes: tradeoffs beat brand loyalty.
Teams should continuously test models (OpenAI, Anthropic, Gemini, open source) across use cases, weighing quality, latency, cost, data residency, and vendor/legal friction like DPAs and country availability.
RAG and data pipelines are foundational because context quality determines output quality.
Understanding embeddings, vector stores, ingestion, retrieval, and context window limits helps PMs reason about relevance, confusion from too much context, latency, and scaling constraints in real products.
Trace analysis matters for agentic systems, but PMs must navigate ownership boundaries.
As agents call tools/other agents, tracing helps pinpoint failures and inefficiencies, yet larger orgs often reserve deep ops/debug work for engineering/SRE due to division of labor and access controls.
WORDS WORTH SAVING
5 quotesYou better damn well be good and know what you're talking about if you're gonna call yourself an AI PM.
— Todd Olson
RAG is kind of a de facto way to build… you wanna give the right context.
— Todd Olson
This is a real issue… how you build and design systems affects your cost of goods sold… and gross margin.
— Todd Olson
The PM is probably the best suited human being to author and manage these [eval] sets.
— Todd Olson
Throw it away. Do not hold onto it.
— Todd Olson
SPEAKERS
Aakash Gupta
hostHost of the Aakash Gupta channel who interviews product leaders about AI product management.
Todd Olson
guestProduct leader at Pendo discussing AI PM fundamentals, agents, evaluation, and workflow-focused product strategy.
High quality AI-generated summary created from speaker-labeled transcript.
