Startup Lessons Learned

OCTOBER 19, 2009

Lessons Learned by Eric Ries Monday, October 19, 2009 Inc Magazine on Minimum Viable Product (and a response) Inc Magazine has a great new piece up about the increasing use of the Minimum Viable Product by businesses (and not just startups). The key ideas are customer development , the pivot , MVP, and root cause analysis.

San Francisco 137

San Francisco Product Lean Continuous Deployment 137

Startup Lessons Learned

JUNE 22, 2009

Lessons Learned by Eric Ries Monday, June 22, 2009 Pivot, dont jump to a new vision In a lean startup , instead of being organized around traditional functional departments, we use a cross-functional problem team and solution team. Each has its own iterative process: customer development and agile development respectively.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Steve Blank

JULY 29, 2013

(However, in some industries such as life sciences, founders may be tenured professors who are not going to give up their faculty positions, so they often become the head of a startup’s scientific advisory board, but aren’t part of the founding team.). Speed, tempo and fearless decision-making are a startups strategic advantage.

Cofounder 335

Cofounder Advisory Board Customer Development Leadership 335

Startup Lessons Learned

OCTOBER 5, 2009

Managing these situations is hard for any company, but potentially lethal for a startup. There are just so many ways for a startup to fail. I’ve lived through the over-architecture failure – where attempting to prevent all kinds of problems wound up delaying the company from putting out any product at all.

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 133

Startup Lessons Learned

OCTOBER 11, 2009

Why was a team this smart, this disciplined, and this committed to waste-free product development creating so much waste? Labels: split-test Innovation inside the box I was recently privy to a product prioritization meeting in a relatively large company. No departments The Five Whys for Startups (for Harvard Business R.

San Francisco 133

San Francisco Lean Metrics Continuous Deployment 133

ReadWriteStart

JUNE 20, 2012

Editor's note : This is the second in a two-part excerpt from the book The Startup Owner’s Manual , a step-by-step how-to guide for entrepreneurs. In this excerpt, authors Steve Blank and Bob Dorf continue to explain the Customer Discovery Philosophy (see Part One, " Is Your Startup a Valid Vision or Just a Hallucination? ").

Customer 119

Customer Advisory Board Engineer Cofounder 119

Startup Lessons Learned

OCTOBER 23, 2009

This is especially useful in situations, like most B2B businesses, where the total number of customers is likely to be small. This case study illustrates one company’s attempt to do customer development by testing their vision with customers before writing a single line of code. Read on and judge for yourself.

San Francisco 144

San Francisco Customer Wiki Lean 144

Startup Lessons Learned

OCTOBER 19, 2009

Heres an excerpt: One of the unfortunate side effects of all the publicity and hype surrounding startups is the idea that entrepreneurship is a guaranteed path to fame and riches. Building a startup is incredibly hard, stressful, chaotic and –- more often than not –- results in failure. But only startups combine all three.

San Francisco 111

San Francisco Lean Continuous Deployment DC 111

steveblank.com

JULY 8, 2011

Useful blogs and links for startups Click Here ————– 2.

Software Review 110

Software Review Startup Silicon Valley Analytics 110

www.vccafe.com

MARCH 11, 2013

Startup Resources (Updated Mar 2013). Venture Capital Cafe > Startup Resources (Updated Mar 2013). VC & Startup Resources. Seed Startups. VC Cafe covers early stage Israeli and European tech & mobile startups. Hundreds of startups featured since 2005, will yours be next? About VC Cafe.

Software Review 53

Software Review Technical Review Startup 53