Dec 7, 2022 · 1h 7m · news
Marty Cagan: Product Lessons from Steve Jobs and Elon Musk; Why do we idolize engineers? | 20VC #957 · 20VC with Harry Stebbings
0:00 / 0:00
▶ Watch on YouTube →
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
In this insightful interview, Silicon Valley product veteran Marty Cagan shares essential frameworks for rigorous product discovery, team empowerment, and commercial execution while warning against the pitfalls of process-driven leadership.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. Harry holds 15% of the talking time here. How this is scored →
Harry as informed peer 4.0 Guest teaching 4.6 Guest disagreement 1.3 Harry pushing back 2.6
speaking balance: gold is Harry, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 24:46 Marty rejects asking customers what features they want
Marty dismisses naive founder approaches to customer feedback, stating bluntly that we don't care what customers say because they don't know what's possible.
Hardest push from Harry ▶ 25:19 Harry directly challenges the utility of qualitative researchHarry interrupts Marty to challenge his premise, directly asking if qualitative feedback even matters if customer statements cannot be trusted.
Biggest teaching moment ▶ 11:20 Marty reframes primary versus secondary risk for foundersMarty educates Harry and founders on how business school graduates obsess over spreadsheets and business model risks while ignoring the primary risk of product value.
Harry holds his own ▶ 52:04 Harry diagnoses the problem of cosseted product leaders and engineersHarry demonstrates strong industry insight by calling out modern tech companies for shielding engineers and PMs from basic P&L and go-to-market discipline.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Harry as informed peer | Guest teaching | Guest disagreement | Harry pushing back | Why |
|---|---|---|---|---|---|---|
| Leadership and Lessons from Tech Giants | 2 | 3 | 1 | 1 | Harry acts primarily as a receptive fan and interviewer, asking open-ended questions about Marty's time with Marc Andreessen and Pierre Omidyar. Marty offers reflective insights on leadership and humility, sharing Marc Andreessen's lesson about knowing what you cannot know. | |
| Navigating Primary vs. Secondary Risks | 2 | 5 | 1 | 1 | Harry asks a clarifying question on nomenclature regarding primary vs secondary risks. Marty educates Harry and the audience on why business model and monetization risks are secondary compared to the primary risk of creating a product people actually want. | |
| The Four Risks of Product Discovery | 2 | 6 | 1 | 1 | Harry asks what critical questions must be answered in product discovery. Marty systematically outlines the four core risks: value, usability, feasibility, and viability, delivering a masterclass framework with Harry in listening mode. | |
| Outcomes Over Outputs: Executing Efficient Product Discovery | 4 | 5 | 1 | 2 | Harry offers his own observation regarding founders building features rather than products in HR tech. Marty validates this distinction, explaining output versus outcomes and comparing slow iteration cycles to modern product discovery. | |
| Uncovering the Truth in Qualitative Feedback | 5 | 6 | 2 | 5 | Harry challenges Marty on customer feedback reliability, asking whether qualitative feedback even matters if buyers lie. Marty re-frames qualitative feedback as a tool to uncover flaws rather than seek validation. | |
| Hiring and Structuring the First Product Team | 5 | 5 | 2 | 5 | Harry challenges Marty's assertion that a founder should wait until 25-30 engineers before hiring a PM. Harry also pushes back on interview tests and brings up David Lieb's strategy on hiring outside domain expertise, which Marty agrees with. | |
| Onboarding, Coaching, and Empowering Teams | 6 | 4 | 1 | 3 | Harry articulates a strong critique of tech leaders cosseting engineers and product managers instead of holding them accountable to business metrics and financial realities. Marty enthusiastically agrees, condemning outsourced engineering. | |
| Resolving Tension Between Product and Sales | 7 | 3 | 2 | 4 | Harry introduces Shreyas Doshi's PM taxonomy and aggressively critiques 'operator' product managers who introduce process and red tape. He offers a cultural theory on why European tech leaders rely heavily on process, drawing out Marty's agreement. | |
| Quickfire Round: Advice, Strategy, and Future of Product | 3 | 4 | 1 | 1 | In a brisk quickfire round, Harry prompts Marty on career advice, product strategy, and industry trends. Marty critiques the misuse of Agile 'product owner' roles and praises Tesla and TikTok. |
Statements from this episode (23)
Great products come from product teams, not individual product managers
“I've never seen a product come from a product manager. I've only seen great products come from product teams.”
Marc Andreessen is the smartest person Marty Cagan has ever met
“Marc Andreessen is literally the, I think the smartest person I've ever met.”
The essence of product discovery is knowing what you cannot know
“The most important thing is to know what you can't know. And isn't that essentially a lesson in humility, right? It's like you need to know what you can't know, because that is really the essence of product discovery.”
Founders gravitate toward risks they feel comfortable with
“Most founders gravitate to the risks they're more comfortable with.”
Startup failure stems from inferior solutions, not a lack of demand
“The issue is rarely demand. The issue normally is the solution that you've come up with is not significantly better than the alternatives that are out there. And if it's not significantly better than the alternatives, people won't switch to your product.”
Value risk is usually the hardest challenge in product discovery
“The first one is. Is it valuable? In other words, will people buy it or if they've already bought it or if it's a free service, will they choose to use it? That's the value question. Usually that's the hardest one, not always, but usually it's the hardest one.”
Product success rates are not increasing despite faster feature output
“The percentage of companies or products that do better is not really going up.”
Startups need 50 to 100 attempts to reach product-market fit
“You will probably need to do between 50 and a hundred attempts before you get to product market fit.”
Product teams can validate or invalidate ideas within hours
“Most of the time we can figure out in hours that this is not right. Hours, sometimes minutes. In fact, it's not unusual to do a dozen iterations in a day.”
Qualitative research should find product flaws, not seek affirmation
“With qualitative feedback, your goal is to find all the things that are wrong with the product. So that's the difference. You're not looking for affirmation, which is what these, you know, naive founders are doing. They're not, you're not doing that. You're ac…”
Marty Cagan will not invest without a proven product leader co-founder
“I personally never invest in a startup unless at least one of the founders is a proven product leader.”
Startups must hire product managers when engineering reaches 25 to 30 people
“Realistically, once you get past about 25, 30 engineers, a founder is saying like, I, or the teams are saying, I can't get enough time with the founder.”
Product vision is a startup's primary tool for attracting top talent
“The biggest reason somebody great would join your company is because of your product vision.”
Almost all innovative products are built by teams without domain expertise
“Look across our industry, across time, at all the innovative products, almost all of them came from people and teams that had no real domain experience.”
Using engineers only to code yields half their potential value
“If you're just using your engineers to code, you're only getting about half their value.”
Empowered engineers are foundational to top tech companies like Tesla and Apple
“There is nothing more than, more important than empowered engineers. And if you look, you know, if you look at companies like Tesla, SpaceX, Google, Amazon, Stripe, Apple, that's the foundation of every one of those companies, empowered engineers.”
Founders who outsource engineering to firms like Accenture are not serious
“When I find a founder that thinks that engineers are somebody you can just do a contract with Accenture or somebody. I'm like, you're not serious about this. Come back. If you decide to get serious.”
Big Tech success does not guarantee success at new startups
“They get somebody from Amazon, they get somebody from Stripe, somebody that's clearly experienced what good looks like. But then they assume that just because they were successful there, that they're going to be successful in our company. And that's not a true…”
Product teams are ultimately responsible for sales performance
“And the bottom line is the responsibility for the sales is on the product team.”
Process-driven product leadership is a bigger issue in Europe than the US
“The problematic behaviors that you're describing, which by the way, you are spot on. And I hate to say this cause I absolutely love Europe, but it's a bigger problem in Europe than it is in the U S. And the re the reason is because so many of those people are …”
Writing product narratives forces deep thinking and accelerates execution
“Like Stripe, Amazon, they believe think deeply to really. So for example, the written narrative is a way to force you to really think Think things through and then you're gonna move a lot faster.”
Feature teams operate as mercenaries, whereas empowered teams own outcomes
“In an empowered team, you are literally giving ownership responsibility to the team. And so that they build those skills. They build that confidence. They build those muscles in a feature team. They're literally just mercenaries doing what they're told.”
Tesla's product strategy is phenomenal and tied to its financing
“I would say what Tesla has pulled off is nothing short of amazing. Amazing on every level. Just phenomenal. And their product strategy has been a very visible product strategy. They kind of had to because it tied in so closely with the financing strategy.”