Lean Lessons Learned: 17 Tweetable Takeaways

Posted by Grace Ng on

At LSM, we eat our own dog food: we want to learn from our workshop attendees about their experiences, so that we could iterate and make it better with each event. At the end of the January 2012 Lean Startup Machine in Palo Alto, we put the exhausted participants on the spot to answer several questions about their experience. Here are 17 of their answers to the question "What were the top 3 things you learned?" arranged by tweet-ability (length). What's your favorite?
  1. MVP is not necessarily code. - Safeer Mohiuddin [tweet it!]
  2. Fell in love w/Customer development. - Anonymous  [tweet it!]
  3. Interviewing strangers. Dropping an idea. - Anonymous  [tweet it!]
  4. Cust. validation - know what your customers want. Shahed Khan [tweet it!]
  5. MVP ≠ code. Pivot if needed. Prove yourself wrong. - Nathan Ross [tweet it!]
  6. MVP. Pivot or persevere. Validation of assumptions. - Hung Pham [tweet it!]
  7. Customer Validation. How to pivot. Customer interviews. - Abdullah Mashuk [tweet it!]
  8. 1) Try it; don't build it. 2) Validate assumptions. 3) Try it again. - Courtney McColgan [tweet it!]
  9. 1. Test your market ASAP. 2. Write better assumptions. 3. Learn faster. - Yaser Syed [tweet it!]
  10. 1. Quickly document your hypothesis & assumption. 2. Test your assumption. - Raja Doddala [tweet it!]
  11. Speed of validation, hacks for tests, will use them in our product dev strategy. - Jeff Zias
  12. 1. How to approach customers. 2. How to build progressive MVPs. 3. How to derisk ideas. - Bilal Aijazi [tweet it!]
  13. Validate the problem set before solution design. Hustle works! Don't worry about being right. - Anonymous  [tweet it!]
  14. Being more introspective about my biases & avoiding creating experiments that can only confirm my beliefs. - Anonymous  [tweet it!]
  15. Scientific method applies to startups, too. Cust. dev. What MVP really means. (More than my head can assimmilate in a weekend.) - Michael Fuery [tweet it!]
  16. Important to identify and test your assumptions. Conflict between an assertion and simply trying to discover customer need is interesting. - Anonymous  [tweet it!]
  17. Ask potential users what problems they have. Ask why they do things the way they do. Find creative ways to test something before becoming convinced you are right. - Leslie Van Zee [tweet it!]