Startup Lessons Learned

JULY 3, 2009

Yet, I think this definition is too important to leave out. 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. Nothing is more demoralizing to an engineering team.

Lean 60

Lean San Francisco Continuous Deployment Cofounder 60

Startup Lessons Learned

APRIL 14, 2009

Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. This is an incredible skill, one that most engineers overlook. 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.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

JUNE 5, 2009

I think this idea is particularly appealing to those of us from an engineering background. Unfortunately, most decisions that confront startups lack a definitive right answer. If it costs $0.10 to acquire an early adopter, how much should it cost to acquire a mainstream customer? But $10.00?

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

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

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. Case Study: Continuous deployment makes releases n. Though technology tools and Web 2.0

San Francisco 113

San Francisco Lean Technical Review Distribution 113

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

San Francisco 150

San Francisco Founder DC Washington 150

Startup Lessons Learned

OCTOBER 19, 2009

Then, the company spends no more than a few hundred dollars marketing the product through search engines and to the contacts in its sales database and LinkedIn. Development time is typically no more than two to three weeks, and it generally takes just a few orders to cover development costs.

San Francisco 137

San Francisco Product Lean Continuous Deployment 137

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. Second, the definitions use of the words maximum and minimum means it is decidedly not formulaic. Definitely highlights the beauty of the web.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

APRIL 9, 2009

No engineering team. But where it makes sense, that team may also include engineers building new experiments or prototypes to try with customers. And instead of design, engineering, QA, and operations we have a solution team implementing a startup-centric version of agile development. You need a problem team and a solution team."

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

Startup Lessons Learned

FEBRUARY 28, 2009

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. Most of all, these arguments stemmed from a simple misconception: that the code we had written was an asset, and that it would cost us to throw it away. Expo (and a call for he.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

AUGUST 1, 2009

Which comes to the second major principle: halt work that leads to more waste, even if it means abandoning sunk costs. Just because something looks pretty, or feels like a good idea, or has a lot of sunk cost in it, does not mean it should be pursued. This is a version of the andon cord technique from lean manufacturing.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

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. Definitely interested in the perspective of the open-source contributor solicited with a job offer. Im definitely curious about your thoughts on how to present the company right. Expo (and a call for he.

Software Review 68

Software Review Software Hiring San Francisco 68

Startup Lessons Learned

DECEMBER 14, 2009

Some companies definitely should. Others definitely shouldn’t. A business that strives for something like this should absolutely be charging money from day one, in order to establish baselines for their two key metrics: CPA (the cost to acquire a new customer) and LTV (the lifetime value of each acquired customer).

Customer 156

Customer San Francisco Viral Lean 156

Startup Lessons Learned

DECEMBER 7, 2008

In a few cases, they are clearly smart people in a bad situation, and Ive written about their pain in The product managers lament and The engineering managers lament. As a last disclaimer, please consult the definition of the word hacker if youre not familiar with the controversies surrounding that term.) Hire a CTO or VP Engineering.

Software Review 94

Software Review Technical Review San Francisco Part-Time VPE 94

Startup Lessons Learned

OCTOBER 23, 2009

We backed into prices from all sorts of angles, estimating the time-cost of equivalent functionality, competitive offerings, other tools we were potentially displacing -- but in the end, we lobbed a few numbers at them and waited to see if they flinched. BUT it definitely does NOT have the super-duper-hyper-ultra-cool Web 2.0

San Francisco 144

San Francisco Customer Wiki Lean 144

Startup Lessons Learned

DECEMBER 16, 2008

But if your new positioning message improves your engagement loop by more than the cost to your viral loop , you have a net win on your hands. You definitely brought clarity around the engagement loop re: A-B-C-D makes perfect sense and can be mapped against any flow that has the possibility to go viral. very cool post Eric!

Viral 140

Viral San Francisco Lean Continuous Deployment 140

Startup Lessons Learned

NOVEMBER 22, 2008

In fact, there were some definite skeptics about whether they measured anything of value at all, since it is always dismaying to get data that says the changes youre making to your product are not affecting customer satisfaction one way or the other. The whole episode cost us hundreds of thousands of dollars in lost revenue.

.Net 158

.Net Operations San Francisco Lean 158

Startup Lessons Learned

JANUARY 28, 2009

I was told they werent sure, because all of their engineers were currently busy refactoring. The engineering team has decided its reached a breaking point, and is taking several weeks to bring it up to modern standards, including unit tests, getting started with continuous integration , and a new MVC architecture.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

Startup Lessons Learned

FEBRUARY 12, 2009

Resegmented market (low cost variety). Heres a situation where you offer to do the job for 1/10th the cost. Here your challenge is to convince that manager that you really can do the job at such low cost. They must be thinking "if its costing people their jobs, it must really work. Maybe I should try that."

San Francisco 89

San Francisco Continuous Deployment Ruby Lean 89

Startup Lessons Learned

JANUARY 12, 2009

At IMVU, when wed hire a new engineer, we could get them to ship code to production on their first day, even if they had never programmed in PHP before. Do you think that the long-term maintainability and reliability costs that result from using PHP are outweighed by how much time and money it saves you in the beginning?

PHP 166

PHP Software Review Ruby San Francisco 166

Startup Lessons Learned

SEPTEMBER 11, 2009

This single decision wound up costing the company significant revenue and over the course of several months sent its customer growth into decline. In the end, we managed to repair the damage, but only after losing a lot of time and at significant opportunity cost. We were totally unprepared for the magnitude of what happened.

Community 158

Community Management Lean Software Review 158