Startup Lessons Learned

NOVEMBER 13, 2008

Lessons Learned by Eric Ries Thursday, November 13, 2008 Five Whys Taiichi Ohno was one of the inventors of the Toyota Production System. Hes a new employee, and he was not properly trained in TDD So far, this isnt much different from the kind of analysis any competent operations team would conduct for a site outage.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

JUNE 2, 2010

Lessons Learned by Eric Ries Wednesday, June 2, 2010 The Five Whys for Startups (for Harvard Business Review) I continue my series for Harvard Business Review with the Lean Startup technique called Five Whys. As start-ups scale, this agility will be lost unless the founders maintain a consistent investment in that discipline.

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

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. Even worse, agile wasnt really helping me ship higher quality software. Great stuff!

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

DECEMBER 7, 2008

Lessons Learned by Eric Ries Sunday, December 7, 2008 The hackers lament One of the thrilling parts of working and writing in Silicon Valley is the incredible variety of people Ive had the chance to meet. Its common to find a hacker at the heart of almost any successful technology company. He throws off volumes of code, and it works.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

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. Its not that the idea behind them is wrong, but I think agile team-building practices make scheduling per se much less important. Youd better.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

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. Its to everyones advantage to let the world think the founders thought of everything.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

SEPTEMBER 15, 2008

Lessons Learned by Eric Ries Monday, September 15, 2008 The one line split-test, or how to A/B all the time Split-testing is a core lean startup discipline, and its one of those rare topics that comes up just as often in a technical context as in a business-oriented one when Im talking to startups. October 3, 2008 2:23 PM schubie said.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

SEPTEMBER 10, 2008

Lessons Learned by Eric Ries Wednesday, September 10, 2008 Smarticus — 10 things you could be doing to your code right now Smarticus — 10 things you could be doing to your code right now A great checklist of techniques and tools for making your development more agile, written from a Rail perspective. Expo SF (May.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

MAY 31, 2010

I am grateful to everyone who helped make this event a success, especially my co-organizers Charles Hudson and David Sachs. And a special thanks is due to all of our presenters, panelists, and mentors. If thats true, its primarily due to your hard work, building companies and testing new ideas. We all owe you.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Startup Lessons Learned

JUNE 17, 2010

They are leaders, visionaries, founders and managers having tremendous success. I was the junior guy on a project team; I was called in to do some technical due diligence for reasons that were obscure to me, because the team already had much more senior engineers assigned to it. As a technical fix, it was brilliant.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Agile VC

APRIL 17, 2011

AGILEVC My idle thoughts on tech startups. Kayak was started here in my backyard of Boston… co-founder & CTO Paul English and the product/engineering team is based here in Concord MA. Co-founder & CEO Steve Hafner and the business team are based in Norwalk, CT. How to Evaluate Firms for a Seed VC.

Pre-Money Valuation 113

Pre-Money Valuation Liquidation Preference Dividend Common Stock 113

Startup Lessons Learned

JANUARY 30, 2009

Build a world-class technology platform, with patent-pending algorithms and the ability to scale to millions of simultaneous users. 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. We can skip the chasm.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Startup Lessons Learned

AUGUST 3, 2009

Refreshing to finally see lean and agile thinking emerge in product/business-floors and not only in technology. While it is still possible - and recommended to experiment with customers in order to determine the minimum that they need, the exercise is bit more complicated due to the formality of the release process. Thank you.

San Francisco 168

San Francisco Product Lean Continuous Deployment 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. Playing with new technologies. Seeing whats possible.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

JANUARY 7, 2010

for Harvard Business Review) Im excited to have just published the first of several articles on entrepreneurship for the Harvard Business Review online. The Conversation - Harvard Business Review For most of us, the phrase management science conjures up a decidedly non-entrepreneurial image, and for good reason.

San Francisco 119

San Francisco Management Continuous Deployment Lean 119

Startup Lessons Learned

JANUARY 12, 2010

Recent economic events, technological change, and the rapid diffusion of information about the old models have combined to help us all realize just how important entrepreneurship is - and just how little we really know about it. My success is due in no small part to their early and enthusiastic endorsement.

Lean 146

Lean San Francisco Wiki Startup 146

Startup Lessons Learned

MARCH 22, 2010

Part of this is due to their determination to overtake us, but part is due to structural changes in the nature of entrepreneurship. For example, over 25% of the technology companies founded between 1995-2005 had a key immigrant founder. But today, it is getting harder and harder to maintain. Expo SF (May.

San Francisco 121

San Francisco Indiana Lean Startup 121

Hearpreneur

JANUARY 31, 2016

We decided to start something we felt would have the greatest positive impact on fellow business owners, an Agile Methodology consulting company. We quit our jobs, pooled our money, and set out to help companies implement Agile – a highly efficient, organized, and empowering way to run your business. 6 – Forging a New Path.

Entrepreneur 48

Entrepreneur India Cofounder Technical Review 48

Startup Lessons Learned

JULY 13, 2009

Lessons Learned by Eric Ries Monday, July 13, 2009 The Principles of Product Development Flow If youve ever wondered why agile or lean development techniques work, The Principles of Product Development Flow: Second Generation Lean Product Development by Donald G. Wow, great review! Thanks for the informative review.

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

JANUARY 15, 2010

Lessons Learned by Eric Ries Friday, January 15, 2010 Two Ways to Hold Entrepreneurs Accountable (for Harvard Business Review) The next part in the series I am writing for Harvard Business Review is online. They are long-term bets on the development of a new line of business, a new technology platform, or the creation of a new market.

Hockey Stick 105

Hockey Stick San Francisco Entrepreneur Lean 105

Startup Lessons Learned

FEBRUARY 10, 2009

Code reviews and pairing Great practices. Heck, thats what it says right there in the agile manifesto. The first version of the 3D IMVU client took about six months to build, and as the founders iterated towards a compelling user experience, the user base grew monthly thereafter. But it worked. We made it. So can you.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

FEBRUARY 11, 2009

Yes, you may be more familiar with the term open source, but lets give credit where credit is due , at least for today). Ignore the famous people who are busy giving lots of speeches about how technology X will change the world. Heres the short version: hire people from the online communities that develop free software. Expo SF (May.

Software Review 68

Software Review Software Hiring San Francisco 68

Startup Lessons Learned

AUGUST 8, 2009

Lessons Learned by Eric Ries Saturday, August 8, 2009 Revisiting the Software Design Manifesto (and whats changed since then) My recent article on technical debt and its positive uses generated a fair bit of controversy. It had a pretty good technical design. That "good design" turned out to be technical debt, after all.

Software Review 87

Software Review Design Software San Francisco 87

Startup Lessons Learned

OCTOBER 5, 2009

Due to an interaction effect between your hardware, solar flares, and quantum flux, this virus will crash your computer and erase your hard drive sometime soon. And I’ve seen companies fail the other way – the so-called Friendster effect: having a high-profile technical failure just when customer adoption is going wild.

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 133

Startup Lessons Learned

SEPTEMBER 18, 2008

Lessons Learned by Eric Ries Thursday, September 18, 2008 How to get distribution advantage on the iPhone I have had the opportunity to meet a lot of iPhone-related companies lately. From a technical point of view, its amazing. All I see is a name, an icon, a price, the developers name, and a review star-rating.

Distribution 74

Distribution San Francisco Lean Continuous Deployment 74

Startup Lessons Learned

AUGUST 24, 2009

The other revels in the world as we all know it will be someday: limitless distribution enabled by new technologies, the importance of collaborative filters, and on-demand availability of all content for end-users. But the same technologies that make life difficult for traditional marketers also offer them unprecedented new opportunities.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

wordsting.com

APRIL 4, 2013

My co-founders and I did. Based on painful personal experience, this article illustrates the limitations of the Lean Startup theory and how it distracts founders from the fundamentals of successful entrepreneurship – the unlean lessons. With dozens of guided demos garnishing good reviews our marketing mostly worked.

Lean 61

Lean Startup Software Review San Francisco 61

Startup Lessons Learned

JULY 2, 2009

That’s because Five Whys will often pierce the illusion of separate departments and discover the human problems that lurk beneath the surface of supposedly technical problems. But if we stay stuck at the technical parts of the problem, and never uncover the human problems behind them, we’re not going far enough.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

SEPTEMBER 27, 2010

Over time, such teams either explode due to irreconcilable differences or dramatically slow down. I believe this is one reason why the myth of the dictatorial startup founder has such enduring appeal. Lean manufacturing , agile software development , and Theory of Constraints are all examples of this idea in action.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

AUGUST 26, 2009

Im also excited to share two long-form reviews from actual attendees. Thank you @ericries for drastically altering my perception of agile startup Thank you all so much for your kind words. Technically you argue it goes back 30 years when StorageTek was founded. I was really overwhelmed this time. Expo SF (May.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

FEBRUARY 20, 2009

So when we start checking in code more often, release more often, or conduct more frequent design reviews, we can actually do a lot to make those steps dramatically more efficient. Sounds very similar to agile development which is the way. However, a technological solution cant necessarily resolve all human root causes.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

MAY 14, 2009

Lessons Learned by Eric Ries Thursday, May 14, 2009 The Lean Startup Workshop - now an OReilly Master Class My rate of posting has been much lower lately, and this is mostly due to preparations for the upcoming Lean Startup Workshop on May 29. I joined a financial services tech startup in 1999. May 14, 2009 5:23 AM David said.

Lean 60

Lean San Francisco Continuous Deployment Software Review 60

Startup Lessons Learned

FEBRUARY 22, 2009

That data is completely consonant with the people I know who are successful technologists today, and similar patterns are documented in each recent wave of technology innovation. There would be no Microsoft, Sun Microsystems, or countless other job-creating tech companies today if early computers required corporate authorization to use.

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

JUNE 15, 2009

Thanks to a phenomenon called the Fundamental Attribution Error in psychology, humans tend to become convinced that other people’s behavior is due to their fundamental attributes, like their character, ethics, or morality – even while we excuse our own actions as being influenced by circumstances. Expo SF (May.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

FEBRUARY 16, 2009

Its design goals arent geared towards efficiency in terms of technical costs. It would carefully monitor their behavior, and especially their technical metrics, like crashes and freezes. Then we could render the whole site with much less latency, bandwidth usage, and server cost. Expo SF (May. Expo (and a call for he.

Continuous Deployment 68

Continuous Deployment San Francisco Software Review Lean 68

Startup Lessons Learned

JANUARY 12, 2009

However, it made me remember that Im tired of technology arguments. I believe that if you practice TDD, continuous integration, and active refactoring from the start, you can write maintainable code in any language. January 16, 2009 2:02 PM Chrissaid. Nice article. Dont get me wrong, the right tool should be used for the right problem.

PHP 166

PHP Software Review Ruby San Francisco 166

Startup Lessons Learned

SEPTEMBER 11, 2009

I think this is one of your better posts this year, because you are addressing a risk that you face AFTER some early success, when your guard is down and you are more inclined to believe that you know what you are doing and therefore do not need to be as diligent at framing your hypotheses and how you plan to verify them.

Community 158

Community Management Lean Software Review 158