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

MAY 9, 2012

TLDR: Brant Cooper and Patrick Vlaskovits , authors of The Entrepreneur's Guide to Customer Development are back with a new book called The Lean Entrepreneur. It took the idea of Customer Development and made it accessible to a whole new audience. Illustrations by FAKEGRIMLOCK. You can pre-order it starting today.

Entrepreneur 167

Entrepreneur Lean Southern California San Diego 167

Startup Lessons Learned

SEPTEMBER 30, 2008

I would love to see some blog posts on any experiences you have had with set-based design. My answer to that was to be part of the team whose whole is better that its individual parts as its mentioned in the article, a team leadership rather that a point leadership. Case Study: Continuous deployment makes releases n.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

AUGUST 1, 2009

Lessons Learned by Eric Ries Saturday, August 1, 2009 The Steve Jobs method Image via CrunchBase Its been a long time since I did a post that was primarily a link to another blog with commentary, but I came across something today that I really want to share. Plus, the premise of the question misunderstands the lean startup, too.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

SEPTEMBER 10, 2008

Is it too self-referential to post a blog entry about someone elses blog entry about how often to write a blog entry ? His post is ostensibly about how often to release new work (whether youre a blog writer, movie star, software team.) The leadership art is to balance the needs of the present with the needs of the future.

San Francisco 76

San Francisco Continuous Deployment Lean DC 76

Startup Lessons Learned

JANUARY 2, 2009

The major thesis will be no surprise to those of you whove been following this blog for a few months. Here in Tampa, our biggest challenge is convincing the regions technology "leadership" that grassroots economic development is a good thing. Case Study: Continuous deployment makes releases n. I am chugging along.

San Francisco 60

San Francisco Tampa Continuous Deployment Lean 60

Startup Lessons Learned

FEBRUARY 22, 2009

We also learned that law is code , and that leadership was needed to build thriving communities in a digital age. If you find it worthwhile, we'd appreciate a post on the blog to help us spread the word. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Expo (and a call for he.

Programming 143

Programming San Francisco Lean Continuous Deployment 143