Startup Lessons Learned

JANUARY 19, 2009

I want to talk specifics, and when you come right down to it, most technology startups dont have a very interesting cost structure. This is another sub-optimization caused by incentivizing the wrong metric. Heres my suggestion: dont hire for any job unless you have tried, and failed, to do it yourself.

Lean 140

Lean Hiring San Francisco Continuous Deployment 140

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? My answer is almost always the same: dont. In fact, in most situations its a bad idea for startups to synchronize these events. But dont be too sure.

San Francisco 168

San Francisco PR Lean Early Stage 168

Startup Lessons Learned

MARCH 3, 2009

Without entering into that theoretical domain, in this post Id like to try and offer a specific and concrete suggestion for how to build a culture of learning into a startup. When I was a manager, I was once leading a cycle post-mortem. The suggestion is that you implement one single company-wide rule. But its not. Whats that you say?

Employee 146

Employee San Francisco Lean Software Review 146

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. My normal answer is that I dont really think thats how Apple products are built.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

DECEMBER 30, 2008

A few commenters have taken issue with the idea that its solely the hiring managers responsibility to assess fit, arguing correctly that the whole team should participate in the evaluation and decision. Still, I do think fit is a quality that requires special treatment, because it is the hardest attribute to evaluate.

San Francisco 83

San Francisco Lean Continuous Deployment DC 83

Startup Lessons Learned

MAY 7, 2009

To illustrate this point, I want to excerpt a large part of a recent blog post by Owen Rogers, who organized my recent trip to Vancouver. Users should only see new functionality once it is ready, fully implemented and thoroughly tested, lest they get a bad impression of the product that could adversely affect the company’s brand.

Continuous Deployment 131

Continuous Deployment San Francisco Software Review Lean 131

blog.expensify.com

APRIL 24, 2012

Monday edit : Skip my post and read this one instead. None of this makes you a “bad programmer” All these differences are perfectly irrelevant if you just want to make 1.6 Learn more… Saturday edit: Wow, quite a response to this. Some additional comments at the end. Sunday edit : Still going! All it takes is time.

Java 107

Java PHP Software Review Coder 107