Startup Lessons Learned

JULY 5, 2010

I believe it is the best introduction to Customer Development you can buy. As all of you know, Steve Blank is the progenitor of Customer Development and author of The Four Steps to the Epiphany. You can imagine how well that worked. On the minus side, that has made it a wee bit hard to understand.

Customer Development 166

Customer Development Developer San Francisco Customer 166

Startup Lessons Learned

SEPTEMBER 7, 2008

Lessons Learned by Eric Ries Sunday, September 7, 2008 Customer Development Engineering Yesterday, I had the opportunity to guest lecture again in Steve Blank s entrepreneurship class at the Berkeley-Columbia executive MBA program. Its a nice complement on the product engineering side to his customer development methodology.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

DECEMBER 16, 2009

Lessons Learned by Eric Ries Wednesday, December 16, 2009 What is Lean about the Lean Startup? The first step in a lean transformation is learning to tell the difference between value-added activities and waste. I was giving my first-ever webcast on the lean startup. This value is evident in Lean Startups.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

Startup Lessons Learned

MARCH 16, 2009

Lessons Learned by Eric Ries Monday, March 16, 2009 Combining agile development with customer development Today I read an excellent blog post that I just had to share. In most agile development systems, there is a notion of the "product backlog" a prioritized list of what software is most valuable to be developed next.

Agile 111

Agile Customer Development Developer San Francisco 111

VC Cafe

MARCH 22, 2011

The CEO then needs to assess those opportunities, validating them through market research and customer development and if ultimately, one of those new opportunities proves to be larger than or incremental to the existing business opportunity, they need to clearly articulate that change of direction to the team and execute the transition rapidly.

Business Model 84

Business Model API Wiki Seed Stage 84

Startup Lessons Learned

JULY 2, 2009

Lessons Learned by Eric Ries Thursday, July 2, 2009 How to conduct a Five Whys root cause analysis In the lean startup workshops , we’ve spent a lot of time discussing the technique of Five Whys. My intention is to describe a full working process, similar to what I’ve seen at IMVU and other lean startups. Expo SF (May. .

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

JULY 29, 2009

I hope to show why lean and agile techniques actually reduce the negative impacts of technical debt and increase our ability to take advantage of its positive effects. Lean vs. debt In the world of physical goods, the leaner a supply chain is, the less debt is required to operate it. A similar relationship applies to technical debt.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

JANUARY 12, 2010

Lessons Learned by Eric Ries Tuesday, January 12, 2010 Amazing lean startup resources A year ago, there was no lean startup movement. I continue to believe that the explosion of interest in the lean startup has very little to do with me. If you are attempting to apply lean startup ideas in your own business - you are not alone.

Lean 146

Lean San Francisco Wiki Startup 146

Startup Lessons Learned

SEPTEMBER 15, 2008

Lessons Learned by Eric Ries Monday, September 15, 2008 The one line split-test, or how to A/B all the time Split-testing is a core lean startup discipline, and its one of those rare topics that comes up just as often in a technical context as in a business-oriented one when Im talking to startups. Check your assumptions, what went wrong?

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

AUGUST 1, 2009

One of the most common questions I get about the lean startup methodology is, "but what about Steve Jobs ?" When I try to unpack what people mean by the question, heres my best take on what they are asking: "Look, Steve Jobs doesnt go out and ask customers what they want. He tells customers what they want, and he gets it right.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

JUNE 15, 2009

Of all the tactics I have advocated as part of the lean startup , none has provoked as many extreme reactions as continuous deployment , a process that allows companies to release software in minutes instead of days, weeks, or months. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

FEBRUARY 22, 2010

I already advocate cross-functional teams as part of the lean startup methodology. Last year, I traveled to dozens of cities talking about lean startups and meeting people interested in entrepreneurship. I already advocate cross-functional teams as part of the lean startup methodology. None of these are impossible.

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

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

Startup Lessons Learned

OCTOBER 20, 2008

I now believe that the "pick two" concept is fundamentally flawed, and that lean startups can achieve all three simultaneously: quickly bring high-quality software to market at low cost. Any advise on how the decision to rewrite may change for lean startups? The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May. .

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

SEPTEMBER 27, 2010

Lean manufacturing , agile software development , and Theory of Constraints are all examples of this idea in action. I won’t apologize for this aspect of the Lean Startup methodology. Lean manufacturing , agile software development , and Theory of Constraints are all examples of this idea in action.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

JANUARY 19, 2009

Lessons Learned by Eric Ries Monday, January 19, 2009 Lean hiring tips In preparing for the strategy series panel this week, I have been doing some thinking about costs. Fundamentally, lean startups do more with less, because they systematically find and eliminate waste that slows down value creation. Another terrific post, Eric.

Lean 140

Lean Hiring San Francisco Continuous Deployment 140

Startup Lessons Learned

JANUARY 18, 2010

Recently, he was bitten by the lean startup bug and has started writing about his experiences attempting to apply lean startup and customer development principles. Ive previously named his post Achieving Flow in a Lean Startup as one of my favorite blog posts of 2009. Things started to slip.

Continuous Deployment 151

Continuous Deployment San Francisco Lean Wiki 151

Startup Lessons Learned

JUNE 17, 2010

Lets start holding people accountable solely for their contribution to the only thing that matters: validated learning about customers. The Entrepreneur’s Guide to Customer Development ▼ June (3) What is a startup? The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May. . Expo SF (May.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

NOVEMBER 13, 2008

Great related post by John Shook at the Lean Enterprise Institute about technical vs. social sides of problems. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? The Lean Startup Intensive is tomorrow at Web 2.0. June 15, 2009 9:27 PM Mark Graban said. Expo SF (May. .

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Aymeric Gaurat-Apelli

JULY 1, 2010

You will find here a list of tools you can use during the customer discovery phase. You can find more tool ideas on the Startup Tools Wiki. What tools do you use to better understand your customers? when you are not outside the building interviewing them) Other articles you might like Lean startups, beware the social debt! (3)

Lean 38

Lean Customer Ruby Startup 38

Startup Lessons Learned

NOVEMBER 7, 2008

If you cant find any , maybe that means you havent figured out who your customer is yet. And if you dont know who your customer is, perhaps some customer development is in order? Labels: customer development , search engine marketing 13comments: Jim Lindstrom said. Eric -- This is a pretty interesting idea.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

SEPTEMBER 30, 2008

Platform selection and technical design - if your business strategy is to create a low-burn, highly iterative lean startup, youd better be using foundational tools that make that easy rather than hard. But I think in a lean startup, the development methodology is too important to be considered "just management." I dont think so.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

JULY 28, 2010

kaChing has been very active in the Lean Startup movement. With case studies like this, we aim to illustrate specific Lean Startup techniques through the stories of current practitioners. kaChing has been very active in the Lean Startup movement. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May. .

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

Startup Lessons Learned

JULY 13, 2009

Lessons Learned by Eric Ries Monday, July 13, 2009 The Principles of Product Development Flow If youve ever wondered why agile or lean development techniques work, The Principles of Product Development Flow: Second Generation Lean Product Development by Donald G. Reinertsen is the book for you.

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

NOVEMBER 29, 2008

December 14, 2008 8:09 PM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) What is customer development?

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

FEBRUARY 20, 2009

I owe it originally to lean manufacturing books like Lean Thinking and Toyota Production System. The batch size is the unit at which work-products move between stages in a development process. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Expo SF (May. . Expo SF (May.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

AUGUST 3, 2009

Lessons Learned by Eric Ries Monday, August 3, 2009 Minimum Viable Product: a guide One of the most important lean startup techniques is called the minimum viable product. I was delighted to be asked to give a brief talk about the MVP at the inaugural meetup of the lean startup circle here in San Francisco. Thanks Eric. Expo SF (May.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

APRIL 7, 2010

Lessons Learned by Eric Ries Wednesday, April 7, 2010 Learning is better than optimization (the local maximum problem) Lean startups don’t optimize. Instead, we try to accelerate with respect to validated learning about customers. and for which customer? That’s the local maximum. That’s right.

San Francisco 154

San Francisco Lean Metrics Design 154

Startup Lessons Learned

SEPTEMBER 10, 2008

Plus, as product development teams in lean startups become adept at learning-and-discovery (as opposed to just executing to spec), its clear that some bugs shouldnt be fixed. We always have to avoid that dysfunction - even the lean manufacturing greats realized that they couldnt afford to see their manual-labor workforce that way.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Aymeric Gaurat-Apelli

JULY 1, 2010

You will find here a list of tools you can use during the customer discovery phase. You can find more tool ideas on the Startup Tools Wiki. What tools do you use to better understand your customers? when you are not outside the building interviewing them) Other articles you might like Lean startups, beware the social debt! (3)

Lean 32

Lean Customer Ruby Startup 32

Startup Lessons Learned

OCTOBER 5, 2008

Ive written about it on our development blog at [link] October 6, 2008 3:34 PM Chris Hondl said. Great to read posts about introducing lean approaches into more teams. Im currently introducing lean to my new team. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

OCTOBER 4, 2008

Maybe youd like to start with The lean startup , How to listen to customers , or What does a startup CTO actually do? ) Eventually, I came to summarize these themes with the phrase " the lean startup." Lean is one of the major trends shaping our world, and its impact goes beyond just optimizing our supply chains.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

NOVEMBER 4, 2008

Lessons Learned by Eric Ries Tuesday, November 4, 2008 Principles of Lean Startups, presentation for Maples Investments Image via Wikipedia Steve Blank and I had the opportunity to create a presentation about lean startups for Maples Investments. Customer development. you get the idea. you get the idea.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

OCTOBER 5, 2009

blog comments powered by Disqus Newer Post Older Post Home Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May.

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 133

Startup Lessons Learned

DECEMBER 14, 2009

Each of these four currencies represents a way for a customer to “pay&# for services from a company. A great product enables customers, developers, partners, and even competitors to exchange their unique currencies in combinations that lead to financial success for the company that organizes them.

Customer 156

Customer San Francisco Viral Lean 156

Startup Lessons Learned

APRIL 14, 2009

(For more on how this plays into the process of scaling up, see the Customer Creation stage of the customer development model.) But in the meantime, by iterating on their product with customers, they have a chance to get there on their own. Labels: agile , customer development 15comments: Scott Shapiro said.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

MARCH 3, 2009

March 17, 2009 7:48 AM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Expo SF (May. . Expo SF (May.

Employee 146

Employee San Francisco Lean Software Review 146