Startup Lessons Learned

SEPTEMBER 15, 2008

The application of agile development methodologies which dramatically reduce waste and unlock creativity in product development. See Customer Development Engineering for my first stab at articulating the theory involved) Ferocious customer-centric rapid iteration, as exemplified by the Customer Development process.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Startup Lessons Learned

OCTOBER 5, 2008

They exchange countless emails, and hes being constantly interrupted and being asked to clarify exactly what the spec means. The fourth spec exists only in these emails, which are changing the design in an ad-hoc fashion. Labels: product development 8comments: Vincent van Wylick said. Want to learn more about me?

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

SEPTEMBER 22, 2008

Sometimes we have the attitude that the Product Development team is the one responsible for Activation and Retention (hey, a great product would do that naturally) or that the Marketing team is responsible for Revenue and Referral (hey, go get me some money or free customers already). Want to learn more about me?

San Francisco 167

San Francisco CPA SEM CTO Hire 167

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. Want to learn more about me? Try About the author. Trying to learn more about lean startups?

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

SEPTEMBER 12, 2008

You might get a bunch of inbound emails from other press and partners, and all of these things can contribute to a feeling that you’re on your way to getting tons of traffic. Thoughts on scientific product development Lo, my 5 subscribers, who are you? It strokes your ego. Want to learn more about me? Try About the author.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

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

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. The basic idea is to avoid building something based on what you think it might need to do in the future.

Software Review 74

Software Review San Francisco Design Continuous Deployment 74

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

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?) Speed up or slow down? Want to learn more about me?

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Startup Lessons Learned

MARCH 16, 2009

Ever since that time, I have struggled to explain how the feedback loop in customer development should interface with the feedback loop in product development. Eric Ries Lean Startup Schematic View Of Agile Development And Customer Development View more presentations from Eric Ries. Want to learn more about me?

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

JULY 6, 2009

If you have thoughts about the right balance of news, events, and commentary, feel free to leave it as a comment or drop me an email. Get in touch: Twitter Email Facebook Linkedin Additional resources Startup LessonsLearned, All Seasons : Every post from the blog, in one 600+ page PDF. As always, I welcome your feedback.

Lean 115

Lean Video San Francisco Continuous Deployment 115

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?) Want to learn more about me? Try About the author.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

SEPTEMBER 14, 2008

is something like "yes, I personally answer the customer support emails." For example, my experience with teenagers is that they are very reluctant to call or email asking for support, even when they have a severe problem. Thoughts on scientific product development Lo, my 5 subscribers, who are you? Try About the author.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Startup Lessons Learned

SEPTEMBER 5, 2008

October 13, 2008 9:44 PM 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?) Want to learn more about me?

Open Source 107

Open Source San Francisco Continuous Deployment Lean 107

Startup Lessons Learned

FEBRUARY 28, 2009

None of it would have happened if we had plenty of cash, or were content to count our progress by traffic or product development milestones. Labels: product development 4comments: Doug said. Everything else, including anything that optimizes any other goal, is waste. Thank you Eric. March 2, 2009 1:58 PM programiTV said.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

JANUARY 30, 2009

Without conscious process design, product development teams turn lines of code written into momentum in a certain direction. This is why agility is such a prized quality in product development. As far as I know, there are no products that are immune from the technology life cycle adoption curve.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Startup Lessons Learned

JULY 30, 2009

Congrats Eric.this is really awesome July 30, 2009 5:13 PM 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?)

Lean 68

Lean San Francisco Continuous Deployment DC 68

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

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. Youll probably get a better result, anyway. Youll probably get a better result, anyway. Want to learn more about me?

Lean 146

Lean San Francisco Wiki Startup 146

Startup Lessons Learned

FEBRUARY 10, 2009

This development philosophy created a culture around rapid prototyping of features, followed by testing them against large numbers of actual customers. It would be hard to argue against this product development strategy, in general. I am not a developer. If a feature worked, wed keep it. If it didnt, wed trash it.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

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

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. Its really helped me articulate my thinking on this topic, and includes an entire chapter on the topic of reducing batch size.)

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

SEPTEMBER 13, 2008

There is much work that I need to do (the only developer so far) before we have something customers can use. Thoughts on scientific product development Lo, my 5 subscribers, who are you? How to get distribution advantage on the iPhone How to Usability Test your Site for Free The one line split-test, or how to A/B all the tim.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

SEPTEMBER 27, 2010

One of the sayings I hear from talented managers in product development is, “good enough never is.&# And, most importantly, it helps team members develop the courage to stand up for these values in stressful situations. Lessons Learned by Eric Ries Monday, September 27, 2010 Good enough never is (or is it?)

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

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. =) November 4, 2008 10:58 PM IMVU said.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

JANUARY 7, 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?) Read the rest at The Conversation - Harvard Business Review.

San Francisco 119

San Francisco Management Continuous Deployment Lean 119

Startup Lessons Learned

SEPTEMBER 2, 2008

Labels: continuous deployment 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?)

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

NOVEMBER 7, 2008

Finally the day came, we unleashed the landing page, emailed our existing customers, and started advertising online. Depending on the type of product, postings on forums, classifieds and emails could give enough information to help gauge potential response. We finally settled on a $1.99 November 8, 2008 8:44 AM OneDish said.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

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. I think Drucker said it best. Any thoughts?

San Francisco 128

San Francisco Lean Continuous Deployment Agile 128

Startup Lessons Learned

JUNE 8, 2009

I had it all set up to a jury-rigged SurveyMonkey - PayPal minimum viable product. Whenever someone decided to buy a ticket, I got an email immediately letting me know. Yet, when I tried other forms of promotion, I’d have to accept their failures when the emails failed to come. Yet it had one huge advantage.

San Francisco 84

San Francisco Lean Continuous Deployment DC 84

Startup Lessons Learned

NOVEMBER 6, 2008

Get in touch: Twitter Email Facebook Linkedin Additional resources Startup LessonsLearned, All Seasons : Every post from the blog, in one 600+ page PDF. Want to learn more about me? Try About the author. Trying to learn more about lean startups? See Four Myths about the Lean Startup or The lean startup.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

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

FEBRUARY 9, 2009

If youd like to give feedback, feel free to post comments here, or get in touch on LinkedIn , Facebook , or try to beat the spam filter on email. Get in touch: Twitter Email Facebook Linkedin Additional resources Startup LessonsLearned, All Seasons : Every post from the blog, in one 600+ page PDF. Check out what I am doing at.

Lean 68

Lean San Francisco Web Advisory Board 68

Startup Lessons Learned

OCTOBER 4, 2008

Please email me if you are interested. Get in touch: Twitter Email Facebook Linkedin Additional resources Startup LessonsLearned, All Seasons : Every post from the blog, in one 600+ page PDF. I help lead the Engineering Leadership SIG at SDForum and wonder if you would be interested in speaking to our group about lean starups.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

SEPTEMBER 1, 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?)

San Francisco 68

San Francisco Developer Continuous Deployment DC 68

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. Get in touch: Twitter Email Facebook Linkedin Additional resources Startup LessonsLearned, All Seasons : Every post from the blog, in one 600+ page PDF. Want to learn more about me?

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

OCTOBER 20, 2008

Lessons Learned by Eric Ries Monday, October 20, 2008 The engineering managers lament I was inspired to write The product managers lament while meeting with a startup struggling to figure out what had gone wrong with their product development process. Good luck, engineering manager. It was painful for a lot of people.

Software Review 164

Software Review Engineer Management Technical Review 164