I'm running another free LIVE 20-minute training on July 7th at 11:00 AM CT with Q&A at the end.

I'm doing a second round of how to turn qualitative insights into quantitative insights via a coding process that you'll be able to execute immediately.

The process is scalable, easy to use, repeatable, and consistent. Your insights will be more actionable, shareable, and understandable.

It was a hit the first round, so I thought it'd be worth a second one.

Back to Basics: Stop Saying We Have an “A/B Testing Program”

The term "A/B testing" is not an accurate, all-encompassing way to describe testing/experimentation efforts most of the time. People use this as a blanket term incorrectly CONSTANTLY.

An "A/B test" is a TYPE of test. It is not the only one. Other common ones include A/B/n tests, MVT tests, and MAB tests.

When referencing a testing/experimentation program (those two terms are used interchangeably all the time, too), call it just that. A "testing program." Or an "experimentation program." That's much more accurate.

Back to Basics: “Redirect Tests” Are Frequently Misclassified

Calling something a "redirect test" is not the same type of categorization as calling something an "A/B test" or an "A/B/n test."

A redirect is simply how the test is setup from a technical perspective in a given testing tool. It does not affect the number of variations you're running or the stats behind the results.

Interested in working on larger research projects or experimentation together? Email me at [email protected]. Let’s chat.