Velocity Growth animated logo

We don't test enough before release

By
Mukund Kabra

Teams skip testing when every test feels like a big project. Make testing routine: a standard way to set up experiments, a minimum sample size, and a rule that big changes ship to part of your users first.

Category:
Measurement
Reading time:
2
min read
Published on:
October 24, 2026
Resources
right Created with Sketch.
Measurement
right Created with Sketch.
We don't test enough before release

We don't test enough before release

Problem

Big changes go live to every user at once.

A new checkout, a redesigned page or a pricing change ships, and then the team watches the numbers and hopes. When results drop, nobody knows whether the change caused it.

Rolling back is painful, so bad changes often stay.

Insight

Testing is cheap once the setup exists.

Teams avoid tests because each one feels custom: new tooling, new analysis, a long debate about results. A standard setup removes that cost.

Releasing to a share of users first turns every launch into a test without slowing it down.

How we approach it

We make testing the default way to ship.

  1. We set up the tools and a standard template for every experiment.
  2. We agree the rules: sample size, test length and what counts as a win.
  3. We release important changes to part of your users first and compare.

You learn from every launch, and you catch bad changes before everyone sees them.

Tags:  
Feature Revenue Attribution; Product Analytics; Growth Impact; Feature Roi; Revenue Measurement; data-driven Insights
left Created with Sketch.
Previous
Next
right Created with Sketch.

Ready to scale profitably?

Let's discuss how to unlock sustainable growth without sacrificing unit economics.

Speak to Velocity
{"@context":"https://schema.org","@graph":[{"@type":"BlogPosting","headline":"We don't test enough before release","description":"How to make testing a normal part of releasing changes, instead of a big project the team avoids.","author":{"@type":"Person","name":"Mukund Kabra","url":"https://www.velocitygrowth.ae/about"},"publisher":{"@type":"Organization","name":"Velocity Growth","url":"https://www.velocitygrowth.ae","logo":{"@type":"ImageObject","url":"https://www.velocitygrowth.ae/vg-icon.png"}},"datePublished":"2026-01-24T04:08:24.271Z","dateModified":"2026-10-23T13:55:14.402Z","url":"https://www.velocitygrowth.ae/problems/dont-test-enough-before-release","mainEntityOfPage":{"@type":"WebPage","@id":"https://www.velocitygrowth.ae/problems/dont-test-enough-before-release"},"keywords":"feature revenue attribution, product analytics; growth impact; feature ROI; revenue measurement; data-driven insights","inLanguage":"en"},{"@type":"WebPage","name":"We don't test enough before release","url":"https://www.velocitygrowth.ae/problems/dont-test-enough-before-release","speakable":{"@type":"SpeakableSpecification","cssSelector":["h1",".post-body > p:first-of-type"]}}]}