The 'Ops First' Validation (Dream Big, Start Small)
by Keith Yandell • Chief Business Officer (formerly led Legal, HR, Marketing, Support, Sales) at DoorDash
A longtime leader at DoorDash who has managed a diverse range of functions including legal, HR, marketing, customer support, and currently BD and corporate development. Known for his generalist leadership style and ability to unify teams, he previously led litigation at Uber.
🎙️ Episode Context
Keith Yandell shares his unique journey leading multiple disparate functions at DoorDash, emphasizing the power of generalist leadership and 'no asshole' culture. He breaks down his tactical frameworks for scaling culture through written documentation, driving consensus in high-stakes meetings, and the critical collaboration between BD and Product teams.
Problem It Solves
Wasting expensive engineering resources on partnerships or features that haven't been proven to have market demand.
Framework Overview
Instead of building bespoke tech integrations immediately, use manual operations to test the value proposition. Only build the scalable platform after the manual test proves successful.
🧠 Framework Structure
Do Things That Don't Scale: Manually ...
Validate via Ops: Check if the operat...
Build Platforms, Not One-offs: Once v...
When to Use
When Business Development (BD) brings in a 'huge opportunity' that requires significant product roadmap deviation.
Common Mistakes
Building a full integration based on corporate headquarters' promises without testing franchisee/end-user adoption.
Real World Example
DoorDash failed with a hotel room service integration because they built the tech before realizing franchisees wouldn't support it. They should have tested it manually first.
We invested heavily in a partnership... and it was a total flop... I should have gone out and stood out front with a promo code.
— Keith Yandell