Startup Lessons Learned

NOVEMBER 4, 2008

My path to lean startups began with Kent Beck and extreme programming. The best resources there are his book Extreme Programming Explained: Embrace Change and the gentle introduction at extremeprogramming.org. Tech entrepreneurs rapidly discover that programming is meaningless when not anchored to customers’ needs.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

JANUARY 30, 2009

As with many Silicon Valley failures, a flawless PR launch turned into a flawed customer acquisition strategy. I know of at least five former employees that went on to become startup founders. Case Study: Continuous deployment makes releases n. We can capitalize on new customers. for Harvard Business Revie.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Startup Lessons Learned

NOVEMBER 8, 2008

Instead, we do everything possible to validate the founders belief. Most people cant sustain more than a few of these iterations, and the founders rarely get to be involved in the later tries. In order to do this, we have our customer development team work hard to find a market, any market, for the product as currently specified.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

FEBRUARY 11, 2009

Its a wonderful filter for people who are intrinsically motivated by the art of programming. This is especially true in Silicon Valley. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

Software Review 68

Software Review Software Hiring San Francisco 68

Startup Lessons Learned

NOVEMBER 7, 2008

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Case Study: Continuous deployment makes releases n. No departments The Five Whys for Startups (for Harvard Business R.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

JUNE 9, 2009

Lessons Learned by Eric Ries Tuesday, June 9, 2009 The Lean Startup Tokyo edition I had a blast speaking at Startonomics Tokyo , which was organized to foster ties between the startup cultures in Japan and Silicon Valley. benjaminjoffe : early adopters of buggy product are visionary customers, sometimes smarter than founders!

Lean 60

Lean San Francisco Japan Continuous Deployment 60

Startup Lessons Learned

NOVEMBER 17, 2008

Some companies and founders refuse to serve existing customers, and are always lurching from one great idea to the next. ► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

NOVEMBER 11, 2008

Lessons Learned by Eric Ries Tuesday, November 11, 2008 Where did Silicon Valley come from? I think the absolute best reading on this subject is a book called Regional Advantage: Culture and Competition in Silicon Valley and Route 128 by AnnaLee Saxenian. And what were they doing beforehand?

Silicon Valley 68

Silicon Valley San Francisco Lean Continuous Deployment 68

Startup Lessons Learned

MARCH 17, 2009

The problem is that the most authentic innovators and entrepreneurs are in the Valley. I want more than anything to come to Silicon Valley after I graduate and join the vibrant ecosystem. Case Study: Continuous deployment makes releases n. No departments The Five Whys for Startups (for Harvard Business R.

Lean 76

Lean San Francisco Web Continuous Deployment 76

Startup Lessons Learned

NOVEMBER 29, 2008

If done right, a programming interview serves two purposes simultaneously. For software engineers, I think this absolutely has to be a programming problem solved on a whiteboard. My technique is to structure a technical interview around an in-depth programming and problem-solving exercise. Have you tried it?

San Francisco 146

San Francisco Lean Agile Java 146

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. Use pair programming and collective code ownership. Pair programming is the most radical, but also the most helpful.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

MAY 14, 2009

What will be covered in the full-day program? Using examples drawn from his own experiences in the startup hub of Silicon Valley, Eric Ries unravels the myths and misconceptions that guide most startups, and paints a picture of a new way forward for the industry. Case Study: Continuous deployment makes releases n.

Lean 60

Lean San Francisco Continuous Deployment Software Review 60

Startup Lessons Learned

SEPTEMBER 8, 2009

Much of what makes the USA, and Silicon Valley in particular, such a great place to start a company is the result of good government policy. I'll add one more point: The SBIR program is based on a dated notion of small business research, and the multi-year process doesn't line up with the speed of many modern startups.

DC 90

DC Washington San Francisco SBIR 90

Startup Lessons Learned

NOVEMBER 17, 2008

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Case Study: Continuous deployment makes releases n. No departments The Five Whys for Startups (for Harvard Business R.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

Startup Lessons Learned

NOVEMBER 18, 2008

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Case Study: Continuous deployment makes releases n. No departments The Five Whys for Startups (for Harvard Business R.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

AUGUST 24, 2009

Just like in the world of startups, we can start to use micro-scale pilot programs, executed in lean fashion, to gather real facts for making ROI decisions about new project investment. Most publishers are still caught up in an outdated “vision vs. metrics&# argument, which is already obsolete here in Silicon Valley.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

MAY 20, 2010

Heres an excerpt: Philosophy Helps Start-Ups Move Faster - WSJ.com Silicon Valley entrepreneurs and venture capitalists often churn out how-to business books and fancy themselves as management gurus, but few see their methodologies adopted. Case Study: Continuous deployment makes releases n. for Harvard Business Revie.

Lean 153

Lean San Francisco Arlington Continuous Deployment 153

Startup Lessons Learned

NOVEMBER 5, 2013

This post was co-written by Sarah Milstein & Eric Ries, co-hosts of The Lean Startup Conference. We’ve just published the program for this year’s Lean Startup Conference , December 9 to 11 in San Francisco, and we can say without hesitation that it’s completely unlike any other entrepreneurship conference in existence.

Lean 166

Lean Early Stage San Francisco Cofounder 166

Startup Lessons Learned

MARCH 13, 2009

Founders push for it. In some ways, founders are even worse. My experience is that many founders actually have a deep anxiety that maybe they are not succeeding. In fact, we often felt frustrated when new startups with a fraction of our success got terrific write-ups in Silicon Valley-centric venues.

San Francisco 168

San Francisco PR Lean Early Stage 168

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

NOVEMBER 5, 2008

Yet, I believe it was Obamas superior agility that led to a decisive 12-point margin in Arapahoe County, CO: I want to say thanks to everyone on the campaign, from the candidate on down to the paid staff and volunteers that I got to work with. Case Study: Continuous deployment makes releases n. for Harvard Business Revie.

Campaign 84

Campaign San Francisco Lean Agile 84

Startup Lessons Learned

MARCH 9, 2010

The event is being produced in partnership with Charles Hudson, who puts on many of Silicon Valleys top events, including the forthcoming Freemium Summit. Last, I always try to have a scholarship program for paid events, and this one is no exception. Im incredibly excited. Im incredibly excited. for Harvard Business Revie.

San Francisco 151

San Francisco Lean Continuous Deployment Startup 151

Startup Lessons Learned

FEBRUARY 7, 2010

Whether youre a US citizen or an immigrant, entrepreneur or investor, founder or employee, theres something you can do. This is especially true if you live outside the echo chamber of Silicon Valley. If you are an immigrant founder who has helped build a company that has created jobs in the US, we need you to tell your story.

San Francisco 118

San Francisco DC Startup Lean 118

Startup Lessons Learned

JULY 15, 2010

His posts are born of tremendous research into the secret history of Silicon Valley , and if you haven’t read those essays, you should. When private capital is available in sufficient quantities to satisfy investor and founder liquidity needs, why go IPO? Let me be clear: Steve is the historian. for Harvard Business Revie.

IPO 166

IPO San Francisco Lean Silicon Valley 166

Startup Lessons Learned

NOVEMBER 5, 2008

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Case Study: Continuous deployment makes releases n. No departments The Five Whys for Startups (for Harvard Business R.

Advertising 60

Advertising San Francisco Media Continuous Deployment 60

Startup Lessons Learned

NOVEMBER 19, 2008

Im Community Manager at VenCorps, co-host of commandN. I worked at Flock, ConceptShare and co-founded Raincity Studios in Vancouver. Would love to grab a coffee next time Im in the Valley. Case Study: Continuous deployment makes releases n. November 19, 2008 1:48 PM Will Pate said. Hi Eric, Will Pate here.

San Francisco 60

San Francisco Lean Continuous Deployment DC 60

Startup Lessons Learned

NOVEMBER 22, 2008

Collecting the answers Once you have the survey up and running, you need to design a program to have customers take it on a regular basis. ► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th.

.Net 158

.Net Operations San Francisco Lean 158

Startup Lessons Learned

JULY 9, 2009

And then, at my first Silicon Valley startup , I watched friends get laid off in successive waves as it started to fail. In fact, I remember sending him and his obscure-to-me co-founder (aka Reid Hoffman ) a bug report early-on, instead of taking them up on their offer of an in-person meeting. No business model, either.

San Francisco 94

San Francisco Lean Continuous Deployment DC 94

Startup Lessons Learned

SEPTEMBER 11, 2009

As a founder of a company, there is nothing more painful than to see your most loyal and devoted customers suffering. I cannot sink any more money into a program that is still having community problems. That is what company founders and staff do not get. " I couldn't agree more. No gain without pain. No of course not.

Community 158

Community Management Lean Software Review 158