Startup Lessons Learned

JULY 30, 2009

Lessons Learned by Eric Ries Thursday, July 30, 2009 Techstars brings The Lean Startup to Boulder Im very excited to announce a pair of events that will kick off a very busy fall speaking tour. The event will include a talk from Eric on The Lean Startup over dinner, followed by moderated table discussion and then final Q&A with Eric.

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

MAY 7, 2009

I spent some time with his company before the conference and discussed ways to get started with continuous deployment , including my experience introducing it at IMVU. Moreover, approaching the problem from the direction that I had intuitively is a recipe for never reaching a point where continuous deployment is feasible.

San Francisco 131

San Francisco Continuous Deployment Software Review Lean 131

Startup Lessons Learned

MARCH 25, 2010

(for Harvard Business Review) Over at Harvard Business Review, Ive been building up a series designed to introduce the Lean Startup methodology to a business-focused audience. Read the rest of The Startups Rules of Speed - The Conversation - Harvard Business Review. The Lean Startup Intensive is tomorrow at Web 2.0.

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

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. The product manager was clearly struggling to get results from the rest of the team. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

NOVEMBER 7, 2008

It was one of those brilliant startup brainstorms that comes to the team in a flash, with a giant thunderclap. Eric, Excellent article about an essential technique for startups. 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.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

MAY 31, 2010

Expo Intensive rocked, the mainstream media has started writing about the Lean Startup, and - most of all - the movement continues to grow and evolve. First of all, the Startup Lessons Learned conference exceeded my wildest expectations. You can read the rest of his posts on his blog : Introduction , Part 1 , Part 2.)

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Startup Lessons Learned

AUGUST 2, 2008

Lessons Learned by Eric Ries Saturday, August 2, 2008 Paul Graham on fundraising I have found no better primer on the current realities of starting a new technology company in a startup hub like Silicon Valley than Paul Grahams essays. but rest assured they would be. How to Fund a Startup [link] Its obvious why investors delay.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

JANUARY 7, 2010

As an entrepreneur, I often saw the best practices of general management fail startups. My most recent startup created a marketplace for customers to buy and sell virtual goods for their 3D avatar. Read the rest at The Conversation - Harvard Business Review. Read the rest at The Conversation - Harvard Business Review.

San Francisco 119

San Francisco Management Continuous Deployment Lean 119

Startup Lessons Learned

OCTOBER 4, 2008

So if youre new, consider not paying any attention to the rest of this post, and just diving into the archives, if you havent already. Maybe youd like to start with The lean startup , How to listen to customers , or What does a startup CTO actually do? ) He previously co-founded and served as Chief Technology Officer of IMVU.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

SEPTEMBER 27, 2010

And the rest is history: Google Maps was a huge success. Yet startups rely on collective learning in order to find their way. I believe this is one reason why the myth of the dictatorial startup founder has such enduring appeal. In fact, in all of the startups I have worked with, I have never seen this happen. Ship it.&#

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

JULY 5, 2010

I have personally sold many copies of his book, and continue to recommend it as one of the most important books a startup founder can read. You can easily take from it whatever makes sense for your business, and leave the rest. Four Steps primarily centers its stories and case studies on B2B hardware and software startups.

Customer Development 166

Customer Development Developer San Francisco Customer 166

Startup Lessons Learned

NOVEMBER 8, 2008

This theory has become so influential that I have called it one of the three pillars of the lean startup - every bit as important as the changes in technology or the advent of agile development. I highly recommend this book for all entrepreneurs, in startups as well as in big companies. Heres the catch. Theory of market types.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

NOVEMBER 17, 2008

Lessons Learned by Eric Ries Monday, November 17, 2008 The four kinds of work, and how to get them done: part one Ive written before about some of the advantages startups have when they are very small, like the benefits of having a pathetically small number of customers. A "startup within the startup" feeling is a good thing.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

JANUARY 15, 2010

Read the rest here. Read the rest here. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R. The Lean Startup Intensive is tomorrow at Web 2.0. Startup Lessons Learned - the Conference (April 23.

Hockey Stick 105

Hockey Stick San Francisco Entrepreneur Lean 105

Startup Lessons Learned

JANUARY 2, 2010

Lessons Learned by Eric Ries Saturday, January 2, 2010 Towards a new entrepreneurship When I started writing about the lean startup , my aspiration was to do more than just share a handful of tips and tricks that work for consumer internet startups. This belief led me to the lean startup, and to an amazing 2009.

San Francisco 122

San Francisco Lean Continuous Deployment DC 122

Startup Lessons Learned

AUGUST 1, 2009

One of the most common questions I get about the lean startup methodology is, "but what about Steve Jobs ?" So how do you reconcile his success with the lean startup, which seems to suggest the opposite?" Plus, the premise of the question misunderstands the lean startup, too. And he doesnt shy away from big-bang launch events.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

FEBRUARY 22, 2009

The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R. The Lean Startup Intensive is tomorrow at Web 2.0. The new startup arms race (for Huffington Post) For Startups, How Much Process Is Too Much? Expo SF (May.

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

JANUARY 2, 2009

For the rest of us, there is an alternative: to create credibility by building a lean startup. Rather than just focus on the right kind of pitch to use, I wanted to write about the kinds of startups that create lasting value, and therefore are great companies to fund even in down times. Is there s choice? Expo SF (May. .

San Francisco 60

San Francisco Tampa Continuous Deployment Lean 60

Startup Lessons Learned

OCTOBER 6, 2008

Lessons Learned by Eric Ries Monday, October 6, 2008 When NOT to listen to your users; when NOT to rely on split-tests There are three legs to the lean startup concept: agile product development , low-cost (fast to market) platforms , and rapid-iteration customer development. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 128

San Francisco Lean Continuous Deployment Agile 128

Startup Lessons Learned

OCTOBER 11, 2009

This team had been working for many months in a standard agile configuration: a disciplined engineering team taking direction from a product owner who would prioritize the features they should work on. Whatever learning took place was happening by the product owner; the rest of the team was just heads-down implementing features.

San Francisco 133

San Francisco Lean Metrics Continuous Deployment 133

Startup Lessons Learned

AUGUST 24, 2009

In other words, they are facing conditions of extreme uncertainty, just like startups. But, as any startup can tell you, this opens up a tremendous set of opportunities for the rest of us. Just like with startups, this is a hybrid question. So I generally feel right at home in these conversations.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

MARCH 13, 2009

Lessons Learned by Eric Ries Friday, March 13, 2009 Dont launch Heres a common question I get from startups, especially in the early stages: when should we launch? In fact, in most situations its a bad idea for startups to synchronize these events. Most startups arent so fortunate. My answer is almost always the same: dont.

San Francisco 168

San Francisco PR Lean Early Stage 168

Startup Lessons Learned

SEPTEMBER 10, 2008

Heres my favorite part: If youve got a team, part of the team should obsess about the backlist, honing it, editing it and promoting it, while the rest work to generate (as opposed to promote) the frontlist. I see startups struggle with this all the time. No departments The Five Whys for Startups (for Harvard Business R.

San Francisco 76

San Francisco Continuous Deployment Lean DC 76

Startup Lessons Learned

JANUARY 28, 2009

Its an essential discipline of good software development, especially in startups. Nonetheless, I want to talk about a dysfunction Ive seen in several startups: they are literally refactoring themselves to death. Labels: agile , product development , Test-driven development 11comments: William Pietri said. Practice five whys.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

Startup Lessons Learned

MARCH 4, 2009

Thanks to those of you who were willing to fill out the survey, I learned my net promoter score (about 25) as well as some clear other segmentation insights: about 80% of you are founders of or work at a startup, you read many of the same other blogs, and many of you would like to engage with Lessons Learned in formats and venues beyond this blog.

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

Startup Lessons Learned

MARCH 11, 2010

Lessons Learned by Eric Ries Thursday, March 11, 2010 For Startups, How Much Process Is Too Much? for Harvard Business Review) In the latest article for my series in HBR, I discuss the problem of how to figure out how much process startups should have. When done right, it can help startups accelerate even as they scale.

San Francisco 120

San Francisco Continuous Deployment Lean DC 120

Startup Lessons Learned

DECEMBER 30, 2008

When doing the post-interview team meeting, it was common for the first opinion expressed about a candidate to become the prevailing opinion of the rest of the team members. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R.

San Francisco 83

San Francisco Lean Continuous Deployment DC 83

Startup Lessons Learned

APRIL 12, 2010

Lessons Learned by Eric Ries Monday, April 12, 2010 The Lean Startup Intensive at Web 2.0 So I am particularly excited that the Lean Startup is a big part of this years Web 2.0 And for those who want more than just the overview, were offering the Lean Startup Intensive on the first day of the conference: May 3, 2010.

Lean 129

Lean San Francisco Web Continuous Deployment 129

Startup Lessons Learned

OCTOBER 11, 2008

And what do you do with the rest? The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R. The Lean Startup Intensive is tomorrow at Web 2.0. Startup Lessons Learned - the Conference (April 23. Expo SF (May. .

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

Startup Lessons Learned

SEPTEMBER 19, 2009

Lessons Learned by Eric Ries Saturday, September 19, 2009 Support the Startup Founders Visa with a tweet Its been an exhilarating first day here in Washington DC for the Geeks on a Plane tour. We can remedy it by creating a special visa for startup founders. Its actually part of a lean startup story. Will you join us?

San Francisco 150

San Francisco Founder DC Washington 150

Startup Lessons Learned

MARCH 23, 2009

Read the rest of the interview at Venture Hacks. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R. The Lean Startup Intensive is tomorrow at Web 2.0. Startup Lessons Learned - the Conference (April 23.

San Francisco 167

San Francisco Lean Continuous Deployment Audio 167

Startup Lessons Learned

NOVEMBER 12, 2009

Lessons Learned by Eric Ries Thursday, November 12, 2009 New York: three straight days of Lean Startup (two of which are free) Greetings from Europe, where Im just wrapping up an incredible (and exhausting) speaking tour. Thanks to web2open , there are two Lean Startup sessions that are completely free and open to the public.

New York 94

New York Lean San Francisco Continuous Deployment 94

Startup Lessons Learned

FEBRUARY 8, 2010

Read the rest of Entrepreneurs: Beware of Vanity Metrics at The Conversation on Harvard Business Review. Read the rest of Entrepreneurs: Beware of Vanity Metrics at The Conversation on Harvard Business Review. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Expo SF (May. .

Metrics 121

Metrics San Francisco Lean Continuous Deployment 121

usersknow.blogspot.com

APRIL 30, 2010

Is this feature usable, and is the UX reasonably consistent with the rest of my product? It doesn’t fit in with the rest of your offering. Come hear me speak at the Startup Lessons Learned conference in San Francisco on April 23rd. Do I have a marketing plan for letting users know this exists? Like this post?

Software Review 40

Software Review Agile San Francisco Advisory Board 40

Startup Lessons Learned

SEPTEMBER 3, 2009

If you look at the typical startup, you will see the vast majority of their energy and time invested in building new technology. We act as if the biggest risk to startup success is that the technology won’t work. Read the rest (and be sure to watch the videos). The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 104

San Francisco DC Continuous Deployment Lean 104

Startup Lessons Learned

MAY 17, 2009

Lessons Learned by Eric Ries Sunday, May 17, 2009 Last chance to register for The Lean Startup at HP on May 21 This coming Thursday, May 21, is the last time Im currently scheduled to give the full Lean Startup presentation in the Bay Area. What about the rest of us? Many startups are now following the Lean Startup process.

Lean 60

Lean San Francisco Continuous Deployment DC 60

Startup Lessons Learned

MARCH 20, 2009

Lessons Learned by Eric Ries Friday, March 20, 2009 How to build companies that matter (the lean startup on OReilly Radar) I have a post up today on OReilly Radar about using lean startup principles to build companies that matter. Read the rest. We Canadian startups can use all the help we can get!

Lean 68

Lean San Francisco Continuous Deployment DC 68