Startup Lessons Learned

SEPTEMBER 15, 2008

Lessons Learned by Eric Ries Monday, September 8, 2008 The lean startup Ive been thinking for some time about a term that could encapsulate trends that are changing the startup landscape. After some trial and error, Ive settled on the Lean Startup. I like the term because of two connotations: Lean in the sense of low-burn.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Steve Blank

MARCH 11, 2015

They’ve found product/market fit (what products customers want to buy). They’ve learned the best distribution channel to get the product from their company to the customer. and how to price the product. for new product development that emphasize immediate returns.

Widget 120

Widget Lean Business Model Metrics 120

www.vccafe.com

MARCH 11, 2013

Lean Methodology Sources. Steve Blank on Lean Customer Development. Part 3- Lean Cust. IP Location Tools. Steve Blank’s Lean Startup Resources. Lean Startup Circle â?? free, distributed source code control management system. Great for visualizing work of product development.

Software Review 53

Software Review Technical Review Startup 53

Steve Blank

DECEMBER 8, 2015

Startups are developing IP relevant to the disruption. For example, Google’s acquisition of Nest (which had customers, revenue and a distribution channel) allowed it to enter the connected home market immediately. (We’ll cover “ corporate moonshots ” in a subsequent post.).

Silicon Valley 120

Silicon Valley Acquisition Boston Early Stage 120

Startup Lessons Learned

SEPTEMBER 11, 2009

In fact, users asked that IMVU make a determination as to who was deliberately passing Unfit for IMVU products into the catalog and stop them from performing peer review on either their main accounts or their alts. Users also asked that IMVU identify and aggressively act to eliminate the source of such products up to and including IP bans.

Community 158

Community Management Lean Software Review 158

maplebutter.com

JANUARY 8, 2013

How to stay lean and iterate quickly while you’re building a two sided marketplace, especially when “network effect” and “critical mass” are the two main focuses? Near shoring development with your team (ex: your team is based in Canada / India) is cool, but not outsourcing. I think 6-8 is a good number.

Technical Review 44

Technical Review Startup Cofounder Software Review 44