What's your learning bias?
"If you already think you are a great singer and a well-happening front person, we have a problem. It means you will have the sort of ego that will render it totally impossible for you to be objective about everything else that's got to be done." - The Manual (How to Have a Number One the Easy Way) by The KLF
It's interesting to be around different types who adopt Lean Startup. In the Learning Loop, aka Build-Measure-Learn, "build" gets interpreted differently. I've noticed that quite a few people use this to indulge, rather than spot, their biases. People tend to map the build part of their loop to their favourite activities – they choose what they want to learn based on what they want to build. In doing so, they lose some of the best learning opportunities available to them.
Can you spot yourself in any of these scenarios?
The Coding Crutch
The classic story is Joel Gascoigne, a programmer who, while running the first tests to validate the idea for his startup Buffer, kept jumping back into programming mode at every little sign of market demand. [tweetable hashtag="#leanstartup"]Every time he stopped learning to write code, he was slowing down further validation and learning. What did he do to break the habit? He deleted all of his code so he'd stay focused on validating market demand! It worked.
Narrowing, rather than broadening, scopes for learning
This isn't limited to coders. For example, some UX designers have a penchant for interfaces or information architecture, so they tend towards wireframes or paper prototypes in their build-measure-learn loop. With learning accomplished, [tweetable hashtag="#leanstartup"]the next learning goal gets framed as another user experience goal, leaving more critical aspects of the business untested.
The Git Of Gab
And people who like talking to people will stick to Customer Development, even when the most crucial validation requires product or channel development. Customer Development is a great tool for understanding commercial opportunities from the customers' perspectives, but rarely does it give you explicit instructions. [tweetable hashtag="#leanstartup"]Some people continually go back to customer interviews when there are more tangible MVPs to build and test.
There are also salespeople with the mantra, "promise the world, deliver what you can." When presented with the concept of a Letter Of Intent as validation, they say that's what they've been doing the whole time! By focusing on "the close" and what it takes to make a deal with each, individual customer, [tweetable hashtag="#leanstartup"]they lose focus on the learning goal – discovering the minimum feature set to meet consistent, repeatable needs of the customer segment.
Sometimes, it's hard to pick an idea or pick a starting point, and planning to learn never leads to actually doing the learning. In other cases, more and [tweetable hashtag="#leanstartup"]more learning goals pile up for the same "MVP" and continually delays getting the thing out there.
People who have analytics backgrounds tend to build out heavy measurement platforms, capturing and reporting on all kinds of behaviours. Building out these systems, rather than focusing on a key few metrics, actually slows down learning as these systems take more time to build, configure, install and they also take more time to pull out actionable information. All of this slows down actionable learning. [tweetable hashtag="#leanstartup"]Are you measuring everything because you're not sure what to measure?
When I was Digital Media Director at a jwt agency, there was a phrase in the analytics department: "Torture your data long enough, and it'll tell you anything." It was a warning to the account directors and clients who only wanted data to back their conclusion. [tweetable hashtag="#leanstartup"]When you start an experiment, are you trying to prove yourself right, or wrong?
Using Learning To Avoid Decisions
Some people continually learn and validate broadly, failing to zero in on more tangible opportunities. As you learn, your idea of customer segments, product, partners, channel and relationship become clearer – so you're in a better position of collecting evidence to back them. As you do, your customer list will start to build. But, some of us don't get there, not because of the lack of validation, but the lack of mettle to simply take things to the next level.
The Lean Startup methodology does not advocate using optimization techniques to make startup decisions. That’s right. You don’t have to listen to customers, you don’t have to split-test, and you are free to ignore any data you want. [tweetable hashtag="#leanstartup"]This isn’t kindergarten. You don’t get a gold star for listening to what customers say. You only get a gold star for achieving results. - Eric Ries
For example, [tweetable hashtag="#leanstartup"]a lot of first-time founders use learning as an excuse to avoid sticking their neck out, like using surveys as an excuse to avoid talking to customers. And there are founders who continually ignore the results of their tests, yet continue to waste time running them.
What can you do about it?
If you're having trouble learning what you need to learn, you might want to look at yourself and see if you're biases are pushing you towards the wrong learning tools.
The key to the build-measure-learn loop is start with what you want to learn, and why. With that clear, the measurement becomes more obvious, and then what to build follows. Start with your learning goal – what worries you the most? what poses the greatest risk? – and work backwards from there.