Remove Continuous Deployment Remove Customer Remove Dividend Remove Product
article thumbnail

Speed up or slow down? (for Harvard Business Review)

Startup Lessons Learned

This is the first post that moves into making specific process recommendations for product development. Everyone was in the flow; the team was hyper-productive. In many cases, they did the impossible, building a new product faster, cheaper, and better than anyone could have predicted. And a certain amount of chaos reigned too.

article thumbnail

Lessons Learned: Work in small batches

Startup Lessons Learned

Its had tremendous impact in many areas: continuous deployment , just-in-time scalability , and even search engine marketing , to name a few. I owe it originally to lean manufacturing books like Lean Thinking and Toyota Production System. Similar results apply in product management, design, testing, and even operations.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Lessons Learned: The one line split-test, or how to A/B all the time

Startup Lessons Learned

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?

article thumbnail

Lessons Learned: Inc Magazine on Minimum Viable Product (and a.

Startup Lessons Learned

Lessons Learned by Eric Ries Monday, October 19, 2009 Inc Magazine on Minimum Viable Product (and a response) Inc Magazine has a great new piece up about the increasing use of the Minimum Viable Product by businesses (and not just startups). Like many companies, TPGTEX rolls out new products several times a year.

article thumbnail

How to conduct a Five Whys root cause analysis

Startup Lessons Learned

Five Why’s rarely works for general abstract problems like “our product is buggy&# or “our team moves too slow.&# 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.

article thumbnail

Lessons Learned: Refactoring yourself out of business

Startup Lessons Learned

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. Still, theyre not really hitting it out of the park, because their product isnt growing new users as fast as theyd like, and they arent making any money from the current users.