The lean startup movement – the way we think of it today, at least – began in 2008 when Eric Ries identified a set of trends he believed encapsulated the startup landscape as it had evolved. In very broad and simple terms, the lean startup methodology can be summarized as:
- Agile software development methodology
- Free and open source solutions whenever possible
- Customer-centric rapid iteration to create a minimum viable product
(you can read Eric Ries’ first blog post here)
Since then, lean has become a mantra for many entrepreneurs – and the lean startup movement has been picked up and iterated by many in the form of books, blog posts and conferences. As a young tech entrepreneur in Vancouver I was invited to attend the Lean Startup Conference last weekend and share my thoughts. The conclusion? Not all speakers are created equal, and there is an unfortunate bias for presenters within the lean startup community to focus on frameworks over real world examples. The speaker who stood out the most was Rob Walling, who spoke brilliantly about “what worked for him” as oppose to “here is the way it is.”
Why “here is what worked for me” works
Rob Walling of softwarebyrob.com is a serial web entrepreneur who runs a number of niche web and SaaS companies. Although his room presence was arguably less than that of other speakers he more than made up for it by delivering relevant and valuable information for those of us sitting in the audience. Rob’s lecture was powerful because instead of providing step-by-step instructions to success or a “this is how things are now” speech he simply described what worked for him.
Taking us through a series of slides which outlined how he had acquired various web properties over the years and repurposed them gave me a deeper understanding of a process most often described only at a higher level. Most importantly, I learned about Rob’s specific failures, and why they happened. Most speakers tell you that they failed at some point during their delivery (it seems to be a rite of passage to be allowed to speak at these things) – but few tell you tangibly how, or what they learned. Patrick Vlaskovits, for instance, introduced himself as an entrepreneurs who had burned through two startups, but never told us what they were or why they failed. Lessons are best learned through tangible examples, not high level frameworks.
Frameworks versus experiences
Frameworks can ultimately operate to an entrepreneurs detriment because they simplify the learning process and detach us from having to think about the why. Although we all must learn from the mistakes others have made, when we simply apply frameworks other’s have given us we skip the part where we are allowed to draw our own conclusions from other people’s experiences. Some speakers at #leanstvan trended towards simply providing models for understanding (or worse – models for success). With the exception of strictly informational talks, I would greatly prefer to hear more tangible experiences and less conceptual, extrapolated frameworks. The speaker who says “trust me, here is the lesson I’ve learned” is far less valuable than the one who says “here is what happened to me, draw what conclusions you will.”
The lean startup movement provides many frameworks for entrepreneurs, however those speakers who teach us more about the tangible experiences which led to those frameworks have arguably much more to offer