CHAPTERS
From Microsoft to Vanta: why “comfort” can stall your growth
Jeremy opens with a key career regret: staying at Microsoft too long despite switching teams internally. He frames comfort as a warning sign—useful for stability, but dangerous for learning velocity and long-term trajectory.
Early Microsoft PM reality: waterfall specs, small scopes, and distance from customers
Jeremy contrasts pre-modern PM at Microsoft with today’s practices: long spec templates, inward-facing decision-making, and PMs wearing many hats with limited customer contact. He explains how Vanta intentionally designs broader PM scopes and a thinner PM team.
PM:Eng ratio and AI prototyping tools reshaping EPD collaboration
They discuss the trend toward PMs supporting more engineers and how AI prototyping accelerates the feedback loop. Jeremy shares how Vanta equips PMs with tools like v0 and expects more overlap across product, design, and engineering.
Guardrails and handoffs: how to prevent AI tooling from creating chaos
Jeremy explains how he avoids a one-size-fits-all operating model and instead lets teams vary based on strengths. He emphasizes design accountability for shipped craft, tighter design-engineering implementation loops, and a future pipeline from prototyping tools into production code.
Outlook at billion-user scale: remote collaboration, protocols, and privacy tradeoffs
Jeremy describes day-to-day PM work on Outlook/outlook.com—distributed across Redmond and Silicon Valley—plus deep technical and policy debates. They cover threading, spam filtering, storage constraints, ads, and the privacy implications of targeting.
How big-company features got built: PRDs, architecture, and global readiness
They break down how a feature like threading would be conceived and shipped inside Microsoft. Jeremy highlights heavy documentation, technical PM involvement, and the overhead of internationalization/accessibility requirements.
How PM evolved over 16 years at Microsoft—and Satya’s strategic reset
Jeremy summarizes broad shifts: larger PM scope, stronger design voice, greater business/customer connection (especially enterprise). He also contrasts Ballmer-era revenue focus with Satya’s clarity, prioritization, and successful acquisition strategy.
Climbing the ladder: saying no, cutting your own scope, and switching domains
Jeremy shares the behaviors that drove promotions: creating focus, questioning whether work still matters, and being willing to cut even “your” projects. He also advocates changing teams every few years to keep learning and avoid identity lock-in.
Director/VP inflection: end-to-end business ownership and audience-aware communication
They discuss what separates senior PM leadership: owning go-to-market, pricing/packaging, onboarding, and implementation—not just features. Jeremy also stresses adapting communication to the audience, from CEOs to sales to engineering.
GitHub lessons for PMs: learn to code, understand workflow, translate engineering “why”
Jeremy argues that PMs benefit from understanding developer workflows and fundamentals even as AI coding tools improve. He explains how PMs can strengthen trust with engineering by asking “why,” translating technical work into customer outcomes, and emphasizing quality—especially for AI products.
What VP Product is really like: always-on accountability, sales enablement, and staying close to the product
Jeremy describes VP realities: incidents, executive visibility, heavy customer interaction, and close partnership with solution engineering/sales. He warns against becoming a pure “translation layer” and advocates carving out time to do real IC work to stay connected to product quality and craft.
Landing the CPO role at Vanta: timing, founder fit, and a ‘no surprises’ recruiting process
Jeremy explains his search criteria (growth-stage, scaling phase, not seed) and how Vanta re-engaged him after an initial pass. He highlights the importance of founder chemistry, cultural alignment, and Christina’s transparency—IC conversations, spec reviews, and GTM exposure before joining.
Vanta’s growth engines and product differentiation: automating trust management end-to-end
Jeremy details Vanta’s evolution from SOC 2 automation for startups to a broader trust management platform for enterprises. He emphasizes building a security feedback loop (what buyers ask for), expanding product lines (VRM, trust centers, questionnaires), and competing via superior UX in a category known for poor experiences.
AI tool adoption at Vanta: strict data guardrails, enablement, and zero tolerance for hype
Jeremy describes how Vanta encourages experimentation while enforcing one key security boundary: don’t put customer data into tools that may train on it. He also shares an important adoption lesson—tools don’t spread by mandate; leaders must enable use (templates, Loom demos) and validate real value beyond flashy demos.
How Jeremy evaluates and coaches PMs: the “3 Bs,” ambiguity, and customer pain mapping
He shares a practical evaluation lens (vision, execution force, relationship-building) and how expectations change with seniority: larger ambiguous problems, then self-directed problem-finding. For new PMs, his advice centers on deep customer understanding, ROI framing, and learning from sales calls.
Get more out of YouTube videos.
High quality summaries for YouTube videos. Accurate transcripts to search & find moments. Powered by ChatGPT & Claude AI.
Add to Chrome