Great article. Designing a/b systems always seems (relatively) simple at the start, but in my experience there are 1,000 things you don't think of until you have massive amounts of worthless results. Add this to the list of things to watch out for.
I think using them together is crucial. Qualitative research gives you insight into what you should look for through quantitative research. It's important to start with some basic qualitative research (talking to a few customers) and then scale it through quantitative methods (analyzing logs).
I like the part about arming others to help you. I've found this to be critical. The more your job specs reflect the excitement of working at your company, the more other people can evangelize that for you.
Shutterstock - New York, San Francisco, Remote, Visa
We're hiring all sorts of software engineers and data scientists. We've got some pretty fun problems -- image search, video search, storage scalability, tons of behavioral data to mine -- and an awesome team. We prefer folks to work in one of our offices, but are always willing to consider remote superstars.
Shutterstock - New York, San Francisco, Berlin, Remote, Visa
We're hiring all sorts of software engineers and data scientists. We've got some pretty fun problems -- image search, video search, storage scalability, tons of behavioral data to mine -- and an awesome team. We prefer folks to work in one of our offices, but are always willing to consider remote superstars.
Shutterstock - New York, San Francisco, Berlin, Remote
We're hiring all sorts of software engineers and data scientists. We've got some pretty fun problems -- image search, video search, storage scalability, tons of behavioral data to mine -- and an awesome team. We prefer folks to work in one of our offices, but are always willing to consider remote superstars.