Customer Development Design Development Team Review San Francisco 
Startup Lessons Learned
NOVEMBER 8, 2008
Lessons Learned by Eric Ries Saturday, November 8, 2008 What is customer development? But too often when its time to think about customers, marketing, positioning, or PR, we delegate it to "marketroids" or "suits." Many of us are not accustomed to thinking about markets or customers in a disciplined way. Heres the catch.
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.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
OCTOBER 5, 2008
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.
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. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?
Startup Lessons Learned
JUNE 8, 2009
You constantly assess the situation, looking for hazards and timing your movements carefully to get across safely. For example, a recent event I held started with a customer validation exercise (actually, this example is fictionalized for clarity). It was pretty ugly, the marketing and design sucked, and I was embarrassed by it.
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. April 23, 2010 in San Francisco.
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.
168 
Let's personalize your content