Hypothesis testing

Hypothesis testing is a structured approach to experimenting with changes to your marketing, sales, or product, using data rather than intuition to validate whether changes actually drive desired outcomes. Rather than implementing changes broadly and assuming they work, hypothesis testing runs controlled experiments: change one element, measure the impact, and decide whether to keep or discard the change based on data.

Hypothesis testing brings scientific rigour to growth decisions. Teams often implement changes based on hunches: 'This headline will perform better,' 'This messaging will resonate more.' Without testing, hunches frequently prove wrong. Hypothesis testing replaces hunches with data, improving decision accuracy and preventing costly mistakes.

Core elements of hypothesis testing

• Hypothesis statement: Specific prediction of what will change and why
• Variables: Define what you're changing (one variable per test) and what you're measuring
• Control group: Baseline against which to compare treatment group
• Test group: Receives the change you're testing
• Sample size: Large enough that results are statistically significant
• Duration: Run test long enough that seasonal factors don't distort results
• Metric: Clear definition of success (how you'll measure if the test worked)

B2B hypothesis testing often requires larger sample sizes because conversion volumes are lower. A B2B email test might need 500 test recipients to generate statistically significant results; the same test in B2C might need 50. Plan test scope accordingly.

Hypothesis testing prevents expensive mistakes. Implementing untested changes across all customers risks poor outcomes. Testing first allows you to confirm changes drive desired results before full implementation. This prevents launching ineffective messaging, pricing, or features to the entire customer base.

Hypothesis testing compounds learning over time. Each test provides insights into what resonates with your customers. Accumulated test results reveal patterns: which headlines work, which offers convert, which features drive engagement. These patterns guide future decisions with increased confidence.

Hypothesis testing improves team efficiency. Rather than debating whether a change will work, teams run tests and let data decide. This reduces bike-shedding, accelerates decision making, and builds team confidence in decisions: they're based on data, not politics or strongest opinion.

Start with clear hypotheses. Rather than vague 'test if this email performs better,' write: 'We believe that subject lines addressing specific ROI metrics will increase open rates by 5% because our target audience evaluates on financial impact.' Specific hypotheses make success criteria clear.

Change one variable per test. Testing multiple changes simultaneously makes it impossible to identify which change drove results. If you test both subject line and send time, and performance improves, which element caused it? Single-variable tests provide clear attribution.

Define sample size and duration before starting tests. Decide how many test recipients you need and how long you'll run tests before analysing results. This prevents temptation to stop tests early when results look positive (which often leads to false positives).

Analyse statistical significance, not just percentage difference. A 5% improvement might be meaningful or noise depending on sample size. Tools like A/B test calculators show whether improvements are statistically significant. Only implement changes where improvements are statistically significant at 95% confidence level.

A SaaS company hypothesised that new users struggling to complete onboarding were due to not understanding feature value. They tested two versions: (1) standard onboarding (feature walkthrough), (2) value-focused onboarding (showing three use cases, then walking through corresponding features). Both groups were tracked over 30 days. Users in the value-focused group (group 2) reached full product engagement at 45% rate, versus 28% for the standard group. This 17-point improvement was statistically significant. The company rolled out value-focused onboarding to all new users, improving overall user activation rate from 28% to 42%.

An enterprise software company tested email subject lines. Hypothesis: Addressing cost reduction (ROI angle) would outperform process improvement (efficiency angle) because CFOs (key decision-maker) prioritise cost. Test group 1 received emails with cost-reduction messaging. Test group 2 (control) received standard messaging. Sample size: 5000 per group. Run duration: 7 days. Cost-reduction messaging improved open rate from 18% to 24% and click rate from 4% to 6.2%. Improvements were statistically significant. The company shifted all sales follow-up emails to emphasise cost reduction, improving conversion rates downstream.

A B2B agency tested landing page layouts. Hypothesis: Placing customer logos prominently above the fold would increase form submissions by 10% because social proof reduces evaluation anxiety. They split traffic 50/50: version A (logos below fold), version B (logos above fold, prominent). 2000 visitors per version, one-week duration. Form submission rate: version A (3.2%), version B (5.1%). This 1.9-point improvement (59% increase) was statistically significant. The agency updated all landing pages to feature customer logos prominently, systematically improving conversion rates across campaigns.