Startup Lessons Learned

NOVEMBER 7, 2008

So, if youre interested in helping avoid mistakes like that, here are the steps: Get a domain name. It doesnt have to be the worlds catchiest name, just pick something reasonably descriptive. If youre concerned about sullying your eventual brand name, dont use your "really good" name, pick a code name.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Steve Blank

NOVEMBER 21, 2016

The students “get out of the building” and test their hypotheses in front of potential beneficiaries using the Customer Development methodology, all while building and updating their Minimal Viable Products. If you can’t see the presentation click here. If you can’t see the presentation click here.

Silicon Valley 120

Silicon Valley Washington United Kingdom Lean 120

Steve Blank

NOVEMBER 21, 2016

The students “get out of the building” and test their hypotheses in front of potential beneficiaries using the Customer Development methodology, all while building and updating their Minimal Viable Products. If you can’t see the presentation click here. If you can’t see the presentation click here.

Silicon Valley 120

Silicon Valley Washington United Kingdom Lean 120

David Teten

APRIL 1, 2021

Nick Kim , Crosscut’s Head of Platform, in his presentation at the 4th Annual VC Platform Summit, shared their Platform development methodology, which he viewed as an exercise in product development. Customer Development. A well-developed model is Andreessen Horowitz’s Executive Briefing Center. Advantages.

Private Equity 78

Private Equity Venture Capital Portfolio Equity 78

Startup Lessons Learned

AUGUST 26, 2009

If you watch the video/audio below, youll get to see some of the questions I was asked after my presentation. Accept that many successful companies are going to want to be backed by big-name firms in other cities. And do your customer development. These quotes are, as is my custom, straight from twitter.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

APRIL 14, 2009

Every board meeting, the metrics of success change. 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. Time-to-complete-a-sale is not a bad metric for validated learning at this stage.

Customer 167

Customer San Francisco Lean Hockey Stick 167

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.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Steve Blank

SEPTEMBER 14, 2009

Filed under: Customer Development , Venture Capital | Tagged: Entrepreneurs « Customer Development Manifesto: Market Type (part 4) Customer Development Manifesto: The Path of Warriors and Winners (part 5) » 16 Responses Jon Ziskind , on September 14, 2009 at 9:19 am Said: Steve – Great post and really great advice.

Silicon Valley 233

Silicon Valley IPO Technical Review Venture Capital 233

Startup Lessons Learned

SEPTEMBER 12, 2008

It’s easy to overestimate the impact of this kind of traffic because it just feels good to have your name and company featured. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? It strokes your ego. No departments The Five Whys for Startups (for Harvard Business R.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Steve Blank

DECEMBER 7, 2010

We’ll build the class around the business model / customer development / agile development solution stack. Secondly, each student team will present “lessons learned” from their team’s experience getting out of the building learning, testing, iterating and/or pivoting their business model. So what did you do?

Wiki 315

Wiki Lean Management Business Model 315

Startup Lessons Learned

OCTOBER 4, 2008

In 2007, BusinessWeek named Ries one of the Best Young Entrepreneurs of Tech and in 2009 he was honored with a TechFellow award in the category of Engineering Leadership. my startup is Blank Label (www.blank-label.com), which is a provider of custom dress shirts that empowers consumers to become the designer of their own product.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

JULY 30, 2009

I want to thank Techstars for putting this event together and giving me a chance to experience the scene, even if it lacks a name. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Traveling to new startup hubs is one of my favorite things about being able to do this full-time.

Lean 68

Lean San Francisco Continuous Deployment DC 68

ConversionXL

MARCH 28, 2014

If you’re a B2B software company you’ll be happy to know a Forbes study titled “Video in the C-Suite” revealed that 59% of C-Suite executives would prefer to watch video over reading text if both are presented on a page. ” The visitor/view metric is one you should only be competing against yourself on.

Video 122

Video Software Review Cofounder Metrics 122

conversionxl.com

SEPTEMBER 10, 2013

It’s Not a Conversion Problem, It’s a Customer Development Problem. This is a customer development problem. So What is Customer Development? The core idea behind customer development is that the assumptions you make about a target market are only guesses. Website Analysis.

Customer Development 60

Customer Development Conversion Developer Customer 60

Startup Lessons Learned

FEBRUARY 20, 2009

Its had tremendous impact in many areas: continuous deployment , just-in-time scalability , and even search engine marketing , to name a few. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? I owe it originally to lean manufacturing books like Lean Thinking and Toyota Production System.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

JUNE 5, 2009

In a startup context, numbers like gross revenue are actually vanity metrics, not actionable metrics. Luckily, we also discovered that certain other metrics, like LTV and CPA were much better than we initially projected. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Startup Lessons Learned

JANUARY 18, 2010

Lessons Learned by Eric Ries Monday, January 18, 2010 Case Study: Continuous deployment makes releases non-events The following is a case study of one entrepreneurs transition from a traditional development cycle to continuous deployment. This case presents a further complication: desktop software. Read on to find out.

Continuous Deployment 151

Continuous Deployment San Francisco Lean Wiki 151

Startup Lessons Learned

OCTOBER 26, 2009

The key to successful integration of customer feedback is to make each kind of collection part of the regular company discipline of building and releasing products. Every two months, the company would have a big end-of-milestone meeting, with our Board of Directors, Business Advisory Board, and all employees present.

Advisory Board 151

Advisory Board Customer San Francisco Lean 151

Startup Lessons Learned

JANUARY 19, 2009

Much of what I have found effective is counter-intuitive, because it requires investing more effort in each hire - all in the name of efficiency. This is another sub-optimization caused by incentivizing the wrong metric. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Lean 140

Lean Hiring San Francisco Continuous Deployment 140

David Teten

SEPTEMBER 23, 2017

An investor had few hard metrics other than the actual financials, and little technology to make the process scaleable. Over the past few decades, better metrics became available, and investors could take a more analytical, data-driven approach. ” Historically, investing was a manual, artisan process.

Private Equity 60

Private Equity Venture Capital Equity Technical Review 60

Startup Lessons Learned

JULY 29, 2009

Real life seldom presents such comparable choices. How likely will customers ultimately use that feature? It's good to see that the metaphor continues to hold up and you have demonstrated a number of insights and opportunities that present themselves when you incur debt wisely. Instead, we balance lots of unknowns.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

MARCH 24, 2009

Lessons Learned by Eric Ries Tuesday, March 24, 2009 The metrics and levers of engagement, presentation on Engagement Loops for Facebook Developer Garage SF Ill be presenting a talk at the Facebook Developer Garage SF Wednesday evening. You can learn more about the event here. Thoughts?

Metrics 88

Metrics San Francisco Lean Viral 88

Startup Lessons Learned

OCTOBER 20, 2008

But we were cutting corners in the development methodology as well as in the code, in the name of increased speed. a is name, b is address, and c is tax percentage. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Startup Lessons Learned - the Conference (April 23.

Software Review 164

Software Review Engineer Management Technical Review 164

Up and Running

MAY 23, 2016

The importance of a domain name. For Gabriel Kuperman, founder and CEO of CuePin, finding a good domain name was a key part of his branding strategy. If you find the domain name you want is taken, Gabriel suggests turning to a domain marketplace that sells premium domains. Pick a name for your business.

Software Review 74

Software Review Software Delaware Forecast 74

Startup Lessons Learned

AUGUST 3, 2009

First, a definition: the minimum viable product is that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort. MVP, despite the name, is not about creating minimal products. Some caveats right off the bat. August 3, 2009 8:08 PM William Mitchell said.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

FEBRUARY 7, 2010

If youre a startup investor, and you support the goals of the Startup Visa proposal, wed like you lend your name to our efforts. If youre a startup investor, and you support the goals of the Startup Visa proposal, wed like you lend your name to our efforts. You can read about the latest iteration of the proposal at StartupVisa.com.

San Francisco 118

San Francisco DC Startup Lean 118

Startup Lessons Learned

JUNE 22, 2009

Each has its own iterative process: customer development and agile development respectively. IMVU had a roughly two-month-long development cycle. At this meeting, we would present our goals for the cycle, all the raw results wed managed to collect, and our conclusions about what was next. Heres what it looked like.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

andrewchenblog.com

MARCH 10, 2010

Coupled with A/B testing, customer development, and thinking through business problems in a scientific, hypothesis-driven way, you end up with a powerful cocktail of techniques to build a modern startup in the most iterative way possible. You could have named it “User Experience Debt&#. Please comment! It´s strategic.

Technical Review 47

Technical Review Design Las Vegas Product 47

Startup Lessons Learned

FEBRUARY 11, 2009

The same is true of brand-name products in almost every category (and it can be measured ). The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? This is always true, because modern economies have become increasingly virtual over the years. Startup Lessons Learned - the Conference (April 23.

San Francisco 102

San Francisco Continuous Deployment Lean DC 102

Startup Lessons Learned

DECEMBER 16, 2009

As Im pontificating about agile, I see the name Kent Beck in my peripheral vision. Eric Names matter. By pulling in a web of associations, names help people quickly assess ideas. There is a dark side to naming. The naming question has been raised about the "lean" in Lean Startups. Eric Names matter.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

Startup Lessons Learned

OCTOBER 7, 2008

If necessary, consider doing this under a different brand name than the one you are wedded to using. There will always be far more apps that dont make the top lists, no matter what metric is used. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Its like knowing the future.

San Francisco 68

San Francisco Lean Retention SEM 68

Startup Lessons Learned

SEPTEMBER 27, 2010

In fact, we know so much that we already know what they will care enough about (namely, the product’s quality – as opposed to, say, missing features). The second misunderstanding is a concern for what will happen if things turn out exactly as we originally predicted (namely, badly). No vanity metrics should be looked at.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

APRIL 7, 2010

At least, not in the traditional sense of trying to squeeze every tenth of a point out of a conversion metric or landing page. Instead, we try to accelerate with respect to validated learning about customers. Even if it shows improvement in some micro metric, does that invalidate the overall design? No one feature is to blame.

San Francisco 154

San Francisco Lean Metrics Design 154

Startup Lessons Learned

MARCH 13, 2009

Do some Customer Development instead. Who doesnt want to see their name in print? Know what the success metrics are for the launch. Now that were beginning our first marketing, the key partners we need have heard our name long enough to trust us. Help you raise money. But dont be too sure. Founders push for it.

San Francisco 168

San Francisco PR Lean Early Stage 168

Startup Lessons Learned

JULY 13, 2009

It moves at a rapid clip, each argument backed up with the relevant math and equations: marginal profit , Littles law , Markov processes , probability theory , you name it. Its goal is to help us recognize that every artifact of our product development process is really just a proxy variable. This is not for the faint of heart.

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

JULY 9, 2009

All the good domain names were taken, all the good ideas were being implemented. If Id bought just a handful of the "best of the rest" domain names that were available at the time (for a whopping $70 each), I probably could have just retired right then. No departments The Five Whys for Startups (for Harvard Business R.

San Francisco 94

San Francisco Lean Continuous Deployment DC 94

Startup Lessons Learned

OCTOBER 11, 2009

Ironically, meetings like this had given data and experimentation a bad name inside this company. No experiment can affect more than a specified number of customers (usually expressed as a % of total). Every experiment has to be evaluated based on a single standard report of 5-10 (no more) key metrics. What a waste.

San Francisco 133

San Francisco Lean Metrics Continuous Deployment 133