Startup Lessons Learned

SEPTEMBER 14, 2008

Lessons Learned by Eric Ries Sunday, September 14, 2008 How to listen to customers, and not just the loud people Frequency is more important than talking to the "right" customers, especially early on. Youll know when the person youre talking to is not a potential customer - they just wont understand what youre saying.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Steve Blank

OCTOBER 5, 2009

The VP of Sales and I flew to Providence to convince Andy van Dam at Brown to join our company, or at a minimum lead our advisory board. Oh, and since it was not code compatible with anything, we were going to have to port all the key scientific applications our customers needed (as soon as we figured out who they were.)

North Carolina 125

North Carolina Silicon Valley Fractional VPE Part-Time VPE 125

Startup Lessons Learned

JUNE 22, 2009

Each has its own iterative process: customer development and agile development respectively. Some startups avoid getting customer feedback for precisely this reason: they are afraid that if early reactions are negative, theyll be "forced" to abandon their vision. IMVU had a roughly two-month-long development cycle.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

OCTOBER 4, 2008

Maybe youd like to start with The lean startup , How to listen to customers , or What does a startup CTO actually do? ) 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. Would love to get in touch.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155