Startup Lessons Learned
MARCH 25, 2010
Defective prototype code was as often thrown out (because customers didnt want it) as it was fixed (when customers did). Hence, cutting corners often paid huge dividends. Two Ways to Hold Entrepreneurs Accountable Beware of Vanity Metrics For Startups, How Much Process Is Too Much?
Startup Lessons Learned
SEPTEMBER 15, 2008
Thats when this approach can pay huge dividends. Focus on the output metrics of that part of the product, and you make the problem a lot more clear. I had the opportunity to pioneer this approach to funnel analysis at IMVU, where it became a core part of our customer development process. Thanks for writing this article.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Steve Blank
JANUARY 21, 2013
I think you will see the work of some talented and determined entrepreneurs who have honed their customer discovery and customer development skills to an impressive level. Align and train mentors to embrace customer development. If you do, my bet is on these talented, motivated and well-prepared undergraduates.
Startup Lessons Learned
FEBRUARY 20, 2009
These changes pay increasing dividends, because each improvement now direclty frees up somebody in QA at the same time as reducing the total time of the certification step. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R.
Startup Lessons Learned
OCTOBER 19, 2009
The key ideas are customer development , the pivot , MVP, and root cause analysis. Being systematic about these hypotheses is what customer development is all about. This is the ultimate startup discipline, the hardest to master, and the one that pays biggest dividends. Why didn’t we learn more?
Startup Lessons Learned
JULY 2, 2009
Luckily, in most prevention situations, even the first few steps in prevention can pay time-savings dividends quickly. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R. Startup Lessons Learned - the Conference (April 23.
Startup Lessons Learned
JANUARY 28, 2009
If thats not a team-wide phenomenon, then its still a form of waste, because everyone has to learn every lesson before it starts paying dividends. I would also suggest, and the engineers will almost certainly hate this suggestion, that the decision-maker asks for hard metrics to justify the refactoring effort in the first place.
Expert insights. Personalized for you.
141 
Let's personalize your content