Startup Lessons Learned

SEPTEMBER 7, 2008

In a startup, both the problem and solution are unknown, and the key to success is building an integrated team that includes product development in the feedback loop with customers. 2008 09 06 Eric Ries Haas Columbia Customer Development Engineering View SlideShare presentation or Upload your own. Expo SF (May.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

JULY 29, 2009

I hope to show why lean and agile techniques actually reduce the negative impacts of technical debt and increase our ability to take advantage of its positive effects. Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

ConversionXL

SEPTEMBER 6, 2013

So What is Customer Development? Steve Blank, a serial entrepreneur in Silicon Valley, developed a methodology for creating businesses that runs in parallel with the traditional product development process. The core idea behind customer development is that the assumptions you make about a target market are only guesses.

Customer Development 126

Customer Development Conversion Developer Customer 126

Startup Lessons Learned

NOVEMBER 8, 2008

Steve Blank has devoted many years now to trying to answer that question, with a theory he calls Customer Development. This theory has become so influential that I have called it one of the three pillars of the lean startup - every bit as important as the changes in technology or the advent of agile development. Expo SF (May.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

JUNE 15, 2009

Of all the tactics I have advocated as part of the lean startup , none has provoked as many extreme reactions as continuous deployment , a process that allows companies to release software in minutes instead of days, weeks, or months. First, continuous deployment separates out two different definitions of the terms “release.&#

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

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. I think where we get into trouble is we have many definitions of quality.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

AUGUST 26, 2009

I did my best to capture video and audio; a YouTube playlist and Slideshare slidecast are below: Slides (with audio): 2009 08 19 The Lean Startup TechStars Edition View more presentations from Eric Ries. Inspiring ideas: real-time biz metrics; safe continuous deployment; A/B split testing. Articulate, inspirational.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

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. Growth - when you have existing customers, the pressure is on to grow your key metrics day-in day-out. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

AUGUST 24, 2009

So let’s turn our attention from what may happen in the future to what is definitely happening in the present. Despite all the energy invested in talking to authors about the size of their platform, very few gatekeepers have a rigorous set of metrics for measuring it. My blog has over 14000 subscribers, for example. Is that good?

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

JUNE 5, 2009

Unfortunately, most decisions that confront startups lack a definitive right answer. Sometimes an early negative result from an experiment is a harbinger of doom for that product, and means it should be abandoned. In a startup context, numbers like gross revenue are actually vanity metrics, not actionable metrics.

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Steve Blank

MARCH 11, 2015

And worse, even if someone does manage to start something new, our management structure has so many financial, legal and HR hurdles that every initiative needs to match our existing business financial metrics, processes and procedures. There are financial metrics (Return on Investment, Hurdle Rate, etc.) Lessons Learned.

Widget 120

Widget Lean Business Model Metrics 120

Startup Lessons Learned

OCTOBER 28, 2008

Its different from selling a product, because it is not part of our regular business practice, is not something that relates to our core competence, and tends not to happen in a repeatable and scalable way. Ill exclude those non- lean startups who basically exist for the purpose of raising bigger and bigger sums of money. Expo SF (May.

San Francisco 128

San Francisco Lean Continuous Deployment DC 128

Startup Lessons Learned

OCTOBER 21, 2008

Lessons Learned by Eric Ries Tuesday, October 21, 2008 Lean startups vs lean companies Venture Hacks has a great article today on lean startups. They quote extensively from two of our most important thinkers: Taiichi Ohno , creator of the Toyota Production System, and Kent Beck , creator of extreme programming.

Lean 121

Lean San Francisco Continuous Deployment Startup 121

Startup Lessons Learned

JANUARY 18, 2010

Recently, he was bitten by the lean startup bug and has started writing about his experiences attempting to apply lean startup and customer development principles. Ive previously named his post Achieving Flow in a Lean Startup as one of my favorite blog posts of 2009. I am not advocating adding no features at all.

Continuous Deployment 151

Continuous Deployment San Francisco Lean Wiki 151

Startup Lessons Learned

MAY 1, 2009

Lessons Learned by Eric Ries Friday, May 1, 2009 Lean Startup webcast post-game Wow, what an incredible turnout for webcast this morning, right on the heels of a phenomenal crowd at startup2startup last night. Its been a great twelve hours for the lean startup! In a future post, Ill attempt to unpack this definition in detail.

Lean 60

Lean San Francisco Startup Continuous Deployment 60

Up and Running

JULY 26, 2016

1x hacker in charge of product/development. 1x hipster working with both product and growth. Lean marketing. This is when metrics come into play. See Also: The Top 10 Tools for Tracking Your Web Metrics. See Also: The 7 Key Metrics Every Business Owner Should Monitor. Big press (cheap or free).

Revenue 60

Revenue Acquisition Channel Campaign 60

Startup Lessons Learned

JUNE 21, 2010

So let’s begin with a definition of a startup that captures its essential nature, and tries to leave behind the specific associations of the most famous startups. A startup is a human institution designed to deliver a new product or service under conditions of extreme uncertainty. This is a tricky part of the definition, too.

San Francisco 168

San Francisco Startup Lean Continuous Deployment 168

Steve Blank

SEPTEMBER 10, 2009

In future posts I’ll describe how Eric Ries and the Lean Startup concept provided the equivalent model for product development activities inside the building and neatly integrates customer and agile development. Market Type also affects the market size as well as how you launch the product into the market.

Customer Development 220

Customer Development Developer Customer Silicon Valley 220

ReadWriteStart

JUNE 29, 2020

Before we look at ways to bootstrap a startup, let’s consider a comprehensive definition of what a startup is. Implement the “lean startup” philosophy. Product development also occurs in small iterations or changes. Year-on-year growth metrics in unique site traffic is 7.8 What is a startup?

Bootstrapping 85

Bootstrapping Global Startup Hungary 85

Startup Lessons Learned

AUGUST 3, 2009

Lessons Learned by Eric Ries Monday, August 3, 2009 Minimum Viable Product: a guide One of the most important lean startup techniques is called the minimum viable product. I was delighted to be asked to give a brief talk about the MVP at the inaugural meetup of the lean startup circle here in San Francisco. Thanks Eric.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Up and Running

MAY 23, 2016

Step 1: Start with a lean plan. It’s the fastest way to get your idea onto paper, and it’s the very first step in the lean planning process, which is much easier and more iterative than traditional business planning methods. Introducing Lean Planning: How to Plan Less and Grow Faster. How to Write a Traditional Business Plan.

Software Review 74

Software Review Software Delaware Forecast 74

Startup Lessons Learned

SEPTEMBER 19, 2009

By definition these 10,000 founders wouldnt be taking jobs from Americans: it could be part of the terms of the visa that they couldnt work for existing companies, only new ones theyd founded. Its actually part of a lean startup story. For more on his lean startup journey, you can take a look at this slide presentation.

San Francisco 150

San Francisco Founder DC Washington 150

Startup Lessons Learned

OCTOBER 19, 2009

What sets this approach apart from practices like using focus groups is that companies base product development decisions not just on what customers say they want but on how they vote with their wallets. Of course, as more people attempt to use the Minimum Viable Product as a tactic, there are a lot of misconceptions possible.

San Francisco 137

San Francisco Product Lean Continuous Deployment 137

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. No vanity metrics should be looked at. It works to undermine excuses for poor or shoddy work.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

SEPTEMBER 15, 2009

I promised to post the slides for my highly abbreviated version of the lean startup presentation, so here they are. 2009 09 08 The Lean Startup Gov 2.0 g2s The very abbreviated version of Customer Development (channeling Steve Blank ). g2s The very abbreviated version of Customer Development (channeling Steve Blank ).

San Francisco 92

San Francisco DC Washington Lean 92

Startup Lessons Learned

FEBRUARY 28, 2009

Lessons Learned by Eric Ries Saturday, February 28, 2009 Throwing away working code Lean startups work by systematically eradicating waste. This builds on a lot of great thinking that has come before, like the agile movements insistence that only the creation of working code counts as progress for a software development team.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

NOVEMBER 29, 2008

The technical interview is at the heart of these challenges when building a product development team, and so I thought it deserved an entire post on its own. Still, a startup product development team is a service organization. Labels: hiring , product development 5comments: TedHoward said. Expo SF (May.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

JULY 9, 2009

And speaking of Facebook, I definitely didnt think it was a good idea when I first heard about it. Definitely one of the best posts from you. All my products and ideas focus on early cash and a business model that works from the first day. The Lean Startup Intensive is tomorrow at Web 2.0. What was different this time?

San Francisco 94

San Francisco Lean Continuous Deployment DC 94

Startup Lessons Learned

APRIL 9, 2009

Thats the essence of so many of the lean startup techniques Ive evangelized: customer development , the Ideas/Code/Data feedback loop , and the adaptation of agile development to the startup experience. The lean startup focuses on situations where we have both an unknown problem and an unknown solution.

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

Steve Blank

NOVEMBER 5, 2009

It should go without saying that this post is not advice, nor is it recommendation of what you should do, it’s simply my observation of how companies using Customer Development positioned themselves to successfully raise money from venture investors. Your presentation doesn’t have a single word about Lean Startups or Customer Development.

Customer Development 267

Customer Development Developer Customer Silicon Valley 267

Startup Lessons Learned

FEBRUARY 10, 2009

But I will tell you not to have too little or too much, because those definitely ruin the food or product. This development philosophy created a culture around rapid prototyping of features, followed by testing them against large numbers of actual customers. The Lean Startup Intensive is tomorrow at Web 2.0. We made it.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

JULY 31, 2009

I'll definitely try this out. The Lean Startup Intensive is tomorrow at Web 2.0. ► April (11) Video update on the Startup Visa Act Lean Enterprise Institute webinar, April 28 Four myths about the Lean Startup Sneak preview, KISSmetrics (and more) Sneak preview, Grockit The Lean Startup Intensive at Web 2.0

San Francisco 68

San Francisco Lean Startup Continuous Deployment 68

Startup Lessons Learned

OCTOBER 11, 2009

Their old product prioritization meetings may have been a battle of opinions, but at least they understood what was going on. Now they first had to go through a ritual that involved complex math, reached no definite outcome, and then proceeded to have a battle of opinions anyway! To their surprise, the metrics didn’t move at all.

San Francisco 133

San Francisco Lean Metrics Continuous Deployment 133

Startup Lessons Learned

AUGUST 1, 2009

One of the most common questions I get about the lean startup methodology is, "but what about Steve Jobs ?" He doesnt put out crappy, buggy products and then ask for feedback. So how do you reconcile his success with the lean startup, which seems to suggest the opposite?" And he doesnt shy away from big-bang launch events.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

A Smart Bear: Startups and Marketing for Geeks

MARCH 11, 2014

How many employees would a medium-sized business have in your definition? Some people have different definitions of that. I mean they have these definitions. Meetings are definitely one of those places, but email is another primary way that that comes in. Jason: Okay. I’m just clarifying. Edwin: Yes.

Technical Cofounder 220

Technical Cofounder Cofounder Software Review Management 220

Startup Lessons Learned

DECEMBER 14, 2009

Some companies definitely should. Others definitely shouldn’t. Let’s look at some examples: In a traditional business, customers pay money for a physical artifact (a product) or a service. Take the minimum viable product , for starters. These concepts have important implications for any lean startup.

Customer 156

Customer San Francisco Viral Lean 156

Startup Lessons Learned

FEBRUARY 11, 2009

Definitely interested in the perspective of the open-source contributor solicited with a job offer. Im definitely curious about your thoughts on how to present the company right. The Lean Startup Intensive is tomorrow at Web 2.0. Amazing lean startup resources Is Entrepreneurship a Management Science? Expo SF (May.

Software Review 68

Software Review Software Hiring San Francisco 68