In the Lean Startup you described Aardvark tested several different business concepts, before choosing one in the end. Do you know how they dealt with the possible need to pivot versus focusing the team's resources on one single product? Or have any other advice in terms of focus versus testing different products?
I Am Eric Ries, Author of the Lean Startup. AMA
51–60 of 115 posts
Re: I Am Eric Ries, Author of the Lean Startup. AMA
#52Are you planning to setup a program for consultants, advisors or trainers to get certified on the-lean-startup-approach?
Re: I Am Eric Ries, Author of the Lean Startup. AMA
#53Re: I Am Eric Ries, Author of the Lean Startup. AMA
#54Eric--for the above-average engineer (lets call him a 3X-5X), but not a 10X or 100X engineer--what advice would you give if they were interested in beginning a tech venture? How much does personal will play a factor compared to personal ability? Do they stand a chance to compete? Can you think of founders that have achieved great success despite lacking supreme talent? And, finally, to expand a little-- can you think…
There are so many assumptions baked into these questions that it's a little hard to answer. First of all, I'm not a fan of the "10X engineer" framing. I'm much more interested in the systems that companies can build to create 10X teams. I am thinking of two conventional "10X engineers" right now that I've worked with in my career. One is extremely loud, brash, judgmental and basically scary. If you are brave enough t…
Re: I Am Eric Ries, Author of the Lean Startup. AMA
#55I'm a huge fan, Eric! Thank you for doing this. My question is of a more personal nature. When you were in your mid-20s, what were your career goals? Have they changed (if so, how drastically)?
Drastically is an understatement! I was 25 when I co-founded IMVU. My goals at that time were to become an excellent technical founder, CTO, and maybe even a startup CEO someday. Looking back, I think if YC had existed, I almost certainly would have applied. But nothing like that existed back then and so I wound up making my own mistakes and then writing about them.
I've always thought that it's not entirely good idea to not make your own mistakes. While painful it provides a better gut than simply being told or reading about things and getting quick answers.
You know in traditional businesses there is a reason that even in many cases family members (in family businesses) spend time at the bottom before they are put into higher level positions. It gives you a chance to see exactly why and how things are done and to experience them and fully understand nuance. Things that can't be learned in school or passed by anecdote.
Re: I Am Eric Ries, Author of the Lean Startup. AMA
#56Re: I Am Eric Ries, Author of the Lean Startup. AMA
#57Re: I Am Eric Ries, Author of the Lean Startup. AMA
#58Re: I Am Eric Ries, Author of the Lean Startup. AMA
#59Re: I Am Eric Ries, Author of the Lean Startup. AMA
#601) How can you quickly validate a business with very little immediately visible value to the user? Direct user interviews won't work here because the service is very data-driven (collecting filesystem events), so it'll require a decent amount of data collection from the user (I'll offer something like a 14-30 day trial to allow this). Since it has to be done over a longer period of time, and it includes collecting information that might be sensitive to some people, it's not very easy to fully validate the business. I've had a few friends using it, and I'll be sharing with a small beta user list soon, but otherwise I was wondering if you had any other ideas.
2) I've put off writing the payment processing code, focusing on the product itself. Especially considering the "trial" period necessary to see value, are there any downsides to releasing the MVP without allowing payments and then adding them in after release? (Other than no cashflow of course...)
Thanks! I'm actually reading through the lean startup now (after reading way too much of it's principles on the internet first). So it's neat to be able to communicate with the author directly like this.