Startup Lessons Learned

NOVEMBER 13, 2008

By continuously adjusting, we eventually build up a robust series of defenses that prevent problems from happening. 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. Id like to point out something else about the example above.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

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. Just load them all in and choose a low cost-per-click. Seems like a fairly low-cost method of gauging customer interest for a would-be product. The Lean Startup Intensive is tomorrow at Web 2.0.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

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. My path to lean startups began with Kent Beck and extreme programming.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

MAY 7, 2009

I spent some time with his company before the conference and discussed ways to get started with continuous deployment , including my experience introducing it at IMVU. Moreover, approaching the problem from the direction that I had intuitively is a recipe for never reaching a point where continuous deployment is feasible.

San Francisco 131

San Francisco Continuous Deployment Software Review Lean 131

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 10, 2008

But if you want to practice rapid deployment, you need to be able to deploy that build in one step as well. If you want to do continuous deployment, youd better be able to certify that build too, which brings us to. For more on continuous deployment, see Just-in-time Scalability. Can you make a build in one step?

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

SEPTEMBER 7, 2008

One major theory that has influenced the way I think about processes comes from Lean Manufacturing , where they use these same techniques to build cars. It seems many startups these days are under a lot of pressure to outsource their development organization to save costs. The Lean Startup Intensive is tomorrow at Web 2.0.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

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

JULY 29, 2009

We can choose to continue paying the interest, or we can pay down the principal by refactoring the quick and dirty design into the better design. Although it costs to pay down the principal, we gain by reduced interest payments in the future. The human tendency to moralize about debt affects engineers, too.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

NOVEMBER 14, 2013

Guest post by Lisa Regan, writer for T he Lean Startup Conference. We’ve posted the full program for The Lean Startup Conference , and it includes more than three days of events for Gold pass holders and six days of events for VIP pass holders. On the evening of December 8, Ignite Lean Startup kicks off the conference.

Continuous Deployment 162

Continuous Deployment Norway Lean Analytics 162

Startup Lessons Learned

MAY 9, 2012

TLDR: Brant Cooper and Patrick Vlaskovits , authors of The Entrepreneur's Guide to Customer Development are back with a new book called The Lean Entrepreneur. Since then, Brant and Patrick have been tireless advocates for the whole Lean Startup movement. Illustrations by FAKEGRIMLOCK. You can pre-order it starting today.

Entrepreneur 167

Entrepreneur Lean Southern California San Diego 167

Startup Lessons Learned

NOVEMBER 8, 2008

This theory has become so influential that I have called it one of the three pillars of the lean startup - every bit as important as the changes in technology or the advent of agile development. The Lean Startup Intensive is tomorrow at Web 2.0. Case Study: Continuous deployment makes releases n. Expo SF (May.

Customer Development 168

Customer Development Developer San Francisco Customer 168

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

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. The Lean Startup Intensive is tomorrow at Web 2.0. Lessons Learned by Eric Ries Thursday, March 25, 2010 Speed up or slow down? Are we going too fast?

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

SEPTEMBER 13, 2008

Since we were only paying per click, it didnt cost us anything to cast a wide net. The Lean Startup Intensive is tomorrow at Web 2.0. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Expo SF (May.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

DECEMBER 8, 2008

In this post I want to talk about the nuts and bolts of how to integrate continuous integration into your team, and how to use it to create two important feedback loops. First, a word about why continuous integration is so important. As with many lean startup practices, its getting started thats the hard part. Expo SF (May.

Software Review 136

Software Review San Francisco Lean Continuous Deployment 136

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. Labels: agile , continuous deployment 1 comments: timothyfitz said. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

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.: Hey Someone else who is extending the agile/lean approach beyond just developing software.

Lean 68

Lean San Francisco Web Advisory Board 68

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. But lean startups cant afford to be satisfied with just that definition, because there are situations where working code is itself a form of waste. Expo SF (May. for Harvard Business Revie.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

OCTOBER 11, 2010

(I am often asked to explain how to apply Lean Startup approaches to domains beyond software. The key to understanding Lean Startup is to recognize two things: Lean Startup techniques confer maximum benefit in the upper-right quadrant, namely high market uncertainty coupled with fast cycle time.

Continuous Deployment 164

Continuous Deployment Technical Cofounder Cofounder San Francisco 164

Startup Lessons Learned

JULY 3, 2009

Lessons Learned by Eric Ries Friday, July 3, 2009 Lean Startup fbFund wrap-up Last week I had a real blast meeting with the companies at the fbFund incubator at Palo Alto. The Lean Startup fbFund Edition View more documents from Eric Ries. The Lean Startup Intensive is tomorrow at Web 2.0. Without further ado. Expo SF (May.

Lean 60

Lean San Francisco Continuous Deployment Cofounder 60

Startup Lessons Learned

APRIL 14, 2009

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. The Lean Startup Intensive is tomorrow at Web 2.0. Case Study: Continuous deployment makes releases n. Expo SF (May.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

MAY 27, 2009

Lessons Learned by Eric Ries Wednesday, May 27, 2009 Austin: the Lean Startup tour continues Next week I head to Austin, TX for my first visit ever. The Lean Startup is a practical approach for creating and managing a new breed of company that excels in low-cost experimentation, rapid iteration, and true customer insight.

Lean 60

Lean Austin San Francisco Startup 60

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. The Lean Startup at Web 2.0

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

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

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 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

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. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 128

San Francisco Lean Continuous Deployment Agile 128

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

DECEMBER 14, 2009

A business that strives for something like this should absolutely be charging money from day one, in order to establish baselines for their two key metrics: CPA (the cost to acquire a new customer) and LTV (the lifetime value of each acquired customer). These concepts have important implications for any lean startup. Expo SF (May.

Customer 156

Customer San Francisco Viral Lean 156

Startup Lessons Learned

AUGUST 24, 2009

As the costs of production fall, it’s getting easier and easier to send in a proposal or even a complete work. Just like in the world of startups, we can start to use micro-scale pilot programs, executed in lean fashion, to gather real facts for making ROI decisions about new project investment. 12comments: Dougvs said.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

JANUARY 4, 2009

This has two major drawbacks: the central directory can become a single point of failure, and there is a performance cost for having to consult the directory ever time you want to access data anywhere in the cluster. The Lean Startup Intensive is tomorrow at Web 2.0. Case Study: Continuous deployment makes releases n.

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

DECEMBER 7, 2008

When I get involved in companies that struggle with this problem, here is the kind of advice I think can help: Introduce TDD and continuous integration. This is one of the bedrock practices of any lean startup , and so its a common piece of advice I give out. The Lean Startup Intensive is tomorrow at Web 2.0. Not necessarily.

Software Review 94

Software Review Technical Review San Francisco Part-Time VPE 94

Startup Lessons Learned

FEBRUARY 11, 2009

Its obvious that can lower your development costs, but I think its even more important that it can reduce your time to market. The Lean Startup Intensive is tomorrow at Web 2.0. Case Study: Continuous deployment makes releases n. Amazing lean startup resources Is Entrepreneurship a Management Science? Expo SF (May.

Software Review 68

Software Review Software Hiring San Francisco 68

Startup Lessons Learned

JUNE 5, 2009

If it costs $0.10 to acquire an early adopter, how much should it cost to acquire a mainstream customer? This model of joint accountability is at the heart of the lean startup, and is just as applicable to venture-backed, bootstrapped, and enterprise startups. The Lean Startup Intensive is tomorrow at Web 2.0. But $10.00?

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Startup Lessons Learned

APRIL 26, 2009

Its a key lean startup concept. Plus, we saw some of the intrinsic limitations of supporting such a large staff: slower cycle times, higher cost basis, and - most importantly - the ability to serve only a limited number of customer segments. We didnt think wed able to compete with that.

Product Development 88

Product Development Developer San Francisco Product 88

Startup Lessons Learned

SEPTEMBER 8, 2009

Beyond just those who will be hearing about the lean startup for the first time, Im expecting to shake a lot of hands and have a lot of interesting side conversations. The Lean Startup Intensive is tomorrow at Web 2.0. Im especially curious to gauge the reaction of the civilian and military representatives of our government.

DC 90

DC Washington San Francisco SBIR 90