Startup Lessons Learned

AUGUST 8, 2009

Let me quote an example that I used recently: Remember IMVUs initial IM add-on product? Unfortunately, when we realized the product design was not what customers wanted, we had to pivot to a new product. When we became a standalone network, it didnt matter how easy it was to add new networks, since we never did.

Software Review 87

Software Review Design Software San Francisco 87

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

SEPTEMBER 14, 2008

This was 2004, and we had never even heard of MySpace, let alone had any understanding of social networking. It required hearing customers say it over and over again for us to take a serious look, and eventually to realize that social networking was core to our business. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Startup Lessons Learned

JANUARY 4, 2009

Lessons Learned by Eric Ries Sunday, January 4, 2009 Sharding for startups The most important aspect of a scalable web architecture is data partitioning. This is true of most web application servers, caches like memcached, and all of the network infrastructure that connects them. But startups rarely have either luxury.

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

SEPTEMBER 5, 2008

Spray files across cheap disks on your network. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R. The Lean Startup Intensive is tomorrow at Web 2.0. Startup Lessons Learned - the Conference (April 23.

Open Source 107

Open Source San Francisco Continuous Deployment Lean 107

Startup Lessons Learned

SEPTEMBER 8, 2009

Lessons Learned by Eric Ries Tuesday, September 8, 2009 What would you want to tell Washington DC about startups? 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. And what hurdles could be eliminated?

DC 90

DC Washington San Francisco SBIR 90

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

AUGUST 1, 2009

One of the most common questions I get about the lean startup methodology is, "but what about Steve Jobs ?" He doesnt put out crappy, buggy products and then ask for feedback. So how do you reconcile his success with the lean startup, which seems to suggest the opposite?" And he doesnt shy away from big-bang launch events.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

OCTOBER 20, 2008

Lessons Learned by Eric Ries Monday, October 20, 2008 The engineering managers lament I was inspired to write The product managers lament while meeting with a startup struggling to figure out what had gone wrong with their product development process. After all, our startup is on a fixed budget.

Software Review 164

Software Review Engineer Management Technical Review 164

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. In fact, the curse of product development is that sometimes small things make a huge difference and sometimes huge things make no difference. That’s right.

San Francisco 154

San Francisco Lean Metrics Design 154

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. How did they do it? Expo SF (May.

San Francisco 128

San Francisco Lean Continuous Deployment Agile 128

Startup Lessons Learned

FEBRUARY 22, 2009

I went to excellent public schools (so-called science magnets) that had computer classes, which meant they had networked computers that I could use. If we network them together, theyll answer each others questions and collaborate on projects we can hardly imagine. But I was also very lucky. Theyll take it from there.

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

SEPTEMBER 18, 2008

If everyone I know is using a specific product, in most markets thats a heavy influence. And in some markets its decisive, because of well-known network effects (as happened with Microsoft, eBay, and many others). This can even vary by category, as people apply different criteria to games vs. utilities vs. social networking apps.

Distribution 74

Distribution San Francisco Lean Continuous Deployment 74

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. Glad you don't > develop software for space shuttles. Thanks for the post, Eric. Expo SF (May.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

FEBRUARY 22, 2010

For startups (and other innovators ), that’s a decisive advantage. The work itself, especially in startups, depends primarily on intelligence, communication, creativity and empathy. Their recent article suggests that startups led by women are actually more successful, on average, than those led by men.

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

Startup Lessons Learned

DECEMBER 7, 2008

Those who have the endurance are the ones that tend to lead teams and join startups, because you just cant be successful in a startup situation without empathy. When a startup encounters difficult technical problems, this is the guy you want solving them. I would characterize them as intolerant but not arrogant. What a waste.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

SEPTEMBER 18, 2008

For companies in the early-adopter phase, you can play "the earlyvangelist game" whenever a customer turns out to be too mainstream for your product. Pick a similar product that they do use, and ask them "who was the first person you know who started using [social networking, mobile phones, plasma TV, instant messaging.]?

San Francisco 133

San Francisco Lean Continuous Deployment DC 133

Startup Lessons Learned

AUGUST 24, 2009

In other words, they are facing conditions of extreme uncertainty, just like startups. But, as any startup can tell you, this opens up a tremendous set of opportunities for the rest of us. When I reviewed a recent product development book, it immediately shot up to Amazon sales rank 300. Is that a lot? Is that good?

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

MARCH 11, 2010

Lessons Learned by Eric Ries Thursday, March 11, 2010 For Startups, How Much Process Is Too Much? for Harvard Business Review) In the latest article for my series in HBR, I discuss the problem of how to figure out how much process startups should have. When done right, it can help startups accelerate even as they scale.

San Francisco 120

San Francisco Continuous Deployment Lean DC 120

Startup Lessons Learned

MARCH 13, 2009

Lessons Learned by Eric Ries Friday, March 13, 2009 Dont launch Heres a common question I get from startups, especially in the early stages: when should we launch? Marketing launch) Make a new product available to customers in the general public. In fact, in most situations its a bad idea for startups to synchronize these events.

San Francisco 168

San Francisco PR Lean Early Stage 168

Startup Lessons Learned

SEPTEMBER 19, 2009

Lessons Learned by Eric Ries Saturday, September 19, 2009 Support the Startup Founders Visa with a tweet Its been an exhilarating first day here in Washington DC for the Geeks on a Plane tour. We can remedy it by creating a special visa for startup founders. Its actually part of a lean startup story. Will you join us?

San Francisco 150

San Francisco Founder DC Washington 150

Startup Lessons Learned

JUNE 23, 2009

Lessons Learned by Eric Ries Tuesday, June 23, 2009 Join the lean startup discussion at Facebook on Thursday I recently agreed to join Facebook s fbFund incubator as a mentor. Part of that includes giving a presentation for the fbFund companies on the lean startup methodology. The Lean Startup Intensive is tomorrow at Web 2.0.

Lean 74

Lean San Francisco Continuous Deployment DC 74

Startup Lessons Learned

JULY 31, 2009

Lessons Learned by Eric Ries Friday, July 31, 2009 A new way to recruit for (and find) startup jobs In my work, I come across a lot of great startups. Similarly, I get pinged by many colleagues, friends, and fans who are looking to find a job with a startup. Great startups are always hiring, if the fit is right.

San Francisco 68

San Francisco Lean Startup Continuous Deployment 68

Startup Lessons Learned

JANUARY 27, 2009

For network-effects businesses, like Skype , just being on the network is enough to create value. I also work for a startup and we have been grappling with the same problem ever since we went public. We're keeping ourselves free for the community that has helped us build our product; premium vs basic seems wrong to us.

San Francisco 148

San Francisco Lean Continuous Deployment DC 148

Startup Lessons Learned

JANUARY 11, 2009

This model has not translated well to the world of social networking, because customers of social networks engage sites in a different way than customers of search engines. Social network page views are much more likely to be internally focused; ads are more of a distraction. As a result, CPI advertising is incredibly cheap.

San Francisco 68

San Francisco Social Network Lean Continuous Deployment 68

Startup Lessons Learned

OCTOBER 7, 2008

For example, if any of the mobile ad networks gets major traction, they may become a dominant way that people discover new apps. If the rating in the App Store is based on usage, I am sure those popular social networking applications are sure to be in the top and the hot seat always. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 68

San Francisco Lean Retention SEM 68

Startup Lessons Learned

DECEMBER 16, 2008

Facebook , LinkedIn , and other successful social networks have elevated this technique to a high art. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R. The Lean Startup Intensive is tomorrow at Web 2.0.

Viral 140

Viral San Francisco Lean Continuous Deployment 140

Startup Lessons Learned

JULY 9, 2009

In the summer of 1999, I started working on a startup from my college dorm. And the great ideas that became todays successful tech startups dwarf anything that had been done to that point. Nonetheless, my first startup was a tool for college students from elite colleges to create resumes and help them find jobs. Great post!

San Francisco 94

San Francisco Lean Continuous Deployment DC 94