Remove Continuous Deployment Remove Design Remove Development Team Review Remove Programming
article thumbnail

Lessons Learned: Work in small batches

Startup Lessons Learned

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. I dont think so.

article thumbnail

Lessons Learned: The product manager's lament

Startup Lessons Learned

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. These specs are handed to a designer, who builds layouts and mockups of all the salient points.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Datablindness

Startup Lessons Learned

You constantly assess the situation, looking for hazards and timing your movements carefully to get across safely. I suddenly lose my ability to judge if our marketing programs are being effective. It was pretty ugly, the marketing and design sucked, and I was embarrassed by it. Use pilot programs. What’s happening?

article thumbnail

Lessons Learned: The four kinds of work, and how to get them done.

Startup Lessons Learned

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?

article thumbnail

Lessons Learned: What is customer development?

Startup Lessons Learned

You can learn about customer development, and quite a bit more, in Steves book The Four Steps to the Epiphany. This is a self-published book, originally designed as a companion to Steves class at Berkeleys Haas school of business. Our goal in product development is to find the minimum feature set required to get early customers.

article thumbnail

Lessons Learned: Product development leverage

Startup Lessons Learned

The idea of leverage is simple: for every ounce of effort your product development team puts into your product, find ways to magnify that effort by getting many other people to invest along with you. That engine of creativity has led to a catalog of something like 2 million virtual goods authored by a hundred thousand developers.

article thumbnail

Lessons Learned: The engineering manager's lament

Startup Lessons Learned

When I was working my first programming jobs, I was introduced to the following maxim: "time, quality, money - pick two." As I evolved my thinking, I started to frame the problem this way: How can we devise a product development process that allows the business leaders to take responsibility for the outcome by making conscious trade-offs?