💡

InsightHunt

Hunt the Insights

E

Eric Ries

Episode #94

Founder and Executive Chairman

Long-Term Stock Exchange (LTSE)

Execution🎯Product Strategy🔍User Research

📝Full Transcript

28,697 words
Eric Ries (00:00:00): People act like having a startup fail is the worst thing that can happen to you. And man, that's not even in the top 10. It's bad, I've done it, it's awful. It's really bad, but far worse is to be in a company that won't die, a zombie, undead company that you hate, but you can't leave. Oof, have I met people like that, and we're having a mental health crisis among founders that's not talked about enough. People have started to talk about the downside mental health risk, obviously the stress of being a founder is hard, but look what's happening to the people that are so-called successes? When you build a company and you sell it out and it becomes something that you find abhorrent, man, maybe you get rich, but it's not good. And so building a company you hate, that becomes a maligned force in the world, that you have to go pretend you weren't involved with or like you feel complicit in... That's way, way worse, and I wish more founders would take that more seriously early on. Lenny (00:00:58): Today, my guest is Eric Ries. If you're not familiar with his work, I would be shocked. He is most famous for creating the Lean Startup methodology and movement and also his incredibly influential book, The Lean Startup. He also coined more terms and concepts that are part of the tech culture than anyone I could think of. He currently spends his time advising founders and startups. He was a former founder and CTO, and currently is the founder and executive chairman of the Long-Term Stock Exchange. (00:01:24): This is now my favorite episode of the podcast and I can't wait for you to hear it. In our conversation, we cover a lot of ground, including the current state of the Lean Startup movement, where he sees things heading, what Eric would redo if he could do it over again, misconceptions about the methodology that frustrate him most, how AI will likely impact product development in startups, how to think about MVPs correctly, when to pivot and when to st...

💡 Key Takeaways

  • 1If you have to ask whether you have Product-Market Fit, you don't have it. PMF feels like a whirlwind where you have no time to ask existential questions.
  • 2A 'Marketing Launch' and a 'Product Launch' are separate events. You can release a product to customers for learning purposes without a public announcement.
  • 3The 'Pivot' is often a process of self-discovery; founders often discover their true vision only after the first iteration fails, rather than having a fixed vision from day one.
  • 4Fearing startup failure is irrational compared to the much worse fate of running a 'zombie company'—a business that won't die but isn't succeeding, trapping you in a job you hate.
  • 5When customers complain about a missing feature in your MVP, that is positive validation. The real danger is when they complain about things you didn't even know existed.
  • 6High craft and design can be part of an MVP, but only if 'craft' is a specific leap-of-faith assumption you are testing. Otherwise, it is often just a delay tactic to avoid feedback.
  • 7Corporate governance and alignment issues will be the biggest bottleneck for AI deployment, as AI models tend to reflect the organizational dysfunction of the teams that build them.

📚Methodologies (3)

Execution

A ruthless heuristic for scoping an MVP that ensures you are testing the leap-of-faith assumption rather than satisfying the founder's ego. It shifts the focus from 'building a product' to 'testing a hypothesis' while containing liability.

Core Principles

  • 1.Write down every feature you think is necessary for the launch.
  • 2.Cut that list in half. Then, cut it in half again. Build that.
  • 3.Treat the MVP as a 'baseline' to measure improvement, not a final destination.
  • +1 more...

"Write out the list of features that are necessary in your MVP. Cut it in half and cut it in half again and build that."

#recursive#execution#process
View Deep Dive →
🎯 Product Strategy

A tactical approach to forcing a decision between pivoting and persevering by removing the ambiguity of 'it might work eventually.' It uses a fixed timebox to force empirical reality upon the team.

Core Principles

  • 1.Admit the current state: Acknowledge that you are currently in the 'zombie' zone (not growing, not dying).
  • 2.Set a strict timebox (e.g., six weeks) where the entire team focuses 100% on moving one specific metric.
  • 3.If the needle doesn't move significantly by the deadline, convene a 'reset meeting'.
  • +1 more...

"If you're asking whether you should pivot or not, you probably know the answer already."

#six-week#truth#protocol
View Deep Dive →
🔍 User Research

A method to test value propositions in high-stakes environments without building the physical or complex underlying product first. It relies on selling the promise (specs/outcome) before the product exists.

Core Principles

  • 1.Identify the 'Leap of Faith' assumption (e.g., customers care about efficiency).
  • 2.Create high-fidelity marketing materials (brochures, datasheets, landing pages) that promise the ideal specifications.
  • 3.Attempt to get a pre-order or a letter of intent based solely on the brochure.
  • +1 more...

"We can build a really high quality brochure in a tiny fraction of the time it takes to build the actual machine."

#brochureware#simulation#research
View Deep Dive →