From The Ground Up

Fwd: Engineering, startups and life

How To Overcome A Lack Of Understanding

with 4 comments

Startups are primarily competing against indifference, lack of awareness, and lack of understanding — not other startups.

Chris Dixon’s post, and specifically his quote above, on competition, speak to the importance of customer development. Jack Welch illuminates for us the extent to which one must understand the customer, in his book Winning. And I paraphrase, “Be granular, know what each of your customers eats for breakfast”. These thoughts reflect the pivotal role customer input plays, no matter the size of your company.

Startups are unique though, they continuously face a lack of resources (time, knowledge, the right manpower, the right money, among others).  For this reason learning and development must be achieved early on and iteratively. Most in the startup world are aware of the philosophy around customer development. There are many a blog post, and two books in particular, elucidating the philosophy of customer development pertaining to the “lean startup”.

The concepts explained in these books are extremely helpful in overcoming “lack of awareness and lack of understanding”. The entrepreneur (that’s you!) must dig in and understand the problem the customer is aiming to solve. Equally important is that you understand whether this problem is one customers are willing to pay you to solve.

Books and words are nice, but Morpheus would agree “there’s a difference between knowing the path and walking the path”. A couple weekends ago, I, and 50 others, got to do just that at the first ever Lean Startup Machine weekend. 54 hours worth of customer development, hell-bent on delivering a kick-ass Minimum Viable Product. A few words come to mind after this exhilirating experience. Addiction might be one of them. Eye-opening lessons were everywhere, here are a few nuggets:

  1. “Getting out of the building” is easier said than done. Push yourself out the door. It takes effort and practice.
  2. Know the difference between testing your hypothesis and seeking evidence: before leaving the building be open and be ready to have your product assumptions crushed and invalidated
  3. Do not ask questions in a way that projects your product on to the customer’s problem
  4. Listen, listen, listen and learn
  5. Listen, listen, listen and know what to filter out: the customer is important but their words are not gospel
  6. An MVP can be as simple as a sign-up page
  7. Getting people to put money down makes them customers: the ultimate customer validation

In retrospect, our team should have done more customer development: more calls, more face-to-face time with potential customers. It really is like most other things, it takes doing and practice. Experience is invaluable. Ideally, after pivoting and iterating, you will get to a place where you have a better vision of the customer and their needs. You’ll be closer to the problem and all its intricacies, and would have gained a ton of understanding. On top of this, during this process, you probably would have learned a lot about any competition, and you’ll be in a better position to face these external challenges.

A solid weekend overall, thanks to these guys for organizing the first ever LSM. And much appreciation to Brant Cooper, Josh Knowles, Giff Constable, and Eric Reis for their time and insights.


Written by Girish Rao

August 4, 2010 at 12:54

Posted in Uncategorized

4 Responses

Subscribe to comments with RSS.

  1. Some great stuff in this post Girish, but I’m puzzled by the title!


    August 5, 2010 at 12:16

    • Thanks Giff. The title is likely a result of late night blogging — I was trying to convey the idea that by using the custdev approach startups don’t have to compete against lack of understanding (Chris’ opening quote), and can instead focus on competing against other more external variables.

      Maybe something like “How to overcome your lack of understanding” might work better.

      Girish Rao

      August 5, 2010 at 16:13

  2. Great post Girish. My two favorite points are #2 & #7. In addition to #2 I would say there’s also a difference between testing a hypothesis & doing a cust dev interview vs doing an interview – it’s important before anything to have assumption written down and a way to test those, specific objectives you plan to learn.

    Trevor Owens

    August 6, 2010 at 12:46

  3. Girish this is an excellent article and it sounds like it was a great learning experience. Hearing what a customer wants is an art-most don’t have the tools to tell you. It’s all about the questions you ask and how you ask them.

    Dave Freireich

    November 15, 2010 at 17:46

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: