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? This may sound crazy, coming as it does from an advocate of c harging customers for your product from day one. They are gaining valuable customer data.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

MARCH 16, 2009

Lessons Learned by Eric Ries Monday, March 16, 2009 Combining agile development with customer development Today I read an excellent blog post that I just had to share. The breakthrough idea of agile is that software should be built iteratively, with the pieces that customers value most created first. Enter Jims post.

Agile 111

Agile Customer Development Developer San Francisco 111

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

SoCal CTO

JANUARY 5, 2011

- SoCal CTO , January 13, 2010 5 Lessons from 150 startup pitches - A Smart Bear: Startups and Marketing for Geeks , July 11, 2010 9 Reasons Why Many Smart People Go Nowhere - Life Beyond Code , March 29, 2010 No Accounting For Startups - Steve Blank , February 22, 2010 Startup Advice In Exactly Three Words - #StartupTriplets - OnStartups , January (..)

Silicon Valley 378

Silicon Valley Startup Term Sheet Venture Capital 378

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. When operating with continuous deployment, its almost impossible to have integration conflicts. Case Study: Continuous deployment makes releases n.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

SEPTEMBER 15, 2008

See Customer Development Engineering for my first stab at articulating the theory involved) Ferocious customer-centric rapid iteration, as exemplified by the Customer Development process. Labels: customer development , lean startup 8comments: Amy said. Case Study: Continuous deployment makes releases n.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Startup Lessons Learned

AUGUST 3, 2009

First, a definition: the minimum viable product is that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort. In a lot of cases, this requires a lot of energy invested in talking to customers or metrics and analytics. Some caveats right off the bat.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

NOVEMBER 13, 2008

It seems your cluster architecture is one of the key architectural constraints making continuous deployment possible. If you cant deploy to 5% of the nodes and check the results, then how would you accomplish continuous deployment? The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

SEPTEMBER 14, 2008

Lessons Learned by Eric Ries Sunday, September 14, 2008 How to listen to customers, and not just the loud people Frequency is more important than talking to the "right" customers, especially early on. Youll know when the person youre talking to is not a potential customer - they just wont understand what youre saying.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

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.&# Let’s begin with the four customer currencies. And this is true outside of games.

Customer 156

Customer San Francisco Viral Lean 156

Startup Lessons Learned

JULY 28, 2010

If you havent seen it, Pascals recent presentation on continuous deployment is a must-see; slides are here. Third, the company expected hundreds of amateurs who performed poorly in the game to realize they weren’t good at investing and therefore become customers. in fact only five people converted into paying customers.

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

Startup Lessons Learned

NOVEMBER 7, 2008

Thats the conclusion Ive come to after watching tons of online products fail for a complete lack of customers. Our goal is to find out whether customers are interested in your product by offering to give (or even sell) it to them, and then failing to deliver on that promise. We finally settled on a $1.99 Setup a simple website.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

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

In my experience, the majority of changes we made to products have no effect at all on customer behavior. The report is set up to show you what happened to customers who registered in that period (a so-called cohort analysis ). This report is set up to tell you about new customers specifically. First of all, why split-test?

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

NOVEMBER 14, 2013

Many workshops thus teach you to apply specific Lean Startup methods: creating experiments, interviewing customers, optimizing pricing, and innovation accounting. We asked him a few questions to learn about continuous delivery, why it’s useful, and what engineers and management need to do to implement it. How do you address that?

Continuous Deployment 162

Continuous Deployment Norway Lean Analytics 162

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? ) That institution will touch many people in its life: customers, investors, employees, and everyone they touch as well. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

SEPTEMBER 30, 2008

When Ive asked mentors of mine who have worked in big companies about the role of the CTO, they usually talk about the importance of being the external face of the companys technology platform; an evangelist to developers, customers, and employees. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

DECEMBER 16, 2009

When a name is misused, as with some of the claims to "agility" extant, the initial interest is followed by disappointment when customers discover there is no corned beef between the slices of rye. Another form of respect is inviting customers to be part of the process of creating those products and services.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

Startup Lessons Learned

OCTOBER 5, 2008

The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Two Ways to Hold Entrepreneurs Accountable (for Ha.

San Francisco 158

San Francisco Management Software Review Product 158

Feld Thoughts

MARCH 11, 2010

I’ve become a big advocate of true Agile development (partly because of my experience with Rally Software – the leader in Agile software development environments) and – more recently – the notion of trying to get to continuous deployment which has been popularized by Eric Ries. Not all of the hackathon projects need to be about code.

Software Review 138

Software Review Wiki Continuous Deployment Agile 138

Startup Lessons Learned

SEPTEMBER 13, 2008

Lessons Learned by Eric Ries Saturday, September 13, 2008 SEM on five dollars a day How do you build a new product with constant customer feedback while simultaneously staying under the radar? Slowly, over time, we optimized (or eliminated) each step in the process of becoming a customer by giving us money. SEM is a simple idea.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

OCTOBER 11, 2010

For "cure for cancer" type businesses, there is no question about who the customer is and what the customer wants, and therefore there is no market uncertainty. Continuous deployment of hardware is an exciting new capability. In order to answer, I have taken to drawing a two-axis diagram.

Continuous Deployment 164

Continuous Deployment Technical Cofounder Cofounder San Francisco 164

Startup Lessons Learned

SEPTEMBER 2, 2008

Scalable systems are no exception - if your assumptions about how many customers youll have, or how they will behave are just a little bit wrong, you can wind up with a massive amount of wasted code. Labels: agile , continuous deployment 1 comments: timothyfitz said. Case Study: Continuous deployment makes releases n.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

APRIL 4, 2010

The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Two Ways to Hold Entrepreneurs Accountable (for Ha.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Startup Lessons Learned

JULY 29, 2009

Unfortunately, customers hated that initial product. Unfortunately, we made two critically flawed assumptions: that customers would primarily consume first-party assets that we shipped to them on CD and that they would tend to congregate in a relatively uniform way. How likely will customers ultimately use that feature?

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

FEBRUARY 22, 2009

To do that they need to understand value, communicate with other business people (like bankers and VCs) about value, and communicate with prospective customers about value. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Case Study: Continuous deployment makes releases n.

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

SEPTEMBER 2, 2008

Labels: agile , listening to customers 3comments: hauteroute said. Wouldn't it make more sense to Learn (customer discovery) then proceed to ideas,code, data, implement and measure? The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Case Study: Continuous deployment makes releases n.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

MARCH 25, 2010

Defective prototype code was as often thrown out (because customers didnt want it) as it was fixed (when customers did). Defective prototype code was as often thrown out (because customers didnt want it) as it was fixed (when customers did). Case Study: Continuous deployment makes releases n.

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

FEBRUARY 28, 2009

Customers dont care if you have good metrics, only if you have a good product. We used those five dollars to buy 100 clicks, every single day, in the hopes that some of those people would become paying customers. We started to put in simple data probes at each of these key stages in our customers usage of the product.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

DECEMBER 23, 2009

Its a gross number, not per-customer: one hit each from a million people is a very different thing than a million hits from just one person. So its reasonable to ask: whats wrong with vanity metrics, at least as a proxy for customer behavior? Its just that the declining segments customers were more valuable.

Metrics 167

Metrics San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

AUGUST 26, 2009

And do your customer development. These quotes are, as is my custom, straight from twitter. Inspiring ideas: real-time biz metrics; safe continuous deployment; A/B split testing. When they could hear the customers complaints in their own voice, it became clear when it was time to up the quality level.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

JULY 2, 2009

When customers are affected, try to have someone who experienced the customer problem first-hand, like the customer service rep who took the calls from angry customers. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Case Study: Continuous deployment makes releases n.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

APRIL 9, 2009

Rather than use boring section headers, I thought Id just quote from actual customers, in their own words. 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.

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

Startup Lessons Learned

OCTOBER 16, 2013

Palantir is a deep technical play and we had a lot of code to write just to fill out the product vision that we had already validated with potential customers; it took us two straight years of development to go from early prototypes to software that could be used in production. It wasn’t always this way. Growth changed all that.

Lean 167

Lean Startup Software Engineering Agile 167

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. It took the idea of Customer Development and made it accessible to a whole new audience. Illustrations by FAKEGRIMLOCK. You can pre-order it starting today.

Entrepreneur 167

Entrepreneur Lean Southern California San Diego 167

Startup Lessons Learned

DECEMBER 8, 2008

The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Two Ways to Hold Entrepreneurs Accountable (for Ha.

Software Review 136

Software Review San Francisco Lean Continuous Deployment 136

Startup Lessons Learned

MAY 31, 2010

When I first encountered customer development , it was considered pure lunacy by mainstream entrepreneurs and VCs. When I first encountered customer development , it was considered pure lunacy by mainstream entrepreneurs and VCs. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 133

San Francisco Lean Technical Review Software Review 133