Startup Lessons Learned

NOVEMBER 25, 2010

On April 1, 2008, I was as nervous as I have ever been in my life. It was just minutes before I was supposed to go on stage for the very first time and present The Lean Startup to a large audience, at a big conference. This is a Lean Startup talk we’re speaking of, people. Don’t think I wasn’t prepared.

Advisory Board 165

Advisory Board Lean Cofounder Audience 165

Startup Lessons Learned

OCTOBER 6, 2009

In addition to some of my recent talks, you can learn more about the Startup Visa movement and enjoy two really interesting lean startup case studies. pbWorks (formerly pbWiki) was one of the first companies that ever invited me to join their advisory board. The Lean Startup Intensive is tomorrow at Web 2.0.

Audio 118

Audio San Francisco Video Continuous Deployment 118

Startup Lessons Learned

OCTOBER 19, 2009

Unfortunately, after months or even years of development, many companies discover that customers arent willing to buy their new wares. It isnt until a customer actually clicks or calls to place an order that TPGTEXs developers will build the software. "We The Inc story, and many others, does a good job emphasizing its lean-ness.

San Francisco 137

San Francisco Product Lean Continuous Deployment 137

Startup Lessons Learned

JUNE 22, 2009

Lessons Learned by Eric Ries Monday, June 22, 2009 Pivot, dont jump to a new vision In a lean startup , instead of being organized around traditional functional departments, we use a cross-functional problem team and solution team. Each has its own iterative process: customer development and agile development respectively.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

OCTOBER 5, 2009

It’s important to invest in good architecture so that your website will scale once customers arrive. If you make that investment, and then customers arrive, and the site stays up, most companies will reward the people who built the architecture and, thus, prevented the scaling problems. How upset will those customers be?

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 133

Startup Lessons Learned

OCTOBER 11, 2009

The larger-account division wanted to move the pricing in just the other direction – making the low-end products more expensive, so their large customers would have an increased incentive to upgrade. Many custom reports had been created for this meeting, and the data warehouse team was in the meeting, too.

San Francisco 133

San Francisco Lean Metrics Continuous Deployment 133

Startup Lessons Learned

OCTOBER 23, 2009

Lessons Learned by Eric Ries Friday, October 23, 2009 Case Study: Using an LOI to get customer feedback on a minimum viable product How much work should you do on a new product before involving customers? But other times, the right way to learn is actually to show a product prototype to customers one-on-one.

San Francisco 144

San Francisco Customer Wiki Lean 144

betashop.com

OCTOBER 8, 2012

It’s not about you, it’s about your customers. At Fab we have been focused from day 1 on making our customers smile. Passion for building a business is not enough; there needs to be passion for your customer and solving your customer’s problem.?. Your customer is growing up on social media. Provide feedback.

Technical Review 108

Technical Review Technology Software Review Valuation 108

Startup Lessons Learned

OCTOBER 19, 2009

Three reasons: change the world, make customers’ lives better and create an organization of lasting value. Three reasons: change the world, make customers’ lives better and create an organization of lasting value. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Expo SF (May.

San Francisco 111

San Francisco Lean Continuous Deployment DC 111