Startup Lessons Learned

JULY 3, 2009

Lessons Learned by Eric Ries Friday, July 3, 2009 Lean Startup fbFund wrap-up Last week I had a real blast meeting with the companies at the fbFund incubator at Palo Alto. The Lean Startup fbFund Edition View more documents from Eric Ries. See Validated learning about customers for more info. Without further ado.

Lean 60

Lean San Francisco Continuous Deployment Cofounder 60

Steve Blank

NOVEMBER 4, 2021

Lean Methodology consists of three tools designed for entrepreneurs building new ventures: The Business Model Canvas – to write down all the hypotheses about a new business; Customer Development – a process for testing those hypotheses outside the building; Agile Engineering – to rapidly build minimal viable products to test product/market fit.

Customer 424

Customer Marketing Lean Vertical 424

Steve Blank

SEPTEMBER 17, 2009

This post describes a solution – the Customer Development Model. In future posts I’ll describe how Eric Ries and the Lean Startup concept provide the equivalent model for product development activities inside the building and neatly integrates customer and agile development.

Customer Development 252

Customer Development Developer Customer Silicon Valley 252

Startup Lessons Learned

FEBRUARY 7, 2013

Last May, I shared the news that long-time Lean Startup advocates Brant Cooper and Patrick Vlaskovits were working on a new book called The Lean Entrepreneur featuring illustrations by FAKEGRIMLOCK. LitMotors approach to using Lean Startup to create a new vehicle category. That new book is about to hit bookstores everywhere.

Lean 167

Lean Entrepreneur Agile San Francisco 167

Both Sides of the Table

NOVEMBER 1, 2009

I know that this all seems obvious now with the movements started by Steven Blank ( Four Steps of Epiphany ) with the whole Customer Development processes / Lean Startup movements also popularized by people like Eric Ries. They had decided to take a Digg style approach to product development. It was Salesforce.com.

Customer 280

Customer Technical Review Software Review Mexico 280

Startup Lessons Learned

APRIL 7, 2010

Lessons Learned by Eric Ries Wednesday, April 7, 2010 Learning is better than optimization (the local maximum problem) Lean startups don’t optimize. Instead, we try to accelerate with respect to validated learning about customers. There are often counter-intuitive changes in customer behavior that depend on little details.

San Francisco 154

San Francisco Lean Metrics Design 154

Startup Lessons Learned

MAY 31, 2010

Expo Intensive rocked, the mainstream media has started writing about the Lean Startup, and - most of all - the movement continues to grow and evolve. I went to the conference thinking that I was well grounded in the basics of the Lean Startup approach and that attendance would hone the edges of that understanding.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

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. It lets the customer and development team spot problems with calculations almost immediately.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

SEPTEMBER 2, 2008

Its inspired by the classic OODA Loop and is really just a simplified version of that concept, applied specifically to creating a software product development team. There are three stages: We start with ideas about what our product could be. How about documentation that nobody reads? the data on a regular basis.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

steveblank.com

JULY 8, 2011

AgileZen – project management visually see and interact with your work Kanbanery – Simple online team or personal kanban board LeanKit Kanban – Great for visualizing work of product development Kanban Pad – “Nice and lean” and free online Kanban tool Banana Scrum – A tool simple as Scrum itself.

Software Review 110

Software Review Startup Silicon Valley Analytics 110

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. First of all, its a myth that cutting corners saves time.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

NOVEMBER 6, 2008

They take things like unit testing, design documents and code reviews more seriously than any other company Ive even heard about. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May. . Expo SF (May.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

Startup Lessons Learned

JUNE 17, 2010

But according to the theory, this should have been covered by the various specs and documentation we were rigorous about producing. Because the art team was considered an internal customer (and “friendly&# to boot), we didn’t waste a lot of time making the tools easy to use. This led to some pretty bizarre situations.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

MARCH 27, 2009

In lean times, it’s most important to focus on cutting costs in ways that speed you up, not slow you down. In fact, every single lean transformation documented in books like Lean Thinking took place in the midst of serious external threats. And, of course, theres the Lean Startup session at the upcoming Web 2.0

San Francisco 117

San Francisco Lean Continuous Deployment DC 117

Startup Lessons Learned

AUGUST 8, 2009

We owe a lot to this seminal document. When it becomes possible to build products "live" with customers, the cycle time changes and design becomes a much more dynamic process. Every time we execute a product pivot - changing some elements of our vision but not others - we change the very purpose of the product being designed.

Software Review 87

Software Review Design Software San Francisco 87

Startup Lessons Learned

NOVEMBER 13, 2008

Now, everyone is learning together - about your product, process, and team. Each five whys email is a teaching document. But also, the ETL doesn't change much anymore (except when integrating a new system), now that the warehouse is in production most of the change occurs in the marts and analytic products.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Steve Blank

JANUARY 6, 2014

In the last few years Agile and “Continuous Deployment” has replaced Waterfall and transformed how companies big and small build products. Agile is a tremendous advance in reducing time, money and wasted product development effort – and in having products better match customer needs.

Continuous Deployment 331

Continuous Deployment Customer Agile Cloud 331

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. I documented the lesson plans etc on [link] March 4, 2009 5:25 AM Eric said. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May. .

Programming 143

Programming San Francisco Lean Continuous Deployment 143

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. In this section, you really just want to document how your business will make money. Schedule.

Software Review 74

Software Review Software Delaware Forecast 74

Startup Lessons Learned

JANUARY 12, 2009

And I think a bad choice, a bad library, a horrible API, lack of documentation etc. You forgot to mention how awesome the documentation on php.net is. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? The Lean Startup Intensive is tomorrow at Web 2.0. Interesting post.

PHP 166

PHP Software Review Ruby San Francisco 166

Steve Blank

MAY 7, 2009

My two cents is that a business plan is the single place to collect your thinking about about your: business model, distribution channel, demand creation plan, financial assumptions, and customer and product development plan. Funny, but with their feedback, we changed several parts of the product.

Business Plan 152

Business Plan Silicon Valley RSS Venture Capital 152

Steve Blank

AUGUST 27, 2009

This series of posts is a brief explanation of how we’ve evolved from Product Development to Customer Development to the Lean Startup. The Product Development Diagram Emerging early in the twentieth century, this product-centric model described a process that evolved in manufacturing industries.

Silicon Valley 268

Silicon Valley Product Startup Product Development 268

Startup Lessons Learned

DECEMBER 6, 2008

When youve mastered that, consider adding operations, customer service, marketing, product management, business development - the idea is that when the team needs to get approval or support from another department, they already have an "insider" who can make it happen. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 74

San Francisco SCRUM Lean Continuous Deployment 74

www.vccafe.com

MARCH 11, 2013

For modifications, please edit the original document here. Lean Methodology Sources. Steve Blank on Lean Customer Development. Part 3- Lean Cust. Scanning / Document Management. Steve Blank’s Lean Startup Resources. Lean Startup Circle â?? Lean project management.

Software Review 53

Software Review Technical Review Startup 53

Startup Lessons Learned

AUGUST 16, 2010

First, SlideShare is a fantastic product (that I use on a regular basis) and an impressive company example of Lean Startup practices in action. Second, their story illustrates a key Lean Startup idea: proving the business in micro-scale. Early this year, SlideShare launched custom channels. That is customer development.

San Francisco 167

San Francisco Lean Analytics Continuous Deployment 167

Startup Lessons Learned

APRIL 9, 2015

They suspected that if they could do customer development throughout the development process, they could come up with a much better product. This is what led us initially to the Lean Startup,” he added. “We We should do Lean Startup and it will solve all our problems.” They could see the potential, however.

Lean 60

Lean Technology Metrics Developer 60

Startup Lessons Learned

SEPTEMBER 11, 2009

I agree that listening and communicating is a key to success, but customer development can only do so much. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? The Lean Startup Intensive is tomorrow at Web 2.0. Eric September 13, 2009 11:32 AM Joel Andren said. Expo SF (May.

Community 158

Community Management Lean Software Review 158

Startup Lessons Learned

NOVEMBER 5, 2008

Education Guideline Book (1st Edition) Sep 2006 View SlideShare document or Upload your own. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? The Lean Startup Intensive is tomorrow at Web 2.0. Amazing lean startup resources Is Entrepreneurship a Management Science?

Advertising 60

Advertising San Francisco Media Continuous Deployment 60

maplebutter.com

JANUARY 8, 2013

How to stay lean and iterate quickly while you’re building a two sided marketplace, especially when “network effect” and “critical mass” are the two main focuses? Near shoring development with your team (ex: your team is based in Canada / India) is cool, but not outsourcing. A few nuggets. 1) Hire A’s.

Technical Review 44

Technical Review Startup Cofounder Software Review 44