Startup Lessons Learned

FEBRUARY 9, 2009

Lessons Learned by Eric Ries Monday, February 9, 2009 The lean startup @ Web 2.0 Expo to explain the lean startup concept to a larger audience. The Lean Startup: a Disciplined Approach to Imagining, Designing, and Building New Products.: It uses principles of agile software development, open source and web 2.0,

Lean 68

Lean San Francisco Web Advisory Board 68

Steve Blank

NOVEMBER 21, 2016

Hacking for Diplomacy takes the Lean Startup methodology and applies it to problems sourced from the State Department. The students “get out of the building” and test their hypotheses in front of potential beneficiaries using the Customer Development methodology, all while building and updating their Minimal Viable Products.

Silicon Valley 120

Silicon Valley Washington United Kingdom Lean 120

Steve Blank

NOVEMBER 21, 2016

Hacking for Diplomacy takes the Lean Startup methodology and applies it to problems sourced from the State Department. The students “get out of the building” and test their hypotheses in front of potential beneficiaries using the Customer Development methodology, all while building and updating their Minimal Viable Products.

Silicon Valley 120

Silicon Valley Washington United Kingdom Lean 120

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. Second, what is the cost of these queues?

Product Development 153

Product Development Developer San Francisco Product 153

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.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

NOVEMBER 7, 2008

We had endless arguments internally about what features it should include, how the avatars should look, and how much it should cost. Finally the day came, we unleashed the landing page, emailed our existing customers, and started advertising online. Just load them all in and choose a low cost-per-click. I used to use $.05,

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

MARCH 25, 2010

for Harvard Business Review) Over at Harvard Business Review, Ive been building up a series designed to introduce the Lean Startup methodology to a business-focused audience. This is the first post that moves into making specific process recommendations for product development. Labels: product development Speed up or slow down?

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

APRIL 18, 2010

Lessons Learned by Eric Ries Sunday, April 18, 2010 Four myths about the Lean Startup Myth: Lean means cheap. Lean startups try to spend as little money as possible. Truth: The Lean Startup method is not about cost, it is about speed. Myth: The Lean Startup methodology is only for Web 2.0/internet/consumer

Lean 167

Lean San Francisco Continuous Deployment Startup 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. In my mind, theyre racking up costs (one month for that part, two months for that other part, uh oh). Massive proprietary databases?

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

SEPTEMBER 2, 2008

We wanted an agile approach that would allow us to build our software architecture as we needed it, without downtime, but also without large amounts of up-front cost. After all, the worst kind of waste in software development is code to support a use case that never materializes. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

MARCH 27, 2009

While some cost-cutting measures reduce that number, others increase it. In lean times, it’s most important to focus on cutting costs in ways that speed you up, not slow you down. Otherwise, cutting costs just leads to going out of business a little slower. A crisis is sometimes needed to force that reexamination.

San Francisco 117

San Francisco Lean Continuous Deployment DC 117

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

AUGUST 2, 2008

It costs not just the time of the actual meeting, but the time getting there and back, and the time preparing for it beforehand and thinking about it afterward. 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. .

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

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. Who will ultimately bear the cost of their mistakes? How severely is failure punished?

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

OCTOBER 5, 2010

Lessons Learned by Eric Ries Tuesday, October 5, 2010 The Lean Startup Bundle People often ask me if they can buy "Lean Startup in a box" from me. Its a strange thing, to be asked by a potential customer if they can give you copious amounts of money, and then to have to refuse. And theres so much more. Phew, Im exhausted.

Lean 153

Lean San Francisco Startup Continuous Deployment 153

Startup Lessons Learned

SEPTEMBER 13, 2008

Since we were only paying per click, it didnt cost us anything to cast a wide net. And then we would use that simple analytics system I mentioned to monitor the conversion rates of customers from each campaign. Only much later did I realize that this was an application of customer development to online marketing.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

MARCH 22, 2010

The cost of creating new companies is falling rapidly, and access to markets, distribution, and information is within the reach of anyone with an Internet connection. The cost will be felt in jobs -- thousands of new jobs that could have been created here, but werent. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 121

San Francisco Indiana Lean Startup 121

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.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

FEBRUARY 28, 2009

Lessons Learned by Eric Ries Saturday, February 28, 2009 Throwing away working code Lean startups work by systematically eradicating waste. This builds on a lot of great thinking that has come before, like the agile movements insistence that only the creation of working code counts as progress for a software development team.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

OCTOBER 5, 2009

Or, if it really was prevented, what was the opportunity cost of choosing to prevent it ahead of time? And in most situations, there is significant cost involved in negotiating over the right estimates to plug in. One way to evaluate this fear is to spend time on analysis: how many customers will be affected?

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 133

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? Small is beautiful.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

NOVEMBER 13, 2008

This approach is a the heart of breaking down the "time/quality/cost pick two" paradox , because these small investments cause the team to go faster over time. Great related post by John Shook at the Lean Enterprise Institute about technical vs. social sides of problems. The Lean Startup Intensive is tomorrow at Web 2.0.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

OCTOBER 6, 2008

Lessons Learned by Eric Ries Monday, October 6, 2008 When NOT to listen to your users; when NOT to rely on split-tests There are three legs to the lean startup concept: agile product development , low-cost (fast to market) platforms , and rapid-iteration customer development. Thats what business is designed to do.

San Francisco 128

San Francisco Lean Continuous Deployment Agile 128

Startup Lessons Learned

JULY 29, 2009

Like a financial debt, the technical debt incurs interest payments, which come in the form of the extra effort that we have to do in future development because of the quick and dirty design choice. Although it costs to pay down the principal, we gain by reduced interest payments in the future.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

FEBRUARY 10, 2009

Ship more infrequently While this may decrease downtime (things break and you roll back), the cost on development time from work and rework will be large, and mistakes will continue to slip through. Labels: agile , continuous deployment , lean startup , product development , Test-driven development 4comments: Nivi said.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

SEPTEMBER 5, 2008

[link] And - of course - going through [link] and reading up on the various different approaches different companies have (successfully) taken towards getting scalability at reasonably low cost. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? So, for reference, I am Adam, of [link].

Open Source 107

Open Source San Francisco Continuous Deployment Lean 107

Startup Lessons Learned

APRIL 9, 2009

Thats the essence of so many of the lean startup techniques Ive evangelized: customer development , the Ideas/Code/Data feedback loop , and the adaptation of agile development to the startup experience. The lean startup focuses on situations where we have both an unknown problem and an unknown solution.

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

Startup Lessons Learned

DECEMBER 8, 2008

Integration risk is the term I use to describe the costs of having code sitting on some, but not all, developers machines. I was told that this project had been in development for a couple of years and was currently integrating, and had been integrating for several months. The Lean Startup Intensive is tomorrow at Web 2.0.

Software Review 136

Software Review San Francisco Lean Continuous Deployment 136

Startup Lessons Learned

JUNE 17, 2010

And lastly, it removes the engineering team’s ability to find breakthrough solutions that might deliver most of the value at a fraction of the cost. And lastly, it removes the engineering team’s ability to find breakthrough solutions that might deliver most of the value at a fraction of the cost. Expo SF (May. .

Technical Review 164

Technical Review San Francisco Lean Software Review 164

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

Startup Lessons Learned

APRIL 14, 2009

Over time, they have found a formula for acquiring, qualifying, and selling customers in the market segments they have targeted. They know how much it costs to bring in a customer and they know how much money they can expect to make on each one. Our cost to acquire a customer on AdWords was only a few cents.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

JANUARY 2, 2010

Lessons Learned by Eric Ries Saturday, January 2, 2010 Towards a new entrepreneurship When I started writing about the lean startup , my aspiration was to do more than just share a handful of tips and tricks that work for consumer internet startups. This belief led me to the lean startup, and to an amazing 2009.

San Francisco 122

San Francisco Lean Continuous Deployment DC 122

Startup Lessons Learned

MARCH 29, 2010

Traveling the past year, I have heard loud and clear that its time for the Lean Startup movement to enter its next phase. My aspiration with the Lean Startup methodology has always been to provide such a framework, so that we have more intelligent conversations about what works and what doesnt for startups.

San Francisco 120

San Francisco Lean Continuous Deployment DC 120

Startup Lessons Learned

MAY 7, 2009

May 25, 2009 4:31 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.

San Francisco 131

San Francisco Continuous Deployment Software Review Lean 131

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

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. Thats why we need continuous integration and test-driven development. Any advise on how the decision to rewrite may change for lean startups?

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

SEPTEMBER 8, 2008

It cost us a few hundred thousand dollars to get our app up and running, but none of that was dollars spent on software licenses or professional services. We just had our app support a few tens of thousands of customers, and it did well. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68