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). Hence, cutting corners often paid huge dividends. Defective prototype code was as often thrown out (because customers didnt want it) as it was fixed (when customers did).

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

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

In my experience, the majority of changes we made to products have no effect at all on customer behavior. Thats when this approach can pay huge dividends. The report is set up to show you what happened to customers who registered in that period (a so-called cohort analysis ). First of all, why split-test?

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

OCTOBER 19, 2009

Unfortunately, after months or even years of development, many companies discover that customers arent willing to buy their new wares. It isnt until a customer actually clicks or calls to place an order that TPGTEXs developers will build the software. "We The biggest is the confusion over why this tactic is useful.

San Francisco 137

San Francisco Product Lean Continuous Deployment 137

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. Luckily, in most prevention situations, even the first few steps in prevention can pay time-savings dividends quickly.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

JANUARY 28, 2009

They have a product that has a moderate number of customers. Its well done, looks professional, and the customers that use it like it a lot. Most of all, I encouraged them to start talking to their most passionate customers and running some big experiments based on that feedback. Only pay for benefits to customers.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79