Experiment win rate and programme KPIs: are you measuring your growth engine properly?

Most teams measure experiments at the wrong layer. They look at one A/B test, see a lift or no lift, and draw a conclusion from it. But a single test says almost nothing about the health of your growth engine. The real question is: does your experimentation programme work well as a system? And you measure that with programme KPIs, not with the outcome of a single test.

Growth marketing is not a bag of tricks but the system that orchestrates SEO, CRO, content, paid and lead generation into one predictable growth engine. That system lives or dies by how well you experiment. In this article you will read which KPIs you need for that: velocity, experiment win rate and learning rate. Not as separate numbers, but as a set you read together.

Why the outcome of a single test misleads you

Picture this: you run a test on your most important landing page and it wins with a decent lift. Feels good. But what if that was the only test you completed that quarter? Then you got lucky, you did not build a growth engine. And suppose you ran ten tests and only two won. Many teams would call that a disappointment. Whereas two winners out of ten valid experiments is a perfectly good result.

The problem is that you are steering on noise this way. Individual tests are erratic: the outcome depends on season, traffic, chance and how sharp your hypothesis was. Only when you look across dozens of experiments do you see a pattern that says something about your process. That is why you shift your attention from the test layer to the programme layer.

What you want to know is not “did this test win?” but “is my programme healthy enough to produce winners consistently?”. That is a fundamentally different question, and you answer it with three KPIs.

KPI 1: velocity, how many valid experiments do you complete

Velocity is the number of well-designed experiments you complete per month or per quarter. Not the number of ideas, not the number of tests you started, but the tests you let run properly and from which you could draw a conclusion.

Velocity is often your biggest lever, and that is counter-intuitive. Teams that want to accelerate usually focus on a higher win rate: better ideas, sharper hypotheses, smarter variants. But the maths works differently. If your win rate sits around 25 percent and is stable, then every extra winner comes from more attempts. Four extra valid tests per month deliver, at that win rate, one extra winner on average. Multiply that across a year and the difference is enormous.

Low velocity is almost always a process problem, not an ideas problem. Tests get stuck in approval, engineering is a bottleneck, or there is no clear owner. If you want to go deeper here, read how to set up an experimentation programme that keeps running. Speed comes from a working process, not from working harder.

Do pay attention to the word valid. Twenty sloppy tests you cannot interpret do not count. Velocity without quality is a false move. An experiment only counts if it had a clear hypothesis, got enough runtime and delivered a measurable outcome.

KPI 2: win rate, and why high is not always good

Win rate is the share of your experiments that delivers a positive, meaningful result. This is where the biggest thinking error sits in many teams: they believe a high win rate is the goal. It is not.

A win rate of roughly 20 to 30 percent counts as healthy in mature experimentation teams. That means seven out of ten tests do not win. That feels like a loss, but it is exactly what you want to see. Because a win rate that creeps towards 60 or 70 percent usually means you are running tests that are too cautious: small, safe tweaks whose outcome you basically already knew. You are confirming what you already suspected instead of learning something new.

The big wins sit in the bold tests, and those have a lower success rate by definition. A team that deliberately takes risks on the hypotheses that genuinely matter accepts a lower win rate in exchange for bigger winners. Steer your team towards a high win rate and you are steering them towards timid experiments. That way you optimise yourself into mediocrity.

So never read win rate separately from velocity. A win rate of 30 percent on forty tests per quarter is a strong engine. That same 30 percent on four tests is almost meaningless. And a win rate of 70 percent is no reason for pride, but a signal that you may dare to think bigger. Just as with vanity metrics in marketing, the rule applies: a number that looks good can steer you in the wrong direction.

KPI 3: learning rate, the value of losing tests

This is where a real programme separates itself from a test factory. Learning rate measures which share of your experiments, won or lost, delivers a usable insight or a concrete decision.

A losing test is not a waste if you learn something from it. In fact: most of your tests are going to lose, so if those losses deliver nothing, you throw away the bulk of your effort. An experiment that cleanly disproves that your audience cares about price saves you months of the wrong focus. That is valuable, even without a lift to show for it.

Learning rate enforces discipline up front. Because a test only delivers a takeaway if you formulated a sharp hypothesis beforehand: “we believe that X, because Y, and we will see that when Z happens.” Without that structure you do not know what you actually know when you lose. With that structure, every result is information. This is also why the design of your experimentation programme is so decisive for what it delivers.

A healthy learning rate is high, higher than your win rate. You may win a quarter of your tests, but you should get an insight out of the vast majority. If your learning rate is low, you are running tests without a clear question. Then you are busy, but you are not learning anything.

Reading the three KPIs together

The power sits in the combination. Each number on its own can mislead you:

• High velocity, low win rate, low learning rate: you run a lot of tests, but without sharp hypotheses. Very busy, little return.
• Low velocity, high win rate: you test too little and too safely. You win often, but the engine is nearly at a standstill.
• Healthy velocity, win rate around 25 percent, high learning rate: this is a working growth engine. Enough good attempts, bold enough to learn, structured enough to use every result.

The goal is therefore not a perfect number on one KPI, but a healthy balance between the three. A good growth approach steers on that balance, and then ties it to the numbers that genuinely affect your business: pipeline, leads and revenue. Because all these programme KPIs are a means, not an end. They tell you whether your engine is running healthily; your business KPIs tell you whether that engine is driving in the right direction. How to tie those two layers together, you can read in our explanation of marketing KPIs that actually matter.

How this fits into a growth engine

Programme KPIs are not a standalone CRO thing. They are the heartbeat of your entire growth system. Whether you run an SEO experiment, adjust a paid campaign, test a new lead generation flow or set up an advocacy programme with customer ambassadors: every discipline feeds the same experimentation rhythm. Velocity, win rate and learning rate tell you whether that rhythm is healthy across all those channels.

That is why they belong at the level of your strategy, not with one team. If you want to understand how experimentation fits into the bigger picture, read our explanation of what growth marketing is and how it works as a system. And if you want to not only measure that system but also run it with a fixed experimentation rhythm, that is exactly what an experienced growth marketing agency sets up for you: a growth engine that predictably learns and wins.

Do you want to check more broadly whether you are measuring your growth engine properly at all? Then work through our growth analytics audit in 9 checks before you tinker any further.

Are you still measuring your growth engine on individual tests instead of on the health of your programme? Then you are probably steering on noise. Schedule a call and we will look together at your velocity, win rate and learning rate, and at what those tell you about your next step.