Startup Lessons Learned

FEBRUARY 20, 2009

Similar results apply in product management, design, testing, and even operations. Take the example of a design team prepping mock-ups for their development team. Give the dev team your very first sketches and let them get started. Today, I want to talk about the reasons smaller batches are better.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Seeing Both Sides

SEPTEMBER 15, 2015

This post was co-authored with Omri Stern and originally appeared in Harvard Business Review. In 2014, for example, 18 IPOs raised a record-breaking $9.8 In the old model of Israeli startups, many Israeli executive teams would hire a vice president of sales in the U.S. Israel has been branded the “startup nation.” We think so.

Cofounder 20

Cofounder Technical Review United States 20

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.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

NOVEMBER 17, 2008

Playing with new technologies. 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. What is customer development? Seeing whats possible.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

NOVEMBER 29, 2008

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. Still, a startup product development team is a service organization. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

OCTOBER 20, 2008

The team cant get permission from the business leaders to get "extra time" for fixing. Because there are no tests for new features (or operational alerts for the production code), the code that supports those new features could go bad at any moment. Second was not changing the requirements without full sign-off. Excellent post Eric.

Software Review 164

Software Review Engineer Management Technical Review 164