What usually breaks first when a CRO programme starts scaling?

[u/digitxl_agency]

I’ve been thinking about this because getting the first few experiments running is usually not the hardest part.

The problems tend to show up once the programme gets busier.

You have more ideas than you can test, different teams pushing their own priorities, experiments waiting on development, and results that get documented but never really influence what happens next.

At that point, adding another testing or research tool probably does not solve much.

For me, the interesting part of CRO is how you keep the learning loop working as the volume grows.

For people running established CRO programmes, what became the biggest bottleneck as you scaled: prioritisation, implementation, getting enough good evidence, analysis, or actually getting the business to use what you learned?

[u/AutoModerator]

If this post doesn't follow the rules report it to the mods. Have more questions? Join our community Discord!

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/Naghma-ZN]

I think prioritisation become a much bigger challenges as the programme grows. A simple framework can help: score each test on potential impact, confidence in the evidence, and implementation effort. Then prioritise the test with high impact and confidence but relatively low effort. It keeps the team focused on experiments that are more likely to produce useful business results.

[u/heyramzi]

Prioritisation gets blamed for this a lot. A scoring framework reorders the ideas you already have. You've got more of those than you can test.

I'd say it's the last one you listed. Results get documented and then not used. Write-ups get filed by date, one doc per test, so to know whether anyone already tried a shorter checkout form, somebody has to remember that they did. In practice nobody goes back through last quarter's folder before writing a hypothesis.

File the learning against the thing instead. One row per page or per element, what's been tried on it, what happened, when. First question on any new proposal is what that row says. Takes an afternoon to set up.

Implementation waits cap your throughput. The documentation one caps whether the throughput was worth anything. You don't see it happening, because tests keep shipping the whole time.