I've become a big fan of making it explicit that the hypothesis can NOT include a feature/idea and instead adding a prediction. So it's Problem - Hypothesis - Evidence - Prediction (thanks Reforge).
Works both ways - start with Problem get to Prediction and (probably more importantly) start with Prediction and remember to go back to Problem!
Love this write up. I've been looking for better documentation into how tech companies are experimenting. It's also validating to see that what I'm doing is similar to the pros. Thanks for the article! Well written.
@adam reading Ben's quite shouldn't only be done in a British accent but also in a soothing deep voice. Makes you want to believe everything he says (with good reason to back it up of course)
This is great, thanks for sharing!
I've become a big fan of making it explicit that the hypothesis can NOT include a feature/idea and instead adding a prediction. So it's Problem - Hypothesis - Evidence - Prediction (thanks Reforge).
Works both ways - start with Problem get to Prediction and (probably more importantly) start with Prediction and remember to go back to Problem!
Love this write up. I've been looking for better documentation into how tech companies are experimenting. It's also validating to see that what I'm doing is similar to the pros. Thanks for the article! Well written.
@adam reading Ben's quite shouldn't only be done in a British accent but also in a soothing deep voice. Makes you want to believe everything he says (with good reason to back it up of course)