The power of the (Lean) startup mindset
Last week, while in Canada, I saw this article in the Globe & Mail: “The power of the startup mindset.”
I was surprised that the word “Lean” didn't appear in the headline (there was physical space for it in the print edition). It was basically an article about the “Lean Startup” methodology, but it didn't mention Lean and it didn't cite Eric Ries and his book The Lean Startup: How Today's Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses.
I'm not sure that “Lean startup” philosophies have become so widespread that it's now the only way that startups are being built. There are still “fat startups,” I'm sure, that work in stealth mode for months or years trying to build the perfect software that they are guessing is wanted by customers.
The article describes sounds what sounds like a classic “minimum viable product” strategy, using iterative development and customer feedback to prove out both the product AND the business model.
When Kira Talent released its first platform, it was little more than a prototype, hampered by a rudimentary interface and numerous bugs. It was, however, enough for the needs of its first customer.
Today, she still doesn't pretend to have all the answers. The close interaction continues, and the ensuing feedback is used to continually optimize Kira Talent's platform, which has undergone many iterations since its inception.
Ms. Cushman is part of a growing group of entrepreneurs who value experimentation and trial and error over the traditional approach of honing products for months before introducing them to customers. These companies understand that innovation is a messy, unpredictable process.
Anyway, check out the article… it suggests that larger companies are learning to use these “Lean Startup” techniques (companies like GE have presented at Eric's event, before).
The same mindset applies to areas like healthcare. Instead of working for months and months trying to develop a perfect process, can we start by implementing something that's better (but not perfect) and then iterate from there? Can we implement and test smaller batches of improvement? This can often be done by breaking large, unmanageable problems (like “patient satisfaction is too low”) into smaller problems (like reducing noise complaints). Many many staff ideas can be implemented and tested (as we write about in our Healthcare Kaizen series of books) instead of relying on one large project to “fix everything.”