Steve Blank

AUGUST 3, 2012

Long before there was the Lean Startup, Business Model Canvas or Customer Development there was a guy in Santa Barbara California who had already figured it out. Frank Robinson of SyncDev has been helping companies figure out their minimum viable product and pivots since 1984, long before I even knew what it meant.

San Jose 261

San Jose Technical Review Customer Development Software Review 261

Startup Lessons Learned

SEPTEMBER 6, 2012

This year, for the first time, we've added a day of workshops and site visits to The Lean Startup Conference. We’re really proud to present the workshops, which we're holding on December 4, and we wanted to tell you more about them. We’ll talk about the cool site visits in a separate post.)

Lean 154

Lean Cofounder Startup Analytics 154

Startup Lessons Learned

OCTOBER 5, 2008

Lessons Learned by Eric Ries Sunday, October 5, 2008 The product managers lament Life is not easy when youre working in an old-fashioned waterfall development process, no matter what role you play. The product manager was clearly struggling to get results from the rest of the team. Lets start with what the product manager does.

San Francisco 158

San Francisco Management Software Review Product 158

Steve Blank

DECEMBER 13, 2010

Here’s the course announcement from Professor Vergara (in English): Customer Development Course in Chile – Lean Launchpad. The objective of this course is that groups of students finish with a completed software product that has real customers and an identified market.

Chile 241

Chile Silicon Valley Lean Agile 241

SoCal CTO

JANUARY 5, 2011

Some really great stuff in 2010 that aims to help startups around product, technology, business models, etc.

Silicon Valley 378

Silicon Valley Startup Term Sheet Venture Capital 378

Startup Lessons Learned

DECEMBER 1, 2014

He’s a founder of Andreessen Horowitz, which has backed Facebook, Skype, Jawbone, and dozens of other companies whose products you use. And the whole site was developed in just 9 weeks. Ben Horowitz ’s book The Hard Thing About Hard Things is driving the conversation around startup management this year. Eric Ries will interview him.

Lean 165

Lean Fractional CTO Part-Time VPE Fractional VPE 165

Startup Lessons Learned

SEPTEMBER 15, 2008

The application of agile development methodologies which dramatically reduce waste and unlock creativity in product development. See Customer Development Engineering for my first stab at articulating the theory involved) Ferocious customer-centric rapid iteration, as exemplified by the Customer Development process.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Startup Lessons Learned

NOVEMBER 7, 2008

Thats the conclusion Ive come to after watching tons of online products fail for a complete lack of customers. Our goal is to find out whether customers are interested in your product by offering to give (or even sell) it to them, and then failing to deliver on that promise. Nothing made any difference.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

SEPTEMBER 15, 2008

In my experience, the majority of changes we made to products have no effect at all on customer behavior. This kind of result is typical when you ship a redesign of some part of your product. Without split-testing, your product tends to get prettier over time. First of all, why split-test? One last note on reporting.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

NOVEMBER 13, 2008

Lessons Learned by Eric Ries Thursday, November 13, 2008 Five Whys Taiichi Ohno was one of the inventors of the Toyota Production System. His book Toyota Production System: Beyond Large-Scale Production is a fascinating read, even though its decidedly non-practical. Each five whys email is a teaching document. and so forth.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

MAY 14, 2009

Lessons Learned by Eric Ries Thursday, May 14, 2009 The Lean Startup Workshop - now an OReilly Master Class My rate of posting has been much lower lately, and this is mostly due to preparations for the upcoming Lean Startup Workshop on May 29. Please feel free to send along your comments or questions about the workshop itself.

Lean 60

Lean San Francisco Software Review Continuous Deployment 60

Startup Lessons Learned

SEPTEMBER 30, 2008

If the CEO wants to completely change the product in order to serve a new customer segment, you need someone in the room who can digest the needs of the new (proposed) business, and lay out the costs of each possible approach. Labels: product development 15comments: mukund said. Have you worked with or for a great CTO?

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

SEPTEMBER 13, 2008

Lessons Learned by Eric Ries Saturday, September 13, 2008 SEM on five dollars a day How do you build a new product with constant customer feedback while simultaneously staying under the radar? In a mature company with a mature product, the goal is to pay for lots of people to come to your website. SEM is a simple idea.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

OCTOBER 4, 2008

Every startup has a chance to change the world, by bringing not just a new product, but an entirely new institution into existence. That institution will touch many people in its life: customers, investors, employees, and everyone they touch as well. November 25, 2009 9:54 AM Danny Wong said. hey eric, love the blog.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

MAY 9, 2012

TLDR: Brant Cooper and Patrick Vlaskovits , authors of The Entrepreneur's Guide to Customer Development are back with a new book called The Lean Entrepreneur. It took the idea of Customer Development and made it accessible to a whole new audience. The book is still in production, so I haven't seen the whole thing yet.

Entrepreneur 167

Entrepreneur Lean Southern California San Diego 167

Startup Lessons Learned

FEBRUARY 20, 2009

I owe it originally to lean manufacturing books like Lean Thinking and Toyota Production System. The batch size is the unit at which work-products move between stages in a development process. Similar results apply in product management, design, testing, and even operations. For software, the easiest batch to see is code.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

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. Five Why’s rarely works for general abstract problems like “our product is buggy&# or “our team moves too slow.&#

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

SEPTEMBER 10, 2008

I am convinced one of Joel Spolskys lasting contributions to the field of managing software teams will turn out to be the Joel Test , a checklist of 12 essential practices that you could use to rate the effectiveness of a software product development team. He wrote it in 2000, and as far as I know has never updated it.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

JUNE 15, 2009

This condition makes it much easier for teams to innovate, experiment, and achieve sustained productivity. One large source of waste in development is “double-checking.&# One is used by engineers to refer to the process of getting code fully integrated into production. Continuous deployment also acts as a speed regulator.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

APRIL 4, 2010

The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Expo New York New York, NY Nov 19 The Lean Startup at MIT Boston, MA Nov 20 Lunch workshop at Dogpatch Labs Boston, MA Dec 17 Lean Startup Cohort program begins San Francisco, CA KISSmetrics KISSmetrics is loading. Amazon PostRank

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Startup Lessons Learned

AUGUST 26, 2009

And do your customer development. My biggest thanks goes to the people who generously sponsored scholarships for others to attend the dinner and workshop, Thank you so much! ericries : special thanks once again to @fancy_free and @KISSmetrics for sponsoring scholarships for the #leanstartup workshop in Boulder.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

APRIL 26, 2009

Lessons Learned by Eric Ries Sunday, April 26, 2009 Product development leverage Leverage has once again become a dirty word in the world of finance, and rightly so. But I want to talk about a different kind of leverage, the kind that you can get in product development. We didnt think wed able to compete with that.

Product Development 88

Product Development Developer San Francisco Product 88

Startup Lessons Learned

JULY 28, 2010

It’s common, perhaps the norm, for startups to pivot like that—to discover that a product is catching on in unintended ways worth pursuing. With 21 employees today, kaChing is devoted to recruiting professional managers and finding product/market fit , first for money managers, then for consumers.

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

Startup Lessons Learned

SEPTEMBER 2, 2008

The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Thoughts on scientific product development Lo, my 5 subscribers, who are you? No departments The Five Whys for Startups (for Harvard Business R. ► May (3) Thank you Philosophy Helps Start-Ups Move Faster (WSJ on the.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 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. Answering that question is what Im striving to do on this blog (and at future webcasts and workshops ). Register here.

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

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. Thoughts on scientific product development Lo, my 5 subscribers, who are you?

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

JULY 29, 2009

Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage. The biggest source of waste in new product development is building something that nobody wants. Unfortunately, customers hated that initial product.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

MAY 7, 2009

They were deploying to production with every commit before they had an automated build server or extensive automated test coverage in place. Initially, IMVU sought to quickly build a product that would prove out the soundness of their ideas and test the validity of their business model.

San Francisco 131

San Francisco Continuous Deployment Software Review Lean 131

Startup Lessons Learned

NOVEMBER 4, 2008

It is becoming easier and cheaper for companies to bring products to market, leveraging free and open source software , cloud computing, open social data (Facebook, OpenSocial ), and open distribution (AdWords, SEO). Customer development. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

JUNE 2, 2010

Five Whys has its origins in the Toyota Production System. And yet the key to startup speed is to maintain a disciplined approach to testing and evaluating new products, features, and ideas. Five Whys has its origins in the Toyota Production System. Techniques from lean manufacturing can be part of a startups innovation culture.

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Startup Lessons Learned

DECEMBER 16, 2009

The foundation of TPS ( Toyota Production System ) is that people need to be (and feel) productive and society needs people to produce value. We are all engaged in creating valuable (we hope) services for society in some form or other and simultaneously meeting our own need to feel significant and productive.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

Startup Lessons Learned

MARCH 25, 2010

This is the first post that moves into making specific process recommendations for product development. Everyone was in the flow; the team was hyper-productive. In many cases, they did the impossible, building a new product faster, cheaper, and better than anyone could have predicted.

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

APRIL 14, 2009

This may sound crazy, coming as it does from an advocate of c harging customers for your product from day one. Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. In fact, this company hasn’t shipped any new products in months.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

DECEMBER 8, 2008

Maybe two different developers made changes to the same underlying subsystem, but in incompatible ways. Maybe operations has changed the OS configuration in production in a way that is incompatible with some developers change. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Software Review 136

Software Review San Francisco Lean Continuous Deployment 136

Startup Lessons Learned

SEPTEMBER 14, 2008

In the very early days, the trick is to find anyone at all who can understand you when you are talking about your product. In our first year at IMVU, we thought we were building a 3D avatar chat product. As product people, we thought of competition in terms of features. But the early customers all compared it to MySpace.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Startup Lessons Learned

MAY 31, 2010

When I first encountered customer development , it was considered pure lunacy by mainstream entrepreneurs and VCs. When I first encountered customer development , it was considered pure lunacy by mainstream entrepreneurs and VCs. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Startup Lessons Learned

OCTOBER 6, 2008

Lessons Learned by Eric Ries Monday, October 6, 2008 When NOT to listen to your users; when NOT to rely on split-tests There are three legs to the lean startup concept: agile product development , low-cost (fast to market) platforms , and rapid-iteration customer development.

San Francisco 128

San Francisco Lean Continuous Deployment Agile 128