💡

InsightHunt

Hunt the Insights

K

Keith Yandell

Episode #168

Chief Business Officer (formerly led Legal, HR, Marketing, Support, Sales)

DoorDash

👥Team & Culture⚡Execution🎯Product Strategy

📝Full Transcript

11,406 words
Keith Yandell (00:00): Every business that you have heard of has gotten rejected by at least a handful of venture capitalists at one point or another. And so that drive to keep going if you believe in the business is critical, absolutely critical. I mean, we were weeks of runway situation and had been told no by everyone. And it was just Tony's drive, really, to keep going. And the way he explains it to me is it's just the difference between a founder and a non-founder. If you're really a founder, you just have to find a way. You have to keep going. There's no question. And I mean, that's the only advice I can give folks, is it only takes one yes. But you got to keep going. Lenny (00:44): Welcome to Lenny's Podcast, where I interview world-class product leaders and growth experts to learn from their hard-won experiences building and growing today's most successful products. Today my guest is Keith Yandell. Keith is a longtime leader at DoorDash, where he's been for about seven years. And in that time, get this, he's led the legal team, the HR team, the marketing team, the customer support team, and currently he leads the BD and corporate development teams. Before DoorDash, he led litigation at Uber. He's also managed folks like Gokul Rajaram, who was previously on this podcast and who suggested that I have Keith on. And damn, was he right. Before I had this chat with Keith, I didn't know that much about him, but now you can count me as a huge Keith fanboy. I suspect you'll feel the same way after you listen to this episode. I'm just going to jump right in and bring you Keith Yandell after a short word from our wonderful sponsors. Lenny (01:38): Today's episode is brought to you by OneSchema, the embeddable CSV importer for SaaS. Customers always seem to want to give you their data in the messiest possible CSV file. And building a spreadsheet importer becomes a never-ending sink for your engineering and support resources. You keep adding features to your spreadshee...

💡 Key Takeaways

  • 1Generalists can often outperform specialists in leadership roles by reinventing systems rather than following tradition.
  • 2To scale culture, create a 'User Manual' for yourself that outlines your flaws and commitments to the team.
  • 3Commit to helping direct reports find their next job, even if it's outside the company, to build trust and get honest feedback.
  • 4Use the 'Steel Man' argument technique to generate empathy and resolve conflicts between teams.
  • 5For BD/Product partnerships, 'Do things that don't scale' first (manual ops) before building scalable tech platforms.
  • 6Demand constructive feedback (T3 B3 method) to create a safe space for improvement.
  • 7Urgency and compound interest in shipping speed are critical for beating competitors.

📚Methodologies (3)

👥 Team & Culture

A transparent document shared with the team that outlines the manager's operating principles, weaknesses, and commitments. It accelerates psychological safety and sets clear expectations.

Core Principles

  • 1.Be Vulnerable: Explicitly list areas you are trying to improve (e.g., 'I argue for sport') so the team isn't confused.
  • 2.Define Expectations: Clearly articulate what traits successful people in the org possess.
  • 3.The Exit Commitment: Commit to helping them find their next job (even external ones) to foster radical transparency.

"I know you don't know how to do this stuff. That's why I'm putting you in the role."

#manual#team#culture
View Deep Dive →
⚡ Execution

A negotiation technique that forces opposing sides to articulate the other's argument to build empathy, followed by clear decision-making protocols.

Core Principles

  • 1.Steel Manning: Ask Side A to make Side B's best argument (e.g., 'Tell me the top 3 reasons we should focus on growth over profit').
  • 2.Clarify the Tiebreaker: Establish upfront who makes the final call if consensus isn't reached (CEO, GM, or Head of Product).
  • 3.Set a Time Horizon: Define a strict deadline for the debate to end and the decision to be executed.

"That generates instant empathy for the other side. And sometimes, they'll even persuade themselves as they're talking."

#'steel#consensus#execution
View Deep Dive →
🎯 Product Strategy

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.

Core Principles

  • 1.Do Things That Don't Scale: Manually simulate the experience (e.g., handing out coupons physically) before writing code.
  • 2.Validate via Ops: Check if the operational reality (e.g., franchisee buy-in) supports the product vision.
  • 3.Build Platforms, Not One-offs: Once validated, product should build a scalable solution for all partners, not a custom hack for one deal.

"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."

#first'#validation#(dream
View Deep Dive →
← Browse All Episodes