What does product management look like when your engineers aren't writing code? Rags Vadali, founder of Floto and former PM at Google and Meta, joins Lily and Randy to talk about how building AI-native products has completely inverted his process. No PRDs, prototypes before specs, and a new artefact at the centre of it all: the Product Experience Document (PXD).
They get into why the real product when you're building an agent is the experience layer on top of it, how synthetic personas work (and where they don't), and what discovery still requires that AI can't replace.
Plus: what product sense means when everyone on your team is shipping code.
Chapters
Key Takeaways
The product is now the experience layer. When you're building an agent, the UI is no longer the product. The real work is defining what experience users have on top of the agent — and that requires a different kind of spec.
Invert the process when the engineers are faster than the spec. At Floto, engineering goes first. PMs come in after the prototype to shape what the experience should be. The old flow — spec, design, build — breaks down when foundation model capabilities are changing faster than you can document them.
Synthetic personas are useful early, but limited. They reflect average user behaviour, not edge cases. The most useful technique: ask negative questions. "What would make you pause before clicking?" yields sharper insights than "Why would you click?"
Discovery principles haven't changed. The products that resonate still come from talking to real people. AI helps you scale signal-gathering — Reddit, G2, Perplexity queries — but the gold standard remains direct user conversations.
The PXD is written for agents, not just people. The Product Experience Document covers: why, success criteria, experience principles, example interactions (good/bad/ugly), critical moments, conversation closing, and success metrics. Engineers fed sections directly into Claude to generate prompts — which reshaped how Rags thought about the format.
Non-deterministic systems need ranges, not requirements. You can't specify a single correct behaviour for an agent. The PXD encodes a range of acceptable answers, hard stop moments, and anti-patterns — because guardrails matter as much as ideals.
Product sense is now a universal hiring criterion. When everyone is shipping code, everyone needs to understand how users will experience what they build. Rags applies a product sense interview to every role, regardless of function.
