Overview
Steve Blank's Customer Development and the broader Lean Startup methodology have been widely adopted but also face substantive criticisms. This note collects the major critiques and their sources.
Criticisms
"Customers can't evaluate what doesn't exist yet"
The most fundamental critique: Customer Development assumes customers can articulate their needs, but for truly innovative products, customers may not be able to evaluate something they have never seen. This echoes Henry Ford's (probably apocryphal) observation about faster horses and Steve Jobs' famous skepticism about customer research. The critique suggests that Customer Development works best for incremental innovation but may be inappropriate for breakthrough products.
Over-reliance on customer feedback (Keith Rabois)
Keith Rabois (PayPal, Khosla Ventures) has argued publicly that the lean startup approach over-indexes on customer feedback at the expense of founder vision. Rabois' position is that great products come from opinionated founders who build what they believe is right, not from aggregating customer opinions. This represents the "product vision" school of entrepreneurship vs. the "customer learning" school.
"The Limits of the Lean Startup Method" (HBR)
Harvard Business Review has published critiques noting that lean startup methods have limits, particularly for capital-intensive industries, regulated markets, and hardware products where iteration cycles are long and costly. The core lean assumption — that you can cheaply test and iterate — breaks down when each iteration requires significant capital expenditure or regulatory approval.
Reforge / Brian Balfour critiques
Reforge and its founder Brian Balfour have argued that the lean startup framework over-simplifies growth and product-market fit. The critique is that "validated learning" and MVP testing tell you whether something works but not why, and that the framework lacks sophistication in areas like growth modeling, retention analysis, and channel strategy.
Design Thinking vs. Customer Development
Blank himself addressed the relationship between Design Thinking and Customer Development in a 2014 blog post, arguing they are complementary rather than competitive. Design Thinking (IDEO, Stanford d.school) focuses on empathy and ideation — understanding the problem space. Customer Development focuses on validation — testing whether the solution works as a business. Critics from the design thinking camp argue that Customer Development starts testing too early, before the problem is properly understood.
Survivorship bias in methodology development
A structural critique: Blank developed Customer Development by analyzing his own startup experiences, but the methodology is inevitably shaped by survivorship bias. The startups he participated in that succeeded (especially E.piphany) may have succeeded for reasons unrelated to customer development practices. The methodology was codified retrospectively, not tested prospectively.
Blank's Response Pattern
Blank has generally been open to criticism and has addressed many critiques directly on his blog. His typical response is to acknowledge the limits while arguing that the alternative — building without customer validation — has a much higher failure rate. He has also noted that Customer Development was never intended for all contexts, particularly not for science/technology breakthroughs where the technology itself is the uncertainty (as opposed to the business model).
Related Research
See further-research-opportunities for gaps in the Blank KB that could benefit from further research.
Sources: steveblank.com, HBR, Keith Rabois public statements, Reforge blog, Stanford d.school