How do we run an experimentation programme without wasting budget?

A budget-controlled experimentation programme starts with a clear assumption, tests it quickly at a proportionate scale, and uses the result to decide what earns further investment. Keep experimentation tied to a specific audience, campaign or business aim, rather than funding open-ended activity in the hope that ideas will pay off.

Treat experiments as learning investments, not speculative spending

A cost-effective experimentation programme tests assumptions early, learns from weak signals and builds only on ideas that show promise. This is not reckless failing fast. It is a disciplined way to make uncertainty smaller before larger budgets are committed.

The useful unit of experimentation is not a grand innovation project. It is a focused prototype for an idea, message, proposition or campaign approach. Teams can explore possibilities freely at the start, but each idea needs a practical next move: test the assumption, capture what happened and decide whether to iterate, progress or stop. Rapid prototyping helps prevent a team from spending months defending an idea that could have been checked in days.

Sources: What’s next? The answer is already in the room

Set the guardrails before creative work begins

Experimentation stays within budget when the team agrees the audience, business aim, available spend and decision criteria before making the work. Audience and industry research provide the starting point, helping teams understand the landscape rather than treating every new idea as a leap into the unknown.

A clear strategy gives each test a job to do. The team can then judge an experiment against the present campaign objective, instead of forcing it to match metrics from a different market moment or a previous success. This makes boardroom conversations more straightforward too: the expected cost, the intended return and the audience insight behind the test are visible from the outset. Planned and budgeted risks are easier to support because they are choices, not surprises.

Sources: How to inspire decision-makers to be bold, The problem with playing it safe

Protect learning from pressure to repeat the past

The biggest threat to a test-and-learn programme is often pressure to deliver familiar results, which can push teams towards safe, repetitive choices. Specific goals are necessary, but goals borrowed from past campaigns can become a brake when conditions, audiences and priorities have changed.

Use measures that fit the current experiment and its intended decision. A small test should not carry the burden of proving an entire strategy, and an early result should not be treated as a final verdict. Make room to identify what did not work, why it did not work and what should change next. That is how experimentation avoids both waste and false confidence. A programme that only funds ideas certain to succeed is not learning, it is simply repeating.

Sources: What’s next? The answer is already in the room, The problem with playing it safe

Budget discipline should make experimentation braver, not smaller

We believe experimentation earns its budget when it turns uncertainty into a clear next decision. That means giving teams space to imagine, while asking every idea to meet reality through rapid prototyping, learning and iteration. We do not see intelligent failing as a licence to spend without care. We see it as a practical alternative to investing heavily in untested assumptions or defaulting to familiar work because it feels safer.

Our work with successful teams has shown us that ideas become more useful when they are tested early and improved quickly. We also believe bold work needs rigorous foundations: audience understanding, a persuasive proposition and a strategy that can stand up to honest questions about cost, return and relevance.

Sources: What’s next? The answer is already in the room, How to inspire decision-makers to be bold, The problem with playing it safe

Stats

FAQs

What should an experimentation budget pay for first?

An experimentation budget should first pay for the research, prototype and measurement needed to test a meaningful assumption. Audience and industry understanding help teams choose ideas with a clear purpose, while rapid prototypes limit the cost of learning. Larger production or rollout spend should follow only when the experiment gives a reason to progress.

How do we know when to stop an experiment?

Stop an experiment when the result gives the team enough clarity to reject, revise or advance the underlying assumption. A useful test does not need to prove an entire strategy. It needs to reveal what is not working, what may work better and whether further investment is justified.

How can we make experimentation easier to approve internally?

Internal approval is easier when a proposed test has a defined audience, a clear objective, a planned budget and a credible account of expected returns. Research and due diligence give decision-makers a basis for judging the idea, rather than asking them to back novelty for its own sake. A strong proposition and clear strategy should make the case without hard-selling.

Does failing fast mean accepting poor work?

Failing fast means testing assumptions quickly and learning from what does not work, not lowering the standard of the work. Intelligent failing is designed to reduce the cost of being wrong by finding out earlier. The aim is better decisions and stronger iterations, not failure as a badge of honour.

Glossary

Intelligent failing
A practice of testing assumptions quickly, learning from weak or unsuccessful results and iterating towards a stronger answer, without treating experimentation as reckless spending.