Startup Lessons Learned

SEPTEMBER 7, 2008

In a startup, both the problem and solution are unknown, and the key to success is building an integrated team that includes product development in the feedback loop with customers. 2008 09 06 Eric Ries Haas Columbia Customer Development Engineering View SlideShare presentation or Upload your own.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

OCTOBER 4, 2008

Lessons Learned by Eric Ries Saturday, October 4, 2008 About the author ( Update January, 2010: This post originally dates from October, 2008 back when I first started writing this blog. I hope you take something of value from this blog. Eric, love the blog. Thanks for your professional blog. So thats me, your author.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

JULY 28, 2010

Lessons Learned by Eric Ries Wednesday, July 28, 2010 Case Study: kaChing, Anatomy of a Pivot (The following guest post is a new experiment for this blog. And if you’re a regular reader of this blog, you may know that IMVU started out as an instant messaging add-on. kaChing has been very active in the Lean Startup movement.

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

Startup Lessons Learned

MAY 31, 2010

Sean Murphy has an excellent and comprehensive roundup of resources about the conference: all of the slides, videos, summaries, notes and write-ups are listed on his blog here. You can read the rest of his posts on his blog : Introduction , Part 1 , Part 2.) All video from the conference is available for free at Justin.tv

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Startup Lessons Learned

OCTOBER 5, 2008

But first I think we need to save the product manager from that special form of torture only a waterfall product development team can create. Labels: product development 8comments: Vincent van Wylick said. Ive written about it on our development blog at [link] October 6, 2008 3:34 PM Chris Hondl said.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

JANUARY 12, 2010

Beyond my own efforts on this blog ( and more ), there is now an amazing variety of resources for lean startup practitioners. Rich also organized the first Lean Startup Meetup right here in San Francisco. And Steve Blank (a long-time mentor) has made the leap to blogging in impressive fashion. Please share in a comment.

Lean 146

Lean San Francisco Wiki Startup 146

Startup Lessons Learned

MARCH 16, 2009

Lessons Learned by Eric Ries Monday, March 16, 2009 Combining agile development with customer development Today I read an excellent blog post that I just had to share. In most agile development systems, there is a notion of the "product backlog" a prioritized list of what software is most valuable to be developed next.

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

JUNE 2, 2010

blog comments powered by Disqus Newer Post Older Post Home Subscribe via email Blog Archive ▼ 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) April 23, 2010 in San Francisco. Amazon PostRank

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Startup Lessons Learned

FEBRUARY 20, 2009

Luckily, I now have the benefit of a forthcoming book, The Principles of Product Development Flow. Labels: five whys root cause analysis , product development 11comments: Peter Severin said. Startup Lessons Learned season one : Every post from the blogs first year in print form. April 23, 2010 in San Francisco.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

SEPTEMBER 2, 2008

Thoughts on scientific product development Lo, my 5 subscribers, who are you? Get in touch: Twitter Email Facebook Linkedin Additional resources Startup LessonsLearned, All Seasons : Every post from the blog, in one 600+ page PDF. Startup Lessons Learned season one : Every post from the blogs first year in print form.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

SEPTEMBER 30, 2008

Own the development methodology - in a traditional product development setup, the VP Engineering or some other full-time manager would be responsible for making sure the engineers wrote adequate specs, interfaced well with QA, and also run the scheduling "trains" for releases. Labels: product development 15comments: mukund said.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

NOVEMBER 7, 2008

This is one of the blog we posted about how some company is doing SEO to promote the website. To help find the right keywords, Ive written an article on my blog Web Startup Help that details How to Do Keyword Research for startups. This post has been removed by a blog administrator. What is customer development?

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

JANUARY 7, 2010

Although much of it will sound familiar to readers of this blog, whats new is my first step towards the " new entrepreneurship " that is my goal for 2010. Unlike previous cross-posting Ive done for blogs, where a lot of the discussion happens here, Id like to ask you to take a minute and click through to read the full article.

San Francisco 119

San Francisco Management Continuous Deployment Lean 119

Startup Lessons Learned

AUGUST 2, 2008

0comments: Post a Comment Newer Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) April 23, 2010 in San Francisco.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

JULY 5, 2010

Instead of that naive approach, I wish Id had a book like this one, to help me figure out how to get started with customer development step-by-step. Instead of that naive approach, I wish Id had a book like this one, to help me figure out how to get started with customer development step-by-step. April 23, 2010 in San Francisco.

Customer Development 166

Customer Development Developer San Francisco Customer 166

Startup Lessons Learned

SEPTEMBER 2, 2008

Its inspired by the classic OODA Loop and is really just a simplified version of that concept, applied specifically to creating a software product development team. There are three stages: We start with ideas about what our product could be. Thoughts on scientific product development Lo, my 5 subscribers, who are you?

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

SEPTEMBER 12, 2008

0comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) April 23, 2010 in San Francisco.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

NOVEMBER 8, 2008

Customer development is a parallel process to product development, which means that you dont have to give up on your dream. Our goal in product development is to find the minimum feature set required to get early customers. A book I am looking forward to read after reading you blog. This is a common mistake.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

SEPTEMBER 10, 2008

I am convinced one of Joel Spolskys lasting contributions to the field of managing software teams will turn out to be the Joel Test , a checklist of 12 essential practices that you could use to rate the effectiveness of a software product development team. Thoughts on scientific product development Lo, my 5 subscribers, who are you?

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Steve Blank

FEBRUARY 23, 2009

This product development diagram had become part of the DNA of Silicon Valley. I was glad to find your blog and look forward to reading it. That’s in stark contrast to the traditional Product Development Model where it’s expected a customer is already there and waiting and it’s simply a matter of [.]

Product Development 143

Product Development Developer Silicon Valley Product 143

Startup Lessons Learned

NOVEMBER 4, 2008

Eric, Any thoughts on how forum feedback fits into customer development and agile product development? Youve probably addressed this in the past, but I continue to be blown away by how fast Blizzard reacts to noise in their forums and rapidly makes fixes to the product. What is customer development?

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

FEBRUARY 9, 2009

The Lean Startup: a Disciplined Approach to Imagining, Designing, and Building New Products.: Expo San Francisco 2009 The current macroeconomic climate presents unparalleled opportunities for those that can thrive with constrained resources. Startup Lessons Learned season one : Every post from the blogs first year in print form.

Lean 68

Lean San Francisco Web Advisory Board 68

Startup Lessons Learned

AUGUST 26, 2009

As a result, for a lot of these companies, Boulder is just a gateway to San Francisco. Get in touch: Twitter Email Facebook Linkedin Additional resources Startup LessonsLearned, All Seasons : Every post from the blog, in one 600+ page PDF. Startup Lessons Learned season one : Every post from the blogs first year in print form.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

SEPTEMBER 15, 2008

This gets me into trouble, because it conjures up for some the idea that product development is simply a rote mechanical exercise of linear optimization. You just constantly test little micro-changes and follow a hill-climbing algorithm to build your product. April 23, 2010 in San Francisco.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

JULY 6, 2009

I worry sometimes about making this blog too much into a travelogue or journal of my public events. wow this blog is god awful. Get in touch: Twitter Email Facebook Linkedin Additional resources Startup LessonsLearned, All Seasons : Every post from the blog, in one 600+ page PDF. April 23, 2010 in San Francisco.

Lean 115

Lean Video San Francisco Continuous Deployment 115

Startup Lessons Learned

SEPTEMBER 10, 2008

Labels: Test-driven development 0comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?)

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

JULY 9, 2010

blog comments powered by Disqus Newer Post Older Post Home Subscribe via email Blog Archive ▼ 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) April 23, 2010 in San Francisco. Amazon PostRank

San Francisco 161

San Francisco Management Founder Lean 161

Startup Lessons Learned

JULY 30, 2009

Brad Feld also had some thoughts on this event on his blog. Get in touch: Twitter Email Facebook Linkedin Additional resources Startup LessonsLearned, All Seasons : Every post from the blog, in one 600+ page PDF. Startup Lessons Learned season one : Every post from the blogs first year in print form.

Lean 68

Lean San Francisco Continuous Deployment DC 68

The Next Web

DECEMBER 2, 2013

The San Francisco-based company made do with $50 million to build its product from scratch to current iteration. To build a replica of the e-commerce platform Shopify , Mathews estimates it would cost between $250,000 and $300,000 with highly-skilled designers, developers and product people. 7) Shopify.

Cost 168

Cost San Francisco New York City Ruby 168

Startup Lessons Learned

SEPTEMBER 14, 2008

As Seth writes this week in Seths Blog: Listening to the loud people , the most aggressive customers arent necessarily the ones you want to hear from. Thanks Eric, your blog has many golden nuggets!!! Thoughts on scientific product development Lo, my 5 subscribers, who are you? April 23, 2010 in San Francisco.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Startup Lessons Learned

DECEMBER 23, 2009

blog comments powered by Disqus Newer Post Older Post Home Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) April 23, 2010 in San Francisco. Amazon PostRank

Metrics 167

Metrics San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

NOVEMBER 17, 2008

Strategy - startups first encounter this when they have the beginnings of a product, and theyve achieved some amount of product/market fit. What is customer development? Stevey's Blog Rants: Good Agile, Bad Agile Learning from Obama: maneuver warfare on the campa. April 23, 2010 in San Francisco.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

APRIL 14, 2009

Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. Their product development team is hard at work on a next-generation product platform, which is designed to offer a new suite of products – but this effort is months behind schedule.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

JANUARY 15, 2010

Two Ways to Hold Entrepreneurs Accountable blog comments powered by Disqus Newer Post Older Post Home Subscribe via email Blog Archive ▼ 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Read the rest here.

Hockey Stick 105

Hockey Stick San Francisco Entrepreneur Lean 105

Startup Lessons Learned

AUGUST 30, 2008

This basic pattern is useful in all aspects of product development. Get in touch: Twitter Email Facebook Linkedin Additional resources Startup LessonsLearned, All Seasons : Every post from the blog, in one 600+ page PDF. Startup Lessons Learned season one : Every post from the blogs first year in print form.

Software Review 74

Software Review San Francisco Design Continuous Deployment 74

Startup Lessons Learned

JULY 29, 2009

Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage. The biggest source of waste in new product development is building something that nobody wants. Leverage product development with open source and third parties.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

AUGUST 8, 2009

The economics of these process trade-offs are discussed in the Principles of Product Development Flow.) Heres an excerpt: In a previous article, we called Toyota’s product development system the “second Toyota paradox.&# Labels: product development 5comments: new york web development company said.

Software Review 87

Software Review Design Software San Francisco 87