2009 Development Team Review Engineer Lean 
Startup Lessons Learned
OCTOBER 20, 2008
Lessons Learned by Eric Ries Monday, October 20, 2008 The engineering managers lament I was inspired to write The product managers lament while meeting with a startup struggling to figure out what had gone wrong with their product development process. This engineering manager is a smart guy, and very experienced.
Startup Lessons Learned
FEBRUARY 20, 2009
Lessons Learned by Eric Ries Friday, February 20, 2009 Work in small batches Software should be designed, written, and deployed in small batches. Its had tremendous impact in many areas: continuous deployment , just-in-time scalability , and even search engine marketing , to name a few. For software, the easiest batch to see is code.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
OCTOBER 5, 2008
I met one recently that is working on a really innovative product, and the stories I heard from their development team made me want to cringe. The product manager was clearly struggling to get results from the rest of the team. Labels: product development 8comments: Vincent van Wylick said. Frustration is mounting.
View from Seed
MARCH 19, 2015
Engineers and even marketers proudly claim to be “full stack.” Starting in 2009, Savoia began using an approach as an engineering director at Google that helped the tech giant know whether it was about to build the right product for the market … or a product that would flop. Why doesn’t everyone do this?”
SoCal CTO
NOVEMBER 1, 2010
Was it a Startup Founder Developer Gap ? Did they really need a Startup CTO or Developer or both? Did they have a Weak Development Team ? So before you ask someone to even spend an hour of their time writing code or reviewing specs make sure you can pay them in some form (coffee, dinner, laptop, etc.),
Startup Lessons Learned
NOVEMBER 8, 2008
Steve Blank has devoted many years now to trying to answer that question, with a theory he calls Customer Development. This theory has become so influential that I have called it one of the three pillars of the lean startup - every bit as important as the changes in technology or the advent of agile development. Great post.
Startup Lessons Learned
JUNE 8, 2009
Lessons Learned by Eric Ries Monday, June 8, 2009 Datablindness Most of us are swimming in a sea of data about our products, companies, and teams. You constantly assess the situation, looking for hazards and timing your movements carefully to get across safely. For a lean startup , this lack of discipline is anathema.
Expert insights. Personalized for you.
164 
Let's personalize your content