Startup Lessons Learned

JANUARY 12, 2010

For the many entrepreneurs that send me cold emails asking for me to review a business plan or answer a strategic dilemma: Im much more likely to answer if youve already tried getting an answer on the mailing list. Last, Ive tried to keep this blog updated with events , slides , audio , video and books that are helpful as well.

Lean 146

Lean San Francisco Wiki Startup 146

Startup Lessons Learned

SEPTEMBER 15, 2008

I am heavily indebted to earlier theorists, and highly recommend the books Lean Thinking and Lean Software Development. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Good stuff.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

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. I highly recommend this book for all entrepreneurs, in startups as well as in big companies. This is a self-published book, originally designed as a companion to Steves class at Berkeleys Haas school of business.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

OCTOBER 4, 2008

He is the co-author of several books including The Black Art of Java Game Programming (Waite Group Press, 1996). Although Catalyst folded with the dot-com crash, Ries continued his entrepreneurial career as a Senior Software Engineer at There.com, leading efforts in agile software development and user-generated content.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

SEPTEMBER 10, 2008

But if you want to practice rapid deployment, you need to be able to deploy that build in one step as well. If you want to do continuous deployment, youd better be able to certify that build too, which brings us to. For more on continuous deployment, see Just-in-time Scalability. Can you make a build in one step?

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

JANUARY 2, 2010

Do you have a suggestion for a guest speaker or case study that illustrates a particular lean startup concept: minimum viable product, continuous deployment, validated learning, the pivot? Writing a book. Im just starting the publishing process that should lead to a book for a general business audience in 2011.

San Francisco 122

San Francisco Lean Continuous Deployment DC 122

Startup Lessons Learned

NOVEMBER 4, 2008

The best resources there are his book Extreme Programming Explained: Embrace Change and the gentle introduction at extremeprogramming.org. For customer development, start with Steves book The Four Steps to the Epiphany or take a look at his recent Entrepreneurial Thought Leader Lecture. Want to learn more about me?

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

FEBRUARY 22, 2009

I'd be interested to hear your opinion of a book we published earlier this year: "Hello World! " The book teaches kids programming with examples written in Python, and is illustrated with fun kid-friendly characters. Case Study: Continuous deployment makes releases n. Can I send you a review copy?

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

SEPTEMBER 5, 2008

Id also recommend Cal Hendersons (flickr) presentations (and book), e.g. [link] And - of course - going through [link] and reading up on the various different approaches different companies have (successfully) taken towards getting scalability at reasonably low cost. Case Study: Continuous deployment makes releases n.

Open Source 107

Open Source San Francisco Continuous Deployment Lean 107

Startup Lessons Learned

MAY 31, 2010

In the meantime his two books, The Monk and the Riddle and Getting to Plan B are both a must-read. In the meantime his two books, The Monk and the Riddle and Getting to Plan B are both a must-read. Case Study: Continuous deployment makes releases n. There are so many more people to thank: Sarah Milstein and the Web 2.0

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Startup Lessons Learned

JANUARY 30, 2009

A much less painful way to learn the lesson is read his book: The Four Steps to the Epiphany. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Once again, a fantastic post.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Startup Lessons Learned

APRIL 9, 2009

Well be discussing in greater detail the three techniques I highlighted at the Expo: continuous deployment, split-testing, and five whys. How to Build a Lean Startup, step-by-step Get started with a detailed guide to three key lean startup techniques: continuous deployment, rapid split-testing, and root cause analysis (five whys).

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

Startup Lessons Learned

MARCH 16, 2009

I wont do the explanation justice so I suggest you grab the book. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

AUGUST 24, 2009

I place them roughly in this order: Movies > Television > Books > Music > Magazines > Radio > Newspapers Each industry is watching the one in front of it sink into the quicksand. When I reviewed a recent product development book, it immediately shot up to Amazon sales rank 300. My blog has over 14000 subscribers, for example.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

JANUARY 19, 2009

One, which is described in great detail in the Mythical Man-Month (in finding that link, I discovered that today is coincidentally the exact 11th anniversary of my first purchasing that book: Jan 19, 1998), is that as you add people to a team or project, there is an increase in communications overhead that makes everyone slightly less productive.

Lean 140

Lean Hiring San Francisco Continuous Deployment 140

Startup Lessons Learned

MARCH 27, 2009

In fact, every single lean transformation documented in books like Lean Thinking took place in the midst of serious external threats. PayPal was fortunate to make several BIG leaps & changes in their models, one of which eventually resulted in runaway success (email & web e-commerce payments, primarily on the eBay marketplace).

San Francisco 117

San Francisco Lean Continuous Deployment DC 117

Startup Lessons Learned

JUNE 5, 2009

Imagine a general manager that has read The Innovator’s Dilemma and related books, and is therefore trying hard to help her organization make a transition to a new product category via disruptive innovation. Case Study: Continuous deployment makes releases n. Pivot, don't jump to a new vision Why Continuous Deployment?

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Startup Lessons Learned

AUGUST 1, 2009

There are some good anecdotes about Chief Engineers in the Toyota Product Development Book. I'm reading "Inside Steve's Brain" book, and I highly reccommend to understand Jobs approach on launching new products. Case Study: Continuous deployment makes releases n. August 7, 2009 6:03 AM mrcavalcanti said.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

JUNE 9, 2009

Books like Crossing the Chasm are excellent, but they can be misleading. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Pivot, don't jump to a new vision Why Continuous Deployment?

Lean 60

Lean San Francisco Japan Continuous Deployment 60

Startup Lessons Learned

SEPTEMBER 29, 2008

Lessons Learned by Eric Ries Monday, September 29, 2008 Q&A with an actual reader One of my favorite things about having a blog is the feedback I get in comments and by email. Thanks again and if you have any other suggestions or books that I should read, I would be forever in your debt. Very exciting. Want to learn more about me?

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

Startup Lessons Learned

SEPTEMBER 18, 2008

If you have a minute, post your answers in a comment, or email me. Heard about O'Reilly video from "So you want to be an entrepreneur" blog 3)I subscribed in spite of the fact that I just pruned my email , twitter and Google reader feeds down to the bone. Case Study: Continuous deployment makes releases n.

San Francisco 133

San Francisco Lean Continuous Deployment DC 133

Startup Lessons Learned

JULY 2, 2009

Have you considered putting all these into a book? oh, and on the book front, you'll be able to get all of my essays so far in ebook, print-on-demand, and kindle editions - coming soon. Case Study: Continuous deployment makes releases n. Great article as always, Eric. They seem to be liking it. (oh,

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

OCTOBER 6, 2008

One time, I became completely enamored with Influence: The Psychology of Persuasion (which is a great book, but thats for another post). I thought that this was a great post, and Ive quoted it extensively to folks via email. Case Study: Continuous deployment makes releases n. Any thoughts? Want to learn more about me?

San Francisco 128

San Francisco Lean Continuous Deployment Agile 128

Startup Lessons Learned

DECEMBER 30, 2008

I have found James Surowiecki s book The Wisdom of Crowds particularly helpful in thinking through these issues. This book is Tipping Point - esque , full of anecdotes and interesting social science citations. Let me briefly summarize the part of the book I find most helpful (leaving a few out, which arent germane to todays topic).

San Francisco 83

San Francisco Lean Continuous Deployment DC 83

Startup Lessons Learned

APRIL 14, 2009

You really should read Steves book: [link] The short version is, you need to build up an in-depth mental model of a prospective customer. Eric, I have Steves book and wish I had it for 1 couple of my earlier startups where the framework would have helped our team get on the same page. Case Study: Continuous deployment makes releases n.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

OCTOBER 20, 2008

TWO See page 199 of Poppendieck and Poppendiecks new(er) book for a finer analysis of defects and bugs: Unit tests prove that the code does what the developers want it to do, i.e. there are no defects. Although I havent read Crosbys book and I dont doubt the veracity of his insights, I think the problem is far more complex these days.

Software Review 164

Software Review Engineer Management Technical Review 164

Feld Thoughts

JANUARY 16, 2013

I guess that’s part of the motivation I have in writing Startup Boards: Reinventing the Board of Directors to Be Useful to the Entrepreneur (the next book in the Startup Revolution series which should be out sometime this summer.). Or fighting through 19 attachments to an email to figure out where the actual board material was.

Continuous Deployment 166

Continuous Deployment Distribution Lean Email 166

Startup Lessons Learned

MARCH 13, 2009

If so, I might have something that can help with more of a grass roots effort1 Or email me at rush1527@yahoo.com March 14, 2009 11:25 AM Maria Marsala, EduCoach said. Im converted - ordered Garys book as well. Case Study: Continuous deployment makes releases n. March 14, 2009 3:25 AM Anonymoussaid. Great article.

San Francisco 168

San Francisco PR Lean Early Stage 168

Startup Lessons Learned

MARCH 4, 2009

In particular, Ive focused on the two channels of communication that were most commonly suggested in the first survey: conferences and books. That Feedburner page lets you subscribe if you want to give your email address. Case Study: Continuous deployment makes releases n. March 7, 2009 3:31 PM Eric said. Great post.

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

Startup Lessons Learned

OCTOBER 5, 2010

We did our best to package as much content (including almsot a dozen books and ebooks) as well as tools and apps, into one low-priced magic offer. But I am even more excited to report that it will include a hardcover copy of my new Lean Startup book. But thats not all! And theres so much more.

Lean 153

Lean San Francisco Startup Continuous Deployment 153

Startup Lessons Learned

JANUARY 28, 2009

Back when it first came out, Fowlers book Refactoring was what got me into the Agile world, so it holds a special place in my heart. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

Startup Lessons Learned

MAY 20, 2010

Heres an excerpt: Philosophy Helps Start-Ups Move Faster - WSJ.com Silicon Valley entrepreneurs and venture capitalists often churn out how-to business books and fancy themselves as management gurus, but few see their methodologies adopted. Case Study: Continuous deployment makes releases n. Want to learn more about me?

Lean 153

Lean San Francisco Arlington Continuous Deployment 153

Startup Lessons Learned

NOVEMBER 5, 2008

I would love to talk to you about writing a book (and various other things.) Cant find an email on your site but please contact me: tim at (as you might expect) oreilly dot com November 23, 2008 10:00 AM Eric said. Case Study: Continuous deployment makes releases n. Thanks for the comments and kind words!

Campaign 84

Campaign San Francisco Lean Agile 84

www.subelsky.com

FEBRUARY 25, 2010

Heres a revised version of what I emailed in response, garnered while building OtherInbox and other Rails apps: First and foremost, I find Rails itself to be very useful for building a product for a lean startup; the expressiveness of Ruby and the conventions of Rails help developers more quickly build a minimum viable product.

Lean 41

Lean Baltimore Ruby Maryland 41

Startup Lessons Learned

MAY 3, 2009

This also gives me a chance to clarify that I am no relation to the author of the classic book on positioning , Al Ries ) Next up, heres the video from my talk with Steve Blank at startup2startup. Case Study: Continuous deployment makes releases n. Ive embedded the slides below the video feed. Want to learn more about me?

Video 104

Video San Francisco Continuous Deployment DC 104

Startup Lessons Learned

SEPTEMBER 9, 2009

If all that archive-browsing leaves you hungry for more, you will soon be able to get Startup Lessons Learned in book form. I think a book of all your most read posts would be amazing (much like Guy Kawasaki). Why Continuous Deployment? * Awesome, looking forward to the book. Let me summarize. Don't launch * 8.9

San Francisco 84

San Francisco Continuous Deployment Lean DC 84

Startup Lessons Learned

AUGUST 8, 2009

In particular, we would cover customer development, continuous deployment, minimum viable product, and actionable metrics. How many workshops, books, webinars, blog posts, etc have you read, said "that's awesome", and then never did anything beyond that. Case Study: Continuous deployment makes releases n.

Lean 102

Lean Programming San Francisco Continuous Deployment 102