Remove Customer Remove Customer Development 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. Here are a few: We know what customers want. By hiring experts, conducting lots of focus groups, and executing to a detailed plan, the company became deluded that it knew what customers wanted. Everyone had fun; the product worked.

article thumbnail

The Entrepreneur’s Guide To 4 Categories Of Business Meetings

YoungUpstarts

Once you have gone past the initial stage of developing your idea and clarifying what your business is going to be, you will have many business meetings. This is of course assuming you are prepared to go out of ‘stealth mode’ – don’t laugh. Customer Development.

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." Iterating at whiteboard !=

Lean 60
article thumbnail

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

Startup Lessons Learned

Thats the conclusion Ive come to after watching tons of online products fail for a complete lack of customers. Our goal is to find out whether customers are interested in your product by offering to give (or even sell) it to them, and then failing to deliver on that promise. We finally settled on a $1.99

Demand 167
article thumbnail

How to conduct a Five Whys root cause analysis

Startup Lessons Learned

When customers are affected, try to have someone who experienced the customer problem first-hand, like the customer service rep who took the calls from angry customers. Labels: five whys root cause analysis , product development 15comments: Anonymoussaid. Otherwise, key details are likely to be missed.