How to prioritise experiments

Use ICE and PIE frameworks to rank objectively. Focus resources on tests with highest potential impact, not just easy wins.

How to prioritise experiments

Introduction

You can't run every experiment at once. Limited time, budget, and traffic force trade-offs. Prioritisation frameworks like ICE (Impact, Confidence, Ease) and PIE (Potential, Importance, Ease) score experiments objectively so you're not guessing. This removes politics and gut feel from the decision. The highest-scoring experiments get resourced first. This chapter shows you how to score experiments consistently and build a prioritised testing queue.

Understand ICE and PIE ranking frameworks

Score your backlog using chosen framework

Balance quick wins with strategic big bets

Update priorities as you learn from tests

Conclusion

Next chapter

Continue reading

Article
4

How to run experiments properly

Execute tests with proper controls. Avoid peeking early. Monitor external factors. Maintain experiment integrity start to finish.

Playbook

Experimentation

Random experiments waste time and budget. A structured framework ensures every test teaches you something, even when it fails. Decide what to test, design experiments properly, analyse results accurately, and share learnings so the whole team gets smarter.

See playbook
Experimentation
Tools

Relevant tools

VWO
Tool

VWO

VWO provides A/B testing, personalisation, and behaviour analytics to optimise website conversion rates through data-driven experimentation.

Hotjar
Tool

Hotjar

Hotjar captures user behaviour through heatmaps, session recordings, and feedback polls to understand how visitors use your website.

Microsoft Clarity
Tool

Microsoft Clarity

Microsoft Clarity provides free session recordings, heatmaps, and user behaviour analytics without traffic limits or time restrictions.

Notion
Tool

Notion

Flexible workspace for docs, wikis, and lightweight databases ideal when you need custom systems without heavy project management overhead.

Growth wiki

Growth concepts explained in simple language

Wiki

A/B testing

Compare two versions of a page, email, or feature to determine which performs better using statistical methods that isolate the impact of specific changes.

Wiki

Hypothesis testing

Structure experiments around clear predictions to focus efforts on learning rather than random changes and make results easier to interpret afterward.

Wiki

Prioritisation

Systematically rank projects and opportunities using objective frameworks, ensuring scarce resources flow to highest-impact work.

Wiki

Constraint

Identify and leverage limitations as forcing functions that drive creative problem-solving and strategic focus.