I recently revisited the journey of Irving Fain, founder and CEO of Bowery Farming, and it reinforced a product leadership mantra I live by: preserve beginner’s mind while going exceptionally deep on the problem. Bowery is a modern farming company that grows produce indoors, free from pollutants and using significantly less water and space. Just this week, the company announced a $300 million Series C round, the largest private fundraise to date for an indoor farming company.
Bowery’s mission to democratize access to fresh, locally grown food. That’s an enormously complex challenge, and what makes it even more compelling is that Irving didn’t come from agriculture. He was previously the CEO and founder of CrowdTwist, a loyalty and analytics solution that was eventually acquired by Oracle, and helped build iHeartRadio. As a product leader, I’ve seen how crossing domains can unlock first-principles thinking that incumbents often overlook.
Looking back on the early days of Bowery, Irving believes his naivety was in fact an asset. Coming in with no preconceived notions about how to solve the problem, he committed to approaching agriculture with a wide aperture and going unreasonably deep. In my experience, that combination—breadth of exploration and ruthless depth—separates breakthrough products from incremental ones. I especially appreciate his discipline of paying just as much attention to the doubters as to the folks who believed in the vision. When I’m validating a thesis, I interview skeptics first, pressure-test assumptions, and map out what would have to be true for the idea to work.
A multi-pronged discovery approach like Irving’s is a playbook I recommend often: define the problem in user language, list the riskiest assumptions, seek disconfirming evidence early, and prototype thin slices that target the biggest unknowns. This is how you de-risk complex systems—whether it’s indoor farming or enterprise SaaS—by turning ambiguity into an ordered queue of learnable risks.
What also stood out to me was the rigor in assembling Bowery’s small-but-mighty team of five. He kept the team deliberately small and sought out folks that didn’t have vast agriculture experience and could approach problems from first principles. In early product stages, I hire for rate of learning, adjacent technical depth, and cognitive diversity. Small teams move faster when they share a clear outcome, a strong culture of experimentation, and the freedom to question every constraint.
For founders, product leaders, and ambitious ICs contemplating the leap, this story offers both inspiration and practical guidance: protect naivety, operationalize first principles, and build a team that learns faster than the problem evolves. The $300M milestone is a signal, but the real lesson is the system that produced it—unreasonable depth, disciplined discovery, and a culture unafraid to rethink the field from the ground up.
You can follow Irving on Twitter at @ifain
To learn more about Bowery Farming and its most recent fundraise, https://techcrunch.com/2021/05/25/indoor-farming-company-bowery-raises-300m/amp/
What is the core mindset the post advocates for product leadership?
The core mantra is to preserve a beginner’s mind while going unreasonably deep on the problem. This breadth-plus-depth approach helps unlock first-principles thinking that incumbents overlook.
How is Bowery Farming's team described in the post?
Bowery’s team is described as small-but-mighty (five people) chosen for first-principles problem solving rather than agriculture experience. Small teams move faster when they share a clear outcome and a culture of experimentation.
What is the practical discovery playbook mentioned?
Define the problem in user language, list the riskiest assumptions, seek disconfirming evidence early, and prototype thin slices that target the biggest unknowns. This approach helps de-risk complex systems.
What is the significance of the $300M milestone?
The milestone is a signal, but the real takeaway is the system that produced it—unreasonable depth, disciplined discovery, and a culture unafraid to rethink the field from the ground up.
What practical guidance does the piece offer for founders and product leaders?
Protect naivety, operationalize first principles, and build a team that learns faster than the problem evolves. This guidance is framed as directly applicable to finding product-market fit in complex domains.
Leave a Reply