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

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

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

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

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? Expo SF (May.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

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

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 Lean Startup Intensive is tomorrow at Web 2.0. Amazing lean startup resources Is Entrepreneurship a Management Science? Expo SF (May. for Harvard Business Revie.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

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 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. The Lean Startup Intensive is tomorrow at Web 2.0. Amazing lean startup resources Is Entrepreneurship a Management Science? Expo SF (May.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

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

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 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. How much will it cost to solve this problem now? They are usually among the most heated arguments a company has.

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. If you can start getting ROI on a feature in month one of a twelve month project versus waiting until the end, youve comparatively reduced the cost of development by the revenue generated by that feature over 11 months. Expo SF (May.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

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

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

SEPTEMBER 2, 2020

The benefit of the hammer and the dance is lower, and also the cost is higher." And in fact, The Lean Startup is very much that. It's focused on how to learn as fast as possible with as little cost as possible. Just look at your measures in terms of cost-benefit. Sweden decided, "You know what?

South Korea 114

South Korea Silicon Valley Sweden Italy 114

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 ?" So how do you reconcile his success with the lean startup, which seems to suggest the opposite?" Plus, the premise of the question misunderstands the lean startup, too. And he doesnt shy away from big-bang launch events.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

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. People want to get started with Lean Startup but arent exactly how. Its called the " The Lean Startup Bundle " and it is available this week only. Phew, Im exhausted.

Lean 153

Lean San Francisco Startup Continuous Deployment 153

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

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. But it worked.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

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

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

JULY 29, 2009

Although it costs to pay down the principal, we gain by reduced interest payments in the future. 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. The human tendency to moralize about debt affects engineers, too.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

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. For those of you with some background in lean manufacturing, you may notice that integration risk sounds a lot like work-in-progress inventory. The Lean Startup Intensive is tomorrow at Web 2.0.

Software Review 136

Software Review San Francisco Lean Continuous Deployment 136

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. Amazing lean startup resources Is Entrepreneurship a Management Science?

Customer Development 168

Customer Development Developer San Francisco Customer 168

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

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.

Continuous Deployment 131

Continuous Deployment San Francisco Software Review Lean 131

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 Lean Startup Intensive is tomorrow at Web 2.0. Amazing lean startup resources Is Entrepreneurship a Management Science?

Open Source 107

Open Source San Francisco Continuous Deployment Lean 107

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

The Next Web

JULY 29, 2013

The costs of living are incredibly high and you will compete with the world’s most successful tech businesses for talent. What are the costs of living in Berlin? It also helped us to start lean and simple, and grow our product into something bigger. He started Skype in Sweden. It’s a difficult and long process.

San Francisco 125

San Francisco Cofounder Germany Europe 125

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. Those are the kinds of indefinite costs that make our team grind to a halt over time. First of all, its a myth that cutting corners saves time.

Software Review 164

Software Review Engineer Management Technical Review 164

crowdSPRING Blog

MARCH 30, 2012

Lean Marketing Tips: Hyperlocal Marketing Channels – [link]. Will CPE (Cost Per Engagement) advertising ever take off? Lean Marketing Tips: Hyperlocal Marketing Channels – [link]. As Sweden Goes, So Goes the World: The Beginning of the End of Cash – [link]. Is Pinterest the next Facebook? – [link].

Social Media 93

Social Media Small Business Design Media 93

Startup Lessons Learned

JANUARY 12, 2009

At the cost of a little extra indirection, you can organize your code around a series of long-lived objects, each of whom communicates with the other objects in simple, easy-to-understand ways. Yes, Python developers DO tend to cost more. Memory-resident code made it slightly slower to iterate on scripts. Im curious.

PHP 166

PHP Software Review Ruby San Francisco 166

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

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. Amazing lean startup resources Is Entrepreneurship a Management Science? It can benefit your team in other, more surprising ways as well. Expo SF (May.

Software Review 68

Software Review Software Hiring San Francisco 68

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