Design Development Team Review Internet New York 
Startup Lessons Learned
FEBRUARY 20, 2009
Lessons Learned by Eric Ries Friday, February 20, 2009 Work in small batches Software should be designed, written, and deployed in small batches. 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.
Startup Lessons Learned
OCTOBER 5, 2008
But I have a special sympathy for the "product manager" in a startup that is bringing a new product to a new market, and doing their work in large batches. 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.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
JUNE 8, 2009
You constantly assess the situation, looking for hazards and timing your movements carefully to get across safely. It was pretty ugly, the marketing and design sucked, and I was embarrassed by it. So the product development team was busy creating lots of split-tests for lots of hypotheses. Yet it had one huge advantage.
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. Usually, that will be about finding new segments of customers that the company can profitably serve.
Startup Lessons Learned
NOVEMBER 8, 2008
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.
Startup Lessons Learned
APRIL 26, 2009
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. Making UGC work requires good tools, open standards, and proper incentive design. Its a key lean startup concept.
Startup Lessons Learned
OCTOBER 20, 2008
Most of the other processs changes - mandatory design reviews (prelimninary, critical, etc), - documenting all our procedures, and so on - were to support those two factors. It might be more precise to categorize them of two kinds of flaws: flaws in implementation, and flaws in design. Im keen on the two-kinds-of-bugs thing.
Expert insights. Personalized for you.
161 
Let's personalize your content