Many assume that the measure of success for an optimization program is a high testing velocity.  The problem here is that in order to support a high velocity, other parts of the test development pipeline become neglected, including developing a well thought out hypothesis.

How critical is a test hypothesis to the success of a test?  What goes into developing a test hypothesis and why is it important?  What happens when that part of the process is neglected?  What is more important, velocity or proper planning?  Is there a metric above all others when it comes to measuring the success?

On this episode of the 33 Tangents podcast, Jim is joined by Jason Boal to wrap up the series on optimization programs.  They discuss why a test hypothesis is a key part of the processes of running an optimization program and gaining support from executive leadership.

We know your time is limited, so it means a lot to us that you would spend some of your time with us. If you have found this episode to be valuable, we would appreciate if you would share it.

And if we are getting you hooked, don’t forget to subscribe, like, and recommend on your favorite podcast platform.

The 33 Tangents video simulcast is now available on YouTube

Subscribe on Apple Podcasts

Subscribe on Google Podcasts

Listen on TuneIn

Listen on Amazon Music

Website: www.33sticks.com

Email: [email protected]

Twitter: https://twitter.com/33Sticks

Facebook: https://www.facebook.com/33sticks/

YouTube: https://www.youtube.com/channel/UC8KUpp_LygXotCrKgR9ZoBg