Steve Blank

JUNE 26, 2014

We’ve pivoted our Lean LaunchPad / I-Corps curriculum. — Over the last three years the Lean LaunchPad class has started to replace the last century’s “how to write a business plan” classes as the foundation for entrepreneurial education. . The Lean LaunchPad is now being taught in over 100 universities.

Intellectual Property 290

Intellectual Property Lean IP Open Source 290

Startup Professionals Musings

JUNE 9, 2013

I strongly recommend a dramatic departure from this model, called “planned iteration” or Lean Startup methodology, where you assume you won’t get it right the first time, so you launch with a minimum viable product (MVP). Since you can predict that your first iteration will somehow miss the mark, speed and cost of pivoting are critical.

Agile 263

Agile Startup Social Network Software Development 263

Steve Blank

SEPTEMBER 5, 2013

Over the last three years our Lean LaunchPad / NSF Innovation Corps classes have been teaching hundreds of entrepreneurial teams a year how to build their startups by getting out of the building and testing their hypotheses behind their business model. Filed under: Customer Development , Lean LaunchPad , Teaching.

Lean 322

Lean Customer Development Sales Cycle Business Model 322

Steve Blank

SEPTEMBER 3, 2014

As he was learning from potential customers and providers he would ask, “What if we could have an app that allowed you to schedule low cost moves?” As the miles sped by I explained to Dave that he had understood only two of the three parts of what makes a Lean Startup successful. This was a great call.

Cofounder 336

Cofounder Founder Technical Cofounder Coder 336

Startup Professionals Musings

NOVEMBER 17, 2014

I strongly recommend a dramatic departure from this model, called “planned iteration” or Lean Startup methodology, where you assume you won’t get it right the first time, so you launch with a minimum viable product (MVP). Since you can predict that your first iteration will somehow miss the mark, speed and cost of pivoting are critical.

Agile 253

Agile Startup Social Network Software Development 253

Startup Lessons Learned

DECEMBER 14, 2017

Guest Post by Misti Yang, Writer for Lean Startup Co. Editor’s Note: We wrapped up the 2017 Lean Startup Week in San Francisco just a few weeks ago, and we’re excited to share with you some of the best lessons learned in entrepreneurship and corporate innovation. Because these Lean Startup people, they do crazy stuff,” Alex joked. “So

Lean 245

Lean Startup CTO Hire Cofounder 245

ReadWriteStart

APRIL 24, 2021

At the same time, leaders are also looking towards acquiring that entrepreneur Agility. Thus, many have been fostering Agile thinking and mindset within their teams. The four Agile values, defined in the Agile Manifesto, deliver value to the customer, responsiveness to change, effective communication, and people centricity.

Agile 146

Agile SCRUM Technical Review Management 146

Gust

NOVEMBER 9, 2014

Eric Ries on Lean Startup methodology, via Wikipedia. I strongly recommend a dramatic departure from this model, called “planned iteration” or Lean Startup methodology, where you assume you won’t get it right the first time, so you launch with a minimum viable product (MVP). Invested Interests agile entrepreneur lean startup pivot'

Agile 163

Agile Startup Lean Social Network 163

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. For example, take the lean dictum of working in small batches.

Product Development 153

Product Development Developer San Francisco Product 153

Steve Blank

SEPTEMBER 16, 2014

” She looked at bit puzzled, so I continued to explain… One of the virtues of using the Business Model Canvas as part of a Lean Startup is that it helps you frame each one of your nine critical hypotheses. How much value should I put on co-founders I’ve worked with before?” ” Lessons Learned.

Cofounder 335

Cofounder Founder Intellectual Property Business Model 335

YoungUpstarts

MAY 9, 2017

Lean is a methodology that can be applied to all disciplines of knowledge work to increase business efficiency, agility, and visibility. Due to its roots in manufacturing, Lean is often equated with the elimination of waste, but this view of Lean misses the mark on realizing its true value. Lean Transformations.

Lean 124

Lean Agile Technical Review Dilution 124

Startup Lessons Learned

SEPTEMBER 13, 2011

At 11:45am I'll be honored to share the stage with two great entrepreneurs: Introducing The Lean Startup, by Eric Ries with case studies, Intuit’s Scott Cook and Instagram’s Kevin Systrom And in the evening, the book launch party is also part of Disrupt. By learning to be rapidly responsive and agile. You can grab one here.

Lean 155

Lean Seattle Los Angeles San Francisco 155

Startup Lessons Learned

JANUARY 19, 2009

Lessons Learned by Eric Ries Monday, January 19, 2009 Lean hiring tips In preparing for the strategy series panel this week, I have been doing some thinking about costs. Fundamentally, lean startups do more with less, because they systematically find and eliminate waste that slows down value creation.

Lean 140

Lean Hiring San Francisco Continuous Deployment 140

Startup Lessons Learned

NOVEMBER 4, 2008

Lessons Learned by Eric Ries Tuesday, November 4, 2008 Principles of Lean Startups, presentation for Maples Investments Image via Wikipedia Steve Blank and I had the opportunity to create a presentation about lean startups for Maples Investments. Agile software development. you get the idea. Customer development.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Steve Blank

APRIL 20, 2009

An interesting phenomena of the 1920s that illustrates the fragility and cost of vacuum tubes is the “Reflex Receiver&# design methodology. There are serious negative trade-off costs with using reflex designs but compared to the economic costs of each vacuum tube, it was a justified trade-off. to do that.

Silicon Valley 302

Silicon Valley RSS San Francisco Technical Review 302

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. Expo SF (May.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

NOVEMBER 12, 2013

Guest post by Lisa Regan, writer for The Lean Startup Conference. We’ve made some cool additions to our pre-conference webcast lineup , including two conversations with founding figures for methods that underlie Lean Startup. Indeed, rapid cycles lead to very short release times and low costs of change.

Product Development 167

Product Development Software Review Technical Review Developer 167

Startup Lessons Learned

NOVEMBER 7, 2008

We had endless arguments internally about what features it should include, how the avatars should look, and how much it should cost. Just load them all in and choose a low cost-per-click. Seems like a fairly low-cost method of gauging customer interest for a would-be product. The Lean Startup Intensive is tomorrow at Web 2.0.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Steve Blank

APRIL 10, 2009

That’s why startups are agile. Startups that are agile have mastered one other trick – and that’s Tempo – the ability to make quick decisions consistently over extended periods of time. Reply Lots of low cost experiments « Open Ambition , on April 22, 2009 at 8:58 am Said: [.]

Silicon Valley 309

Silicon Valley RSS Startup Agile 309

Steve Blank

AUGUST 31, 2009

Finally, I’ll write about 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. customers aren’t buying it, the cost of distribution is too high, etc.) Product Development Diagram 1.

Customer Development 245

Customer Development Developer Customer Silicon Valley 245

Startup Lessons Learned

OCTOBER 20, 2008

When I first encountered agile software techniques, in the form of extreme programming , I thought I had found the answer. I explained it to people this way: agile lets you make the trade-offs visible to whole company, so that they can make informed choices. Even worse, agile wasnt really helping me ship higher quality software.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

JULY 29, 2009

Although it costs to pay down the principal, we gain by reduced interest payments in the future. 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. The human tendency to moralize about debt affects engineers, too.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

NOVEMBER 13, 2008

This approach is a the heart of breaking down the "time/quality/cost pick two" paradox , because these small investments cause the team to go faster over time. Wed never heard of five whys, and we had plenty of "agile skeptics" on the team. The Lean Startup Intensive is tomorrow at Web 2.0. Five whys helps us keep our cool.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

SEPTEMBER 30, 2008

If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? Platform selection and technical design - if your business strategy is to create a low-burn, highly iterative lean startup, youd better be using foundational tools that make that easy rather than hard.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

SEPTEMBER 7, 2008

In addition to presenting the IMVU case, we tried for the first time to do an overview of a software engineering methodology that integrates practices from agile software development with Steves method of Customer Development. Ive attempted to embed the relevant slides below. What about a hardware business with some long-lead-time components?

Customer Development 131

Customer Development Engineer San Francisco Developer 131

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. Who will ultimately bear the cost of their mistakes? How severely is failure punished?

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Steve Blank

APRIL 21, 2011

The Stanford Lean LaunchPad class was an experiment with a new model of teaching startup entrepreneurship. All the teams were showing us what agile looked like, but this week several would remind us what focused and relentless really meant. Veritas , the team building a low cost residential wind turbine. Next was D.C.

Channel 234

Channel Artificial Inteligence San Francisco Business Model 234

Startup Lessons Learned

FEBRUARY 20, 2009

I owe it originally to lean manufacturing books like Lean Thinking and Toyota Production System. Sounds very similar to agile development which is the way. The Lean Startup Intensive is tomorrow at Web 2.0. The batch size is the unit at which work-products move between stages in a development process. Small is beautiful.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

NOVEMBER 8, 2008

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. The Lean Startup Intensive is tomorrow at Web 2.0. ► May (3) Thank you Philosophy Helps Start-Ups Move Faster (WSJ on the.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

OCTOBER 5, 2009

Or, if it really was prevented, what was the opportunity cost of choosing to prevent it ahead of time? And in most situations, there is significant cost involved in negotiating over the right estimates to plug in. In other words, a principled way to combine agility with stability. How much will it cost to solve this problem now?

San Francisco 133

San Francisco Architecture Lean 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 ?" So how do you reconcile his success with the lean startup, which seems to suggest the opposite?" Plus, the premise of the question misunderstands the lean startup, too. And he doesnt shy away from big-bang launch events.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

SEPTEMBER 10, 2008

I know plenty of people who prefer more advanced source control system, but my belief is that many agile practices diminish the importance of advanced features like branching. 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

JULY 2, 2009

Lessons Learned by Eric Ries Thursday, July 2, 2009 How to conduct a Five Whys root cause analysis In the lean startup workshops , we’ve spent a lot of time discussing the technique of Five Whys. My intention is to describe a full working process, similar to what I’ve seen at IMVU and other lean startups.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Steve Blank

JUNE 26, 2015

—– Lean Innovation Management. In the last five years “ Lean Startup ” methodologies have enabled entrepreneurs to efficiently build a startup by searching for product/market fit rather than blindly trying to execute. The result will be: a new, Lean version of the Three Horizons of Innovation. Here’s how.

Lean 120

Lean Management Business Model Incubator 120

Steve Blank

NOVEMBER 12, 2009

After these slides, these VC’s recognized that this company had dramatically reduced risk and built a startup that was agile, resilient and customer-centric. The presentation didn’t have a single word about Lean Startups or Customer Development. The primary goal of customer development is to reduce the cost of mistakes.

Venture Capital 245

Venture Capital Silicon Valley RSS Hockey Stick 245

Steve Blank

SEPTEMBER 14, 2017

They accomplished their goal, but at a huge, unanticipated cost: the processes and committees they designed ended up strangling innovation. A canonical Lean Innovation process inside a company or government agency would look something like this: Curation. There’s a much better way. As the head of the U.S. Lessons Learned.

Incubator 319

Incubator Curation Engineer Government 319

Steve Blank

MAY 6, 2015

I am always surprised when critics complain that the Lean Startup’s Build, Measure, Learn approach is nothing more than “throwing incomplete products out of the building to see if they work.”. It’s time to update Build, Measure, Learn to what we now know is the best way to build Lean startups. Here’s how. Build-Measure-Learn.

Lean 120

Lean Agile Business Model Customer Development 120