ℹ️ We often queue a mix of

2-3 'quick, high impact'

+

1-2 'lengthy, high impact'

implementations.

ℹ️ We draw from 20-30 archetypical solutions that have proven very successful.

💡 The goal with each new version is to veritably measure significantly improved purchase and revenue results. Meaning we want to capture sufficient performance variance with each new version.

💡 The goal of 1-2 big bottom line improvement wins is protected with sufficient runway in 3-5 tries.

ℹ️  We can include any segments of users and website traffic, and measure results for each separately.

ℹ️  We can also use A/B testing tools to maintain segmented or "personalized" experiences.

💡 The goal is to take a veritable step up. And it's actually easier to get veritable results by aiming for high impact and wide variance ➝ *So rather than using A/B tools to split test little bits and individual elements, it's more beneficial to implement and measure our best high impact ideas, or new improved versions that incorporate many of our best ideas.*

💡 To achieve smooth productivity, we work directly with development teams to implement new versions effeciently.

ℹ️ We measure the long term effects of successful A/B tests in increasing monthly revenue.

ℹ️ If we do not measure improvement with a new version—it happens sometimes—then we can keep the previous version, and move forward with the next implementation, already prepared and ready to go as planned.

💡 A big CRO win means not only increased monthly revenue, it means more returning customers, positive reviews, and efficiencies of digital marketing campaigns. It may unlock compounded growth, new acquisition channels, or warrant new investment.

💡 With this practical process, we reach for more dynamic results, faster, while exercising more creativity and trying to provide our users and customers the most positive experience we can provide. We measure properly to be sure—and so we can celebrate.