Startup Lessons Learned

SEPTEMBER 15, 2008

Lessons Learned by Eric Ries Monday, September 15, 2008 The one line split-test, or how to A/B all the time Split-testing is a core lean startup discipline, and its one of those rare topics that comes up just as often in a technical context as in a business-oriented one when Im talking to startups. First of all, why split-test?

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

SEPTEMBER 10, 2008

Lessons Learned by Eric Ries Wednesday, September 10, 2008 Smarticus — 10 things you could be doing to your code right now Smarticus — 10 things you could be doing to your code right now A great checklist of techniques and tools for making your development more agile, written from a Rail perspective. Expo SF (May. . Expo SF (May.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

SEPTEMBER 12, 2008

It’s easy to overestimate the impact of this kind of traffic because it just feels good to have your name and company featured. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R. It strokes your ego.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

JUNE 5, 2009

Lessons Learned by Eric Ries Friday, June 5, 2009 It’s a startup, not a spreadsheet Some people, when they start to realize the power of using data to inform their decisions, become obsessed with optimization. Unfortunately, most decisions that confront startups lack a definitive right answer. But this is wrong, too.

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Startup Lessons Learned

OCTOBER 4, 2008

(Maybe youd like to start with The lean startup , How to listen to customers , or What does a startup CTO actually do? ) In 2007, BusinessWeek named Ries one of the Best Young Entrepreneurs of Tech and in 2009 he was honored with a TechFellow award in the category of Engineering Leadership.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

FEBRUARY 20, 2009

Its had tremendous impact in many areas: continuous deployment , just-in-time scalability , and even search engine marketing , to name a few. 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?

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

APRIL 14, 2009

Lessons Learned by Eric Ries Tuesday, April 14, 2009 Validated learning about customers Would you rather have $30,000 or $1 million in revenues for your startup? In an early-stage startup especially, revenue is not an important goal in and of itself. Don’t startups exist for the same reason? How does that stack up?

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

JANUARY 18, 2010

Ash Maurya is the founder of WiredReach , a bootstrapped startup that he has been running for seven years. Recently, he was bitten by the lean startup bug and has started writing about his experiences attempting to apply lean startup and customer development principles. Things started to slip.

Continuous Deployment 151

Continuous Deployment San Francisco Lean Wiki 151

Startup Lessons Learned

OCTOBER 26, 2009

The key to successful integration of customer feedback is to make each kind of collection part of the regular company discipline of building and releasing products. The key to successful integration of customer feedback is to make each kind of collection part of the regular company discipline of building and releasing products.

Advisory Board 151

Advisory Board Customer San Francisco Lean 151

Startup Lessons Learned

JANUARY 19, 2009

Fundamentally, lean startups do more with less, because they systematically find and eliminate waste that slows down value creation. I want to talk specifics, and when you come right down to it, most technology startups dont have a very interesting cost structure. As a mentor of mine always says, "Startups dont starve, they drown."

Lean 140

Lean Hiring San Francisco Continuous Deployment 140

Startup Lessons Learned

JULY 29, 2009

Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage. In a startup, we should take full advantage of our options, even if they feel dirty or riddled with technical debt. Startups are always moving, so invest in moving faster and better.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

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

FEBRUARY 7, 2010

Lessons Learned by Eric Ries Sunday, February 7, 2010 Tell your Startup Visa story Ive been promising big Startup Visa -related news on Twitter for a few weeks. Weve created a place where you can tell your Startup Visa story anonymously if youd like. There is news, its very exciting, and I still cant share it. Soon, I promise.

San Francisco 118

San Francisco DC Startup Lean 118

Startup Lessons Learned

DECEMBER 16, 2009

Lessons Learned by Eric Ries Wednesday, December 16, 2009 What is Lean about the Lean Startup? That foundational idea, so clearly articulated in books like Lean Thinking, is what originally led me to start using the term lean startup. The following is a guest post for Startup Lessons Learned by the legendary Kent Beck.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

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.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

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

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

FEBRUARY 11, 2009

The same is true of brand-name products in almost every category (and it can be measured ). If given the opportunity to work with two customer segments, one of which sees your product as a basic utility and another of which sees it as a lifestyle statement, choose the latter. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 102

San Francisco Continuous Deployment Lean DC 102

Startup Lessons Learned

JULY 9, 2009

In the summer of 1999, I started working on a startup from my college dorm. All the good domain names were taken, all the good ideas were being implemented. If Id bought just a handful of the "best of the rest" domain names that were available at the time (for a whopping $70 each), I probably could have just retired right then.

San Francisco 94

San Francisco Lean Continuous Deployment DC 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. First, a caveat.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

JULY 13, 2009

It moves at a rapid clip, each argument backed up with the relevant math and equations: marginal profit , Littles law , Markov processes , probability theory , you name it. Its goal is to help us recognize that every artifact of our product development process is really just a proxy variable. This is not for the faint of heart.

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

OCTOBER 7, 2008

If necessary, consider doing this under a different brand name than the one you are wedded to using. 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.

San Francisco 68

San Francisco Lean Retention SEM 68

Startup Lessons Learned

SEPTEMBER 27, 2010

Yet startups rely on collective learning in order to find their way. I believe this is one reason why the myth of the dictatorial startup founder has such enduring appeal. Startups are different, leading to this axiom: if you do not know who the customer is, you do not know what quality is. I understand this fear.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

FEBRUARY 10, 2009

It’s also not a new technique here, we’ve been practicing continuous deployment for years; far longer than I’ve been a member of this startup. But, unfortunately, startups cant afford to adopt that standard. In a lot of cases, thats just a fancy name for revenue or profit, but not always. But it worked.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

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

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

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. Imagine you want to store data about customers, each of whom has "last name" field in your database. But startups rarely have either luxury. Give each entity a name.

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

DECEMBER 14, 2009

Lessons Learned by Eric Ries Monday, December 14, 2009 Business ecology and the four customer currencies Lately, I’ve been rethinking the concept of “business model&# for startups, in favor of something I call “business ecology.&# A successful startup strives for this latter case.

Customer 156

Customer San Francisco Viral Lean 156

Startup Lessons Learned

SEPTEMBER 18, 2008

Even with only a few months of development, third parties have crammed every single category in the store full of apps. All I see is a name, an icon, a price, the developers name, and a review star-rating. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Distribution 74

Distribution San Francisco Lean Continuous Deployment 74

Startup Lessons Learned

SEPTEMBER 13, 2008

We would pretty much bid on any phrase that was "[name of competitive product] chat" and variations like that. And then we would use that simple analytics system I mentioned to monitor the conversion rates of customers from each campaign. Its now a technique I recommend for any web-based startup. I just came across this post.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

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

MARCH 24, 2009

When I work with startups on improving engagement, I really try to emphasize the importance of their most powerful lever: positioning. In most applications, most of the time, customers return to use the application not in response to a notification or event, but under their own volition. Expo SF (May. . Expo SF (May.

Metrics 88

Metrics San Francisco Lean Viral 88

Startup Lessons Learned

SEPTEMBER 22, 2008

Lessons Learned by Eric Ries Monday, September 22, 2008 You dont need as many tools as you think Im always excited to see someone else writing about lessons learned from their startup, and wanted to link today to Untitled - Startup Lessons Learned -- Take it with a grain of salt. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68

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. Instead, we try to accelerate with respect to validated learning about customers. How can we do split-testing when we have only a pathetically small number of customers ?

San Francisco 154

San Francisco Lean Metrics Design 154

Startup Lessons Learned

OCTOBER 11, 2009

Ironically, meetings like this had given data and experimentation a bad name inside this company. Ironically, meetings like this had given data and experimentation a bad name inside this company. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? What a waste. What a waste.

San Francisco 133

San Francisco Lean Metrics Continuous Deployment 133

Startup Lessons Learned

SEPTEMBER 13, 2010

Or take a recent TechCrunch article about a startup I wont name: “X billion messages sent since June 2009.&# Or take a recent TechCrunch article about a startup I wont name: “X billion messages sent since June 2009.&# The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 154

San Francisco Metrics Lean PR 154

Startup Lessons Learned

OCTOBER 23, 2009

This is especially useful in situations, like most B2B businesses, where the total number of customers is likely to be small. This case study illustrates one company’s attempt to do customer development by testing their vision with customers before writing a single line of code. Read on and judge for yourself.

San Francisco 144

San Francisco Customer Wiki Lean 144