Startup Lessons Learned

AUGUST 8, 2009

I thought a good place to start was with the origins of the idea that "software design" should be considered a discipline in its own right, on par with computer science, software engineering, and computer programming. Great engineers see it and smile. This is called set-based concurrent engineering (SBCE). [1]

Software Review 87

Software Review Design Software San Francisco 87

Startup Lessons Learned

SEPTEMBER 10, 2008

Lessons Learned by Eric Ries Wednesday, September 10, 2008 A new version of the Joel Test (draft) (This article is a draft - your comments are especially welcome as I think through these issues. At IMVU , our engineering team accumulated thousands upon thousands of tests, and we had a build cluster (using BuildBot ) that ran them.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

JANUARY 12, 2009

At IMVU, when wed hire a new engineer, we could get them to ship code to production on their first day, even if they had never programmed in PHP before. PHP can do what no other language or framework can (albeit django). and Rails as a web framework. In most cases, simple changes are simple to make. Enough about that.

PHP 166

PHP Software Review Ruby San Francisco 166

Startup Lessons Learned

AUGUST 1, 2009

The only efforts a new product team should be expending are those that lead to validated learning about customers. In the meantime, I hope some of you will find the lean startup a helpful framework. Beyond Apple, we can find examples of the Steve Jobs character at Toyota, in the form of the Chief Engineer.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

JANUARY 15, 2010

This whole framework breaks down when teams confront entrepreneurial situations in which theyre trying to build something new under conditions of extreme uncertainty. This whole framework breaks down when teams confront entrepreneurial situations in which theyre trying to build something new under conditions of extreme uncertainty.

Hockey Stick 105

Hockey Stick San Francisco Entrepreneur Lean 105

Startup Lessons Learned

APRIL 14, 2009

This is an incredible skill, one that most engineers overlook. For more on how this plays into the process of scaling up, see the Customer Creation stage of the customer development model.) But in the meantime, by iterating on their product with customers, they have a chance to get there on their own.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

MARCH 29, 2010

Tactics were discussed out of context, and there wasnt an overarching framework for figuring out what works for what kinds of companies, industries, and stages of growth. Tactics were discussed out of context, and there wasnt an overarching framework for figuring out what works for what kinds of companies, industries, and stages of growth.

San Francisco 120

San Francisco Lean Continuous Deployment DC 120

Startup Lessons Learned

MARCH 25, 2009

It will probably be the first time Ill be able to take extensive Q&A on some of the new frameworks Ill be debuting at Web 2.0 The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? As always, if you decide to attend, please come say hello. Want to learn more about me?

Agile 60

Agile Lean San Francisco Continuous Deployment 60

Startup Lessons Learned

OCTOBER 5, 2009

Imagine you hear from an engineer that they are worried that a certain payment subsystem is unreliable, and will therefore double-charge some customers. One way to evaluate this fear is to spend time on analysis: how many customers will be affected? How upset will those customers be? How upset will those customers be?

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 133

Startup Lessons Learned

SEPTEMBER 22, 2008

Lessons Learned by Eric Ries Monday, September 22, 2008 You dont need as many tools as you think Im always excited to see someone else writing about lessons learned from their startup, and wanted to link today to Untitled - Startup Lessons Learned -- Take it with a grain of salt. Seth Godin: How often should you publish?

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68

Startup Lessons Learned

APRIL 26, 2009

Although customers didnt flock to this offering at first, we had enough of a developer program active to start recruiting early adopters to start creating 3D objects for sale in our catalog. That engine of creativity has led to a catalog of something like 2 million virtual goods authored by a hundred thousand developers.

Product Development 88

Product Development Developer San Francisco Product 88

Startup Lessons Learned

MARCH 13, 2009

Do some Customer Development instead. You create an entire framework of understanding and action based on your product/idea that sets it in motion in a self-sustaining way. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Help you raise money. But dont be too sure.

San Francisco 168

San Francisco PR Lean Early Stage 168

Startup Lessons Learned

DECEMBER 7, 2008

Lessons Learned by Eric Ries Sunday, December 7, 2008 Getting started with split-testing One of the startup founders I work with asked me a smart question recently, and I thought Id share it. A few days ago I open-sourced a framework for split-testing, A/B testing or continous optimization. link] Id love to hear what anybody thinks.

San Francisco 132

San Francisco Lean Continuous Deployment DC 132

Startup Lessons Learned

DECEMBER 16, 2008

Lessons Learned by Eric Ries Tuesday, December 16, 2008 Engagement loops: beyond viral Theres a great and growing corpus of writing about viral loops, the step-by-step optimizations you can use to encourage maximum growth of online products by having customers invite each other to join. December 17, 2008 2:04 PM Alex Horovitz said.

Viral 140

Viral San Francisco Lean Continuous Deployment 140

www.rocketwatcher.com

DECEMBER 5, 2011

The big things to consider is how easy your name is to spell and how unique it looks to search engines. And for the LOVE OF GOD, keep the engineers our of the decision loop. Big thanks to @aprildunford for providing a framework around one of the hardest things in a startup: [link]. customer development. Great post.

Naming 41

Naming Startup Product Name Framework 41

Startup Lessons Learned

FEBRUARY 12, 2009

a guide for hackers) (This post was inspired by a conversation with Nivi from Venture Hacks , but is otherwise not his fault) There has been a proliferation of frameworks and metaphors lately that are designed to help startups avoid the all-too-common fatal mistake of failing to find a market. Expo (and a call for he.

San Francisco 89

San Francisco Continuous Deployment Ruby Lean 89

Startup Lessons Learned

FEBRUARY 11, 2009

Having had a number of years to try and answer this question at cocktail parties and social gatherings of all kinds, I thought Id try and expand on his framework a little, and then try and use these answers to help make suggestions for those who are trying to get people to buy virtual goods. Expo (and a call for he.

San Francisco 102

San Francisco Continuous Deployment Lean DC 102

Startup Lessons Learned

MAY 1, 2009

Q: Does the Lean Startup framework work efficiently within a company of 2-3 people (think small)?" A: yes, yes, yes Q: Does the Lean Startup framework work efficiently within a company of 2-3 people (think small)?" The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Lean 60

Lean San Francisco Startup Continuous Deployment 60