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.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

NOVEMBER 29, 2008

Finding great engineers is hard; figuring out whos good is even harder. The technical interview is at the heart of these challenges when building a product development team, and so I thought it deserved an entire post on its own. I have found this quite rare in engineers. Thats OK, were not trying to hire a therapist.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

NOVEMBER 17, 2008

Now its time to start to think seriously about how to find a repeatable and scalable sales process, how to position and market the product, and how to build a product development team that can turn an early product into a Whole Product. Case Study: Continuous deployment makes releases n. What is customer development?

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

DECEMBER 7, 2008

In a few cases, they are clearly smart people in a bad situation, and Ive written about their pain in The product managers lament and The engineering managers lament. As a last disclaimer, please consult the definition of the word hacker if youre not familiar with the controversies surrounding that term.) Hire a CTO or VP Engineering.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

NOVEMBER 8, 2008

Our goal in product development is to find the minimum feature set required to get early customers. In order to do this, we have our customer development team work hard to find a market, any market, for the product as currently specified. Case Study: Continuous deployment makes releases n. This is a common mistake.

Customer Development 168

Customer Development Developer San Francisco Customer 168