Remove Customer Development Remove Developer Remove Product Development Remove Stealth
article thumbnail

Lessons Learned: Achieving a failure

Startup Lessons Learned

Build the product in stealth mode to build buzz for the eventual launch. But that was two full years before any customers were allowed to use it. It was considered naive that the "next AOL" would ship a product that wasnt ready for prime time. Stealth is a customer-free zone. We can skip the chasm.

article thumbnail

The Entrepreneur’s Guide To 4 Categories Of Business Meetings

YoungUpstarts

by Dori Sella, author of “ Business Meetings that Work: 6 Steps to Increase Productivity “ Starting a business, whether it’s based on technology, a new marketing concept or a product is always exciting. This is of course assuming you are prepared to go out of ‘stealth mode’ – don’t laugh.

Stealth 198
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Lean Startup fbFund wrap-up

Startup Lessons Learned

bigs : @ericries says Stealth dev is a (undesirable, failure-presaging) customer-free zone. LeanStartup Of course, a big enabler of those kinds of mistakes is stealth-mode. Another recent meme that I hope more and more startups will take to heart: "stealth is a customer-free zone." Danger, Will Robinson.

Lean 60
article thumbnail

Lessons Learned: Using AdWords to assess demand for your new.

Startup Lessons Learned

Turns out, there was aboslutely no demand whatsoever for that particular product. Oops - there went several precious weeks of development effort down the drain. If you cant find any , maybe that means you havent figured out who your customer is yet. What is customer development? What a great post.

Demand 167
article thumbnail

How to conduct a Five Whys root cause analysis

Startup Lessons Learned

It allows teams to diagnose sources of waste in their development process and continuously improve, reversing the usual trend of teams getting slower over time. These problems can be anything: development mistakes, site outages, marketing program failures, or even internal missed schedules. My experience is: usually not.