Startup Lessons Learned

OCTOBER 26, 2009

Lessons Learned by Eric Ries Monday, October 26, 2009 A real Customer Advisory Board A reader recently asked on a previous post about the technique of having customers periodically produce a “state of the company&# progress report. One example is having a real Customer Advisory Board.

Advisory Board 151

Advisory Board Customer San Francisco Lean 151

Startup Lessons Learned

OCTOBER 4, 2008

He serves on the advisory board of a number of technology startups, and has worked as a consultant to a number of startups, companies, and venture capital firms. Thanks to Suns amazing PR blitz, there was tremendous demand for experts on Java, and I did my best to convince people that I was one of that mythical breed.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

OCTOBER 5, 2009

If we’re practicing continuous deployment, we can be confident that we’ll be able to rush an emergency fix into production without risking introducing further problems. Case Study: Continuous deployment makes releases n. We can also ask: how would we fix the problem if it does occur?

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 133

Startup Lessons Learned

JULY 29, 2009

As in many scalability decisions, we’d have been much better off investing in agility, so that we could change the architecture in response to actual customer demand, rather than trying to predict the future. should the test subjects be part of the customer advisory board? One last thought.

Technical Review 168

Technical Review Software Review San Francisco Lean 168