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. Chris and I had the opportunity to present on our approach this past spring at the MySQL Conference. Labels: agile , continuous deployment 1 comments: timothyfitz said.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

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. Case Study: Continuous deployment makes releases n.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

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. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

FEBRUARY 10, 2009

Lessons Learned by Eric Ries Tuesday, February 10, 2009 Continuous deployment and continuous learning At long last, some of the actual implementers of the advanced systems we built at IMVU for rapid deployment and rapid response are starting to write about it. At IMVU it’s a core part of our culture to ship.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

FEBRUARY 9, 2009

Expo San Francisco 2009 The current macroeconomic climate presents unparalleled opportunities for those that can thrive with constrained resources. 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 68

Lean San Francisco Web Advisory Board 68

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. I want to talk specifics, and when you come right down to it, most technology startups dont have a very interesting cost structure. The blog is fantastic as well.

Lean 140

Lean Hiring San Francisco Continuous Deployment 140

Startup Lessons Learned

MARCH 29, 2010

Heres a tiny sample: "Case studies, case studies, case studies presented by real people. Then, well talk case studies in each area, presented by practicing entrepreneurs who have actually grappled with the topic at hand. And do I still need to get out of the building if Ive got great metrics and surveys?"

San Francisco 120

San Francisco Lean Continuous Deployment DC 120

Startup Lessons Learned

FEBRUARY 16, 2009

Lessons Learned by Eric Ries Monday, February 16, 2009 Continuous deployment with downloads One of my goals in writing posts about topics like continuous deployment is the hope that people will take those ideas and apply them to new situations - and then share what they learn with the rest of us.

Continuous Deployment 68

Continuous Deployment San Francisco Software Review Lean 68

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

JUNE 5, 2009

In a startup context, numbers like gross revenue are actually vanity metrics, not actionable metrics. Luckily, we also discovered that certain other metrics, like LTV and CPA were much better than we initially projected. If it costs $0.10 Case Study: Continuous deployment makes releases n. But $10.00?

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Startup Lessons Learned

SEPTEMBER 30, 2008

If the CEO wants to completely change the product in order to serve a new customer segment, you need someone in the room who can digest the needs of the new (proposed) business, and lay out the costs of each possible approach. In my mind, theyre racking up costs (one month for that part, two months for that other part, uh oh).

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

JULY 3, 2009

davemcclure : amazing concepts on Continuous Development => "Cluster Immune System" @EricRies #LeanStartup @fbFund [link] dalelarson : Because most features take longer to argue and prioritize than to build. ericries #leanstartup Another new idea in the section on continuous deployment and the cluster immune system.

Lean 60

Lean San Francisco Continuous Deployment Cofounder 60

Startup Lessons Learned

MAY 27, 2009

Heres their description of the event: The current macroeconomic climate presents unparalleled opportunities for those that can thrive with constrained resources. 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 Continuous Deployment 60

Startup Lessons Learned

APRIL 14, 2009

Every board meeting, the metrics of success change. 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. Time-to-complete-a-sale is not a bad metric for validated learning at this stage.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

AUGUST 24, 2009

So let’s turn our attention from what may happen in the future to what is definitely happening in the present. As the costs of production fall, it’s getting easier and easier to send in a proposal or even a complete work. I used to be skeptical of all this talk of “personal brand.&# Is that a lot?

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

NOVEMBER 8, 2008

There are three fundamental situations that change what your company needs to do: creating a new market (the original Palm), bringing a new product to an existing market (Handspring), and resegmenting an existing market (niche, like In-n-Out Burger; or low-cost, like Southwest Airlines). Case Study: Continuous deployment makes releases n.

Customer Development 168

Customer Development Developer San Francisco Customer 168

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. I cant really imagine how much it cost our "grownup" counterparts at other dot-com startups to get their first app up and running. Case Study: Continuous deployment makes releases n.

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

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. Real life seldom presents such comparable choices. One last thought.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

APRIL 26, 2009

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. Case Study: Continuous deployment makes releases n. We didnt think wed able to compete with that.

Product Development 88

Product Development Developer San Francisco Product 88

Startup Lessons Learned

SEPTEMBER 2, 2008

Or your cost of customer acquisition just magically floats up to match your customer lifetime value. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Case Study: Continuous deployment makes releases n.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

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.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

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. Case Study: Continuous deployment makes releases n.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

APRIL 18, 2010

Truth: The Lean Startup method is not about cost, it is about speed. Truth: The Lean Startup method is not about cost, it is about speed. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev.

Lean 167

Lean San Francisco Continuous Deployment Startup 167

Startup Lessons Learned

OCTOBER 5, 2010

But," you are sure to ask, "how much will all this bundling cost me?" But," you are sure to ask, "how much will all this bundling cost me?" Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev.

Lean 153

Lean San Francisco Startup Continuous Deployment 153

Startup Lessons Learned

MARCH 23, 2009

I started writing and teaching about shipping imperfect products a few years ago but this is a far better, practical and more powerful presentation. There is a lot to be said about the opportunity cost of perfection, iterative evolution and the difference between shipping a lemon and shipping a band aid.

San Francisco 167

San Francisco Lean Continuous Deployment Audio 167

Startup Lessons Learned

SEPTEMBER 19, 2009

In my presentation this morning, I emphasized three key areas: reducing the personal cost of failure for entrepreneurs, innovation-friendly legal reforms, and access to the digital means of production (slides from my White House presentation are available at the end of this post). The Geeks are doing their part.

San Francisco 150

San Francisco Founder DC Washington 150

Startup Lessons Learned

AUGUST 8, 2009

In particular, we would cover customer development, continuous deployment, minimum viable product, and actionable metrics. Because of the cost and intensity of this program, it is designed for startups with significant venture backing or who have reached profitability. The cost is equivalent to an entry-level FTE.

Lean 102

Lean Programming San Francisco Continuous Deployment 102

Startup Lessons Learned

MAY 17, 2009

Lessons Learned by Eric Ries Sunday, May 17, 2009 Last chance to register for The Lean Startup at HP on May 21 This coming Thursday, May 21, is the last time Im currently scheduled to give the full Lean Startup presentation in the Bay Area. Ship new software at a dizzying pace: multiple times a day while improving quality and lowering costs.

Lean 60

Lean San Francisco Continuous Deployment DC 60

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

JANUARY 27, 2009

Here the key is for your free customers to get value from the site that is greater than the costs they perceive by the fact that youre selling access to them. When the goals not clear, I think you wind up with situations that are essentially value-destroying, where free users are actually driving up costs.

San Francisco 148

San Francisco Lean Continuous Deployment DC 148

Startup Lessons Learned

MAY 22, 2009

Lessons Learned by Eric Ries Friday, May 22, 2009 The Lean Startup at SIPA follow-up I had wonderful time presenting at SIPA last night , and was completely exhausted by the incredible post-speech response. 2009 05 21 The Lean Startup At SIPA View more OpenOffice presentations from Eric Ries. I could not make it to the presentation.

Lean 76

Lean San Francisco Continuous Deployment Startup 76

Startup Lessons Learned

AUGUST 3, 2009

In a lot of cases, this requires a lot of energy invested in talking to customers or metrics and analytics. Without further ado, the video: Slides are below: Minimum Viable Product View more presentations from Eric Ries. Your presentation was something that I needed right now. Case Study: Continuous deployment makes releases n.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

FEBRUARY 11, 2009

Why do Citizens of Humanity jeans cost $200 , when physically similar pants can be had for one-tenth the price? 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 (and a call for he.

San Francisco 102

San Francisco Continuous Deployment Lean DC 102

Startup Lessons Learned

JUNE 12, 2009

So far, we have limited registration at the workshops to people who can afford the admittedly high cost of entry. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Take a look and let me know what you think.

Lean 60

Lean Programming San Francisco Continuous Deployment 60

Startup Lessons Learned

JULY 13, 2009

For example, heres him discussing our collective blindness to queues: To understand the economic cost of queues, product developers must be able to answer two questions. Second, what is the cost of these queues? Today, only 15 percent of product developers know the cost of delay. But, what is the cost of this buffer?

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

JANUARY 6, 2009

There are no canned presentations, so you can come set the agenda. The first event is January 21, and is being put on by Dealmaker Media as part of their Strategy Series events: In the Trenches: Cutting Costs in a Tight Economy. Case Study: Continuous deployment makes releases n.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

AUGUST 18, 2009

Thanks for coming to Boulder with such an insightful presentation. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Case Study: Continuous deployment makes releases n. I really value both.

San Francisco 60

San Francisco DC Sweden Continuous Deployment 60