Customer Development Metrics PHP Product 
Startup Lessons Learned
JANUARY 12, 2009
Lessons Learned by Eric Ries Monday, January 12, 2009 Why PHP won When I first learned to program on the web, Perl + CGI was the dominant platform. But by the time I was building my first websites for commercial use , PHP had taken over. Writing unit tests or mock objects in PHP is an exercise in constant frustration.
Startup Lessons Learned
JANUARY 30, 2009
Build a truly mainstream product. Build the product in stealth mode to build buzz for the eventual launch. The whole company and board play-tested the product to see its new features first hand. Everyone had fun; the product worked. But that was two full years before any customers were allowed to use it.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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. This kind of result is typical when you ship a redesign of some part of your product. Without split-testing, your product tends to get prettier over time. First of all, why split-test? One last note on reporting.
steveblank.com
JULY 8, 2011
interactions, widgets, effects Django – high-level Python framework Cappuccino – open source framework for app development Kodingen – cloud development environment, code editor, hosting service, collaboration platform. Simple editing. Lighthouse – Issue Tracking Tool.
Startup Lessons Learned
NOVEMBER 13, 2008
Lessons Learned by Eric Ries Thursday, November 13, 2008 Five Whys Taiichi Ohno was one of the inventors of the Toyota Production System. His book Toyota Production System: Beyond Large-Scale Production is a fascinating read, even though its decidedly non-practical. Each five whys email is a teaching document. and so forth.
Startup Lessons Learned
SEPTEMBER 30, 2008
If the CEO wants to completely change the product in order to serve a new customer segment, you need someone in the room who can digest the needs of the new (proposed) business, and lay out the costs of each possible approach. Labels: product development 15comments: mukund said. Have you worked with or for a great CTO?
Startup Lessons Learned
JANUARY 2, 2009
At IMVU, we were terrified by how early we shipped (and charged for) our first product. We were even more embarrassed by the pathetically small number of customers we had, and the pathetically low amount of revenue we had earned so far. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?
Expert insights. Personalized for you.
166 
Let's personalize your content